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
Definition
Status | IN DEVELOPMENT |
RBIberia Owner | |
RBI Owner |
❓ Open questions
We need to make this section empty constantly.
Requirements
Problem statement
We are going live with the first version of the Agreements feature to support the Popeyes Spain go-live. Due to time constraints, we were not able to finalise every detail. The purpose of this story is to finalize the feature by adding any requirements that were not covered by v2.
Scope
1 - Animation on Transition between modals
Following the animations to be implemented on the transaction between the modal agreements and modal agreements text.
2 - Customize the market email checkbox to sent push notification
Currently, on Checkbox market email the application will send only email and won´t send the push notification when the checkbox is checked.
This functionality haven´t implemented on sing up too.
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]
0 Comments