Note |
---|
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
Table of Contents |
---|
Definition
Status |
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
RBIberia Owner
| |||||||||
RBIberia Owner | |||||||||
RBI Owner | |||||||||
Epic link |
| ||||||||
Design task link |
| ||||||||
Figma link |
❓ Open questions
Info |
---|
We need to constantly make this section empty. |
Requirements
Problem statement
Scope:
1 - Update colors on “Bonus Crowns“ and “Bonus Earned“
Acceptance criteria
Success metrics
🤔 Assumptions
Premises
Solution
Scenarios
Info |
---|
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]