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.
Acceptance criteria
Success metrics
🤔 Assumptions
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?
The checkbox text is customized by Sanity tool.
2 - Agreement modal text customized
Currently, the modal texts(sub-title and agreements checkbox) come from the Lokalise (hardcoded).
3 - Animation on Transition between modals
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