Introduction
...
| Expand | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
What does success look like? What metrics can we effect and why it is important to affect those metrics?
|
Scope and 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. |
Scope Definition
...
| Expand | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
Describe the product requirements that will fulfill the underserved need(s) starting off with the use cases, then specific functionality.
|
| 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
...
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.
...