A structured review record for a proposed feature, covering its purpose, scope, design, delivery needs, and unresolved issues. Use before committing to a feature or story design that needs review across engineering and delivery.
Review detailsIdentify the work, its customer context, and the people preparing the proposal.
Overview and problemExplain the need, relevant background, and reason to act.
Goals and scopeState the outcomes this work must deliver and the conditions for calling it complete.
Out of scopeName related work this proposal does not include.
Proposed designSummarize the main components and how they work together to meet the goals.
TechnologyList the platforms, languages, services, data stores, and supporting components the design needs.
Non-functional requirementsSet measurable expectations for speed, capacity, availability, recovery, data growth, usage patterns, and cost.
DependenciesIdentify work, teams, or expertise this proposal relies on.
Risks and mitigationRecord security, privacy, delivery, and operational concerns, including any need for specialist review.
Open questionsCapture unresolved choices or concerns that could change the design, scope, or delivery plan.
ResourcesLink supporting material reviewers may need, such as backlog items, work records, specifications, or technical references.