Introduction
| Expand |
|---|
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 | ||
|---|---|---|
| ||
List the known features that are out of scope for this project or might be revisited at a later time. As is case with the assumptions, it is important to list these out so that architects and engineers can plan accordingly for these later updates.
|
Guideline for Development
...
| Expand | ||
|---|---|---|
| ||
Link to mockups, prototypes, or screenshots related to the requirements. |
| Expand | ||
|---|---|---|
| ||
Links to user journeys, process flow, or other diagrams related to the requirements. |
| Expand | ||
|---|---|---|
| ||
If this project is a component to other areas or an update to an existing product, specifically call out where this product will interact with other areas. |
| Expand | |||
|---|---|---|---|
| |||
List any open questions that come to mind throughout the lifecycle of this initiative.
|
...
Framework
...
| Expand | ||
|---|---|---|
| ||
Provide a high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success. |
Milestones and Launch Checklist
| Expand |
|---|
The intent of this section is for the following: Launch Readiness: launch checklist including high-level go-to-market plan to ensure cross-departmental alignment. High-level Messaging: Includes Unique Selling Proposition (USP) raising visibility of the proposed solution’s value proposition. Risk Mitigation: Identifies potential risks and propose mitigation strategies. Subscription / Pricing / Billing Impacts: Financial impact this product will introduce (if any) |
| Expand | ||
|---|---|---|
| ||
Milestones and launch checklist including high-level go-to-market plan to ensure cross-departmental alignment. |
| Expand | ||
|---|---|---|
| ||
Includes Unique Selling Proposition (USP) raising visibility of the proposed solution’s value proposition. |
| Expand | ||
|---|---|---|
| ||
Identifies potential risks and propose mitigation strategies. |
| Expand | ||
|---|---|---|
| ||
Describe any financial impact this product will introduce (if any) |
Additional References
| Expand |
|---|
List and link to any other reference sites, documents … that might be important to the reader. |