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 a 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 finalise the feature by adding any requirements that were not covered by v1.
Scope
1 - Checkbox de market email
On the Agreements modal,
if the user hasn´t checked “Market email“, then show the checkbox on the modal to the user accept it
We should save the user option on the database
Data from mParticle:
How many users saw the agreement modal?
How many users saw the market email checkbox?
How many users accepted the market email checkbox?
2 - Agreement modal text customized
Currently, the modal texts(sub-title and agreements checkbox) come from the Lokalise (hardcoded).
The sanity tool needs to have the texts to be configured and alter on the modal.
3 - Animation on Transition between modals
Following the animations to be implemented on the transaction between the modal agreements and modal agreements text.
Acceptance criteria
Market email on Update Agreement modal
If the user has already had the value as true, the checkbox will NOT be displayed on Agreement modal.
If the user has the value as false or empty, the checkbox will be displayed on Agreement modal.
If the user checks the checkbox on Agreement modal, and clicks on the Continue button, the true value will be saved on the database.
If the user checks the checkbox on Agreement modal, but clicks on the Disagree button, the false or empty value will be kept on the database.
If the user changes from true to false on Settings account user, as the value becomes false, when the user accesses the app and Agreement modal appears again, the checkbox will be displayed.
L&F
Make sure the modal resizes, fitting the height when the checkbox is displayed or not in order to not display a scrollbar.
mParticle
When the Update agreement is loaded, an attribute will be sent to mParticle.
If the user checks the checkbox and clicks on the Continue button, an attribute as true will be sent to mParticle.
If the user does not check the checkbox and clicks on the Continue button, an attribute as false will be sent to mParticle.
If the user checks the checkbox but clicks on the Disagree button, no attribute will be sent to mParticle.
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