diff --git a/docs/anchors/prd.adoc b/docs/anchors/prd.adoc new file mode 100644 index 0000000..d0aab75 --- /dev/null +++ b/docs/anchors/prd.adoc @@ -0,0 +1,51 @@ += PRD +:categories: requirements-engineering +:roles: product-owner, business-analyst, software-developer, team-lead +:related: moscow, user-story-mapping, impact-mapping, ears-requirements +:proponents: Marty Cagan, Roman Pichler +:tags: product, requirements, specification, planning, stakeholders + +[%collapsible] +==== +Full Name:: Product Requirements Document + +Also known as:: Product Spec, Feature Spec, Requirements Specification + +[discrete] +== *Core Concepts*: + +Problem statement:: Clear articulation of the problem to be solved and the target users + +Goals and success metrics:: Measurable outcomes that define what "done" looks like (KPIs, OKRs) + +User personas and use cases:: Who will use the product and what they are trying to accomplish + +Functional requirements:: What the system must do — features, behaviors, and capabilities + +Non-functional requirements:: Quality attributes — performance, security, scalability, accessibility + +Scope and out-of-scope:: Explicit boundaries to prevent scope creep and align stakeholders + +Constraints and assumptions:: Technical, business, regulatory, or timeline constraints + +Open questions:: Unresolved decisions or dependencies that must be tracked + +Key Proponents:: Marty Cagan ("Inspired"), Roman Pichler ("Strategize") + +[discrete] +== *When to Use*: + +* Before starting design or development of a new product or major feature +* When aligning cross-functional teams (engineering, design, marketing, legal) +* To provide a shared reference for scope negotiations and tradeoff decisions +* When stakeholder sign-off or compliance documentation is required +* As a living document updated throughout the product discovery process + +[discrete] +== *Related Anchors*: + +* <> +* <> +* <> +* <> +==== diff --git a/docs/anchors/prd.de.adoc b/docs/anchors/prd.de.adoc new file mode 100644 index 0000000..d842c5f --- /dev/null +++ b/docs/anchors/prd.de.adoc @@ -0,0 +1,51 @@ += PRD +:categories: requirements-engineering +:roles: product-owner, business-analyst, software-developer, team-lead +:related: moscow, user-story-mapping, impact-mapping, ears-requirements +:proponents: Marty Cagan, Roman Pichler +:tags: product, requirements, specification, planning, stakeholders + +[%collapsible] +==== +Vollständiger Name:: Product Requirements Document (Produktanforderungsdokument) + +Auch bekannt als:: Product Spec, Feature Spec, Anforderungsspezifikation + +[discrete] +== *Kernkonzepte*: + +Problembeschreibung:: Klare Formulierung des zu lösenden Problems und der Zielnutzer + +Ziele und Erfolgskennzahlen:: Messbare Ergebnisse, die definieren, was „fertig" bedeutet (KPIs, OKRs) + +Nutzerpersonas und Anwendungsfälle:: Wer das Produkt nutzt und was die Nutzer erreichen möchten + +Funktionale Anforderungen:: Was das System tun muss — Features, Verhalten und Fähigkeiten + +Nicht-funktionale Anforderungen:: Qualitätsattribute — Performance, Sicherheit, Skalierbarkeit, Barrierefreiheit + +Scope und Out-of-Scope:: Explizite Grenzen zur Vermeidung von Scope Creep und zur Abstimmung mit Stakeholdern + +Einschränkungen und Annahmen:: Technische, geschäftliche, regulatorische oder zeitliche Einschränkungen + +Offene Fragen:: Ungelöste Entscheidungen oder Abhängigkeiten, die verfolgt werden müssen + +Schlüsselvertreter:: Marty Cagan ("Inspired"), Roman Pichler ("Strategize") + +[discrete] +== *Wann zu verwenden*: + +* Vor Beginn von Design oder Entwicklung eines neuen Produkts oder eines größeren Features +* Zur Abstimmung funktionsübergreifender Teams (Engineering, Design, Marketing, Recht) +* Als gemeinsame Referenz für Scope-Verhandlungen und Abwägungsentscheidungen +* Wenn Stakeholder-Freigabe oder Compliance-Dokumentation erforderlich ist +* Als lebendes Dokument, das während des Produktentdeckungsprozesses aktualisiert wird + +[discrete] +== *Verwandte Anker*: + +* <> +* <> +* <> +* <> +==== diff --git a/skill/semantic-anchor-translator/references/catalog.md b/skill/semantic-anchor-translator/references/catalog.md index d6666e9..c9f09f1 100644 --- a/skill/semantic-anchor-translator/references/catalog.md +++ b/skill/semantic-anchor-translator/references/catalog.md @@ -202,6 +202,11 @@ Source: https://github.com/LLM-Coding/Semantic-Anchors ## Requirements Engineering +### PRD +- **Also known as:** Product Requirements Document, Product Spec, Feature Spec +- **Proponents:** Marty Cagan, Roman Pichler +- **Core:** Problem statement, goals & success metrics, user personas, functional & non-functional requirements, scope boundaries, constraints, open questions + ### MoSCoW - **Proponents:** Dai Clegg - **Core:** Must have, Should have, Could have, Won't have diff --git a/website/public/data/anchors.json b/website/public/data/anchors.json index 963aa84..ceef23c 100644 --- a/website/public/data/anchors.json +++ b/website/public/data/anchors.json @@ -1804,6 +1804,37 @@ "filePath": "docs/anchors/plain-english-strunk-white.adoc", "tier": 3 }, + { + "id": "prd", + "title": "PRD", + "categories": [ + "requirements-engineering" + ], + "roles": [ + "product-owner", + "business-analyst", + "software-developer", + "team-lead" + ], + "related": [ + "moscow", + "user-story-mapping", + "impact-mapping", + "ears-requirements" + ], + "proponents": [ + "Marty Cagan", + "Roman Pichler" + ], + "tags": [ + "product", + "requirements", + "specification", + "planning", + "stakeholders" + ], + "filePath": "docs/anchors/prd.adoc" + }, { "id": "problem-space-nvc", "title": "Nonviolent Communication (Rosenberg)", diff --git a/website/public/data/categories.json b/website/public/data/categories.json index 67d1896..1957d94 100644 --- a/website/public/data/categories.json +++ b/website/public/data/categories.json @@ -105,6 +105,7 @@ "anchors": [ "ears-requirements", "moscow", + "prd", "problem-space-nvc", "user-story-mapping" ] diff --git a/website/public/data/roles.json b/website/public/data/roles.json index 34da6df..877c6ba 100644 --- a/website/public/data/roles.json +++ b/website/public/data/roles.json @@ -17,6 +17,7 @@ "mece", "moscow", "plain-english-strunk-white", + "prd", "problem-space-nvc", "pyramid-principle", "regulated-environment", @@ -123,6 +124,7 @@ "morphological-box", "moscow", "myers-briggs-type-indicator", + "prd", "problem-space-nvc", "pugh-matrix", "semantic-versioning", @@ -276,6 +278,7 @@ "mutation-testing", "owasp-top-10", "plain-english-strunk-white", + "prd", "property-based-testing", "regulated-environment", "semantic-versioning", @@ -325,6 +328,7 @@ "moscow", "myers-briggs-type-indicator", "owasp-top-10", + "prd", "problem-space-nvc", "pugh-matrix", "pyramid-principle",