Introduction
Expand | title | Explanation ...
---|
The product requirements document (PRD) is a central document used to align all stakeholders (product management, engineering, QA, designers, and leadership) on the overall objective and vision of the proposed product and is used as a decision-making tool. When creating the PRD, provide just as much information as needed and nothing more. If the document is too long and complex, it will quickly become outdated, and readers will lose interest. PRD content and structure vary by organization. Depending upon the product line, company culture, and processes, PRDs could have quite a different look and feel. In this latest iteration of the Unified Compliance PRD template, we changed the template to help raise visibility of how the proposed product (or feature set) adheres to Unified Compliance’s strategic plan including details on why this product proposal is important to Unified Compliance. |
...
Expand |
---|
|
Vision and Initiative Alignment
Expand |
---|
How does this proposal fit into our overall vision and which specific initiative does this proposal align with and how? |
The Problem
Expand |
---|
What problem are we trying to solve? and why it important to our customers and/or to Unified Compliance? |
Goals
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
What does success look like? What metrics can we effect and why it is important to affect those metrics?
|
...
List any open questions that come to mind throughout the lifecycle of this initiative.
Question | Answer | Date Answered |
---|---|---|
Framework
Provides high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success.
...