Feature - Headers consistency
- Bandoch dos Santos, Diego
This 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
- 5 Solution
- 5.1 Scenarios
- 5.1.1 Scenario 1: xxx
- 5.2 Design
- 5.1 Scenarios
- 6 Development
- 7 Release
Definition
Status | NOT STARTED IN DESIGN IN DEVELOPMENT COMPLETED |
RBIberia Owner |
|
RBI Owner |
|
Open questions
We need to constantly make this section become empty.
Requirements
Problem statement
Review why headers do not follow a strategy (some are white, some are black) proposal is to do all white
Acceptance criteria
Success metrics
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]