Feature - Template (deprecated)
This is a template that should be used to document each feature. It’s meant to be easy, not prescriptive - change it at will!
Table of contents
- 1 Table of contents
- 2 Definition
- 3 Open questions
- 4 Requirements
- 4.1 Problem statement
- 4.2 Acceptance criteria
- 4.3 Success metrics
- 4.4 Assumptions
- 5 Solution
- 5.1 Scenarios
- 5.1.1 Scenario 1: xxx
- 5.2 Design
- 5.1 Scenarios
- 6 Development
- 7 Release
Definition
Status | status:NOT STARTED status:IN DESIGN status:IN DEVELOPMENT status:COMPLETED |
RBIberia Owner |
|
RBI Owner |
|
Open questions
We need to constantly make this section empty.
Requirements
Problem statement
Acceptance criteria
Success metrics
Assumptions
Solution
Scenarios
Note: these are high-level scenarios that must pass testing before we can release the feature. They should also be used to drive design. Note that we do not specify user interface details in these steps - that is deliberate so that we focus on the process and not on the UI since the UI can change throughout design and development.
Scenario 1: xxx
Steps | Expected results |
---|---|
Do this | Expect that |
Design
Figma design here: [insert link]
Development
Release
, multiple selections available,
Related content
TEMPLATE [Opportunity] Feature
TEMPLATE [Opportunity] Feature
More like this
[DRAFT] INTERNAL TEMPLATE
[DRAFT] INTERNAL TEMPLATE
More like this
[Solution] Email Update in the Guest App
[Solution] Email Update in the Guest App
More like this
[Discovery Plan] Block user from closing window
[Discovery Plan] Block user from closing window
Read with this
[Solution] Admin tool - offer assignment improvement
[Solution] Admin tool - offer assignment improvement
Read with this
[Solution] Block user from closing window
[Solution] Block user from closing window
More like this