Feature - Improve component of loyalty program
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
- 4.5 Premises
- 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 empty.
Ā
Ā
Requirements
Problem statement
Acceptance criteria
Success metrics
Assumptions
Scope:
1 - Change the color of the āRewardsā header
2 - Remove the Cards effect from the Rewards component
3 - Create a carrossel based on the quantity of crows
4 - Food image and button with disabled aspects when crows arenĀ“t sufficient to buy the product
Ā
Premises
Ā
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]