...
| Expand | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
What does success look like? What metrics can we effect and why it is important to affect those metrics?
|
Scope and Features Requirements
| Expand | ||
|---|---|---|
| ||
The intent of this section is for the following: Scope Definition: defines the scope of the proposed product (or features), including what will and will not be included helping manage expectations and focus development efforts. Guideline for Development: provides detailed information on the product’s features, functionalities, user flow, and interface to guide the development team in building the product. Framework: provides high-level evaluation criteria for alternative solutions (build, buy, partner) to evaluate different routes to success. |
| Expand | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
Describe the product requirements features that will fulfill the underserved need(s).
OR:
|
| 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.
|
| Expand | ||||
|---|---|---|---|---|
| Link to mockups, prototypes, or screenshots
| |||
If we have them, link to:
| ||||
| Expand | ||||
| ||||
Links to user journeys, process flow, or other diagrams
|
| 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 | ||
|---|---|---|
| ||
Provide a high-level evaluation criterion why we would not build in-house but outsource. for alternative solutions (build, buy, partner) to evaluate different routes to success. |
...
| Expand | ||
|---|---|---|
| ||
The intent of this section is for the following: Monetization: Financial impact this product will introduce (if any) Risk Mitigation: Identifies potential technical risks and propose mitigation strategies. 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. |
...
| Expand | ||
|---|---|---|
| ||
Will this product be part of an existing subscription or an add-on? Will this product be usage based or part of a subscription? |
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
Identifies If applicable, identifies potential technical risks and propose mitigation strategies.
|
...
| Expand | ||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||
This section is a reminder to the product team to make sure all relevant stakeholders are involved as necessary.
|
...