Roadmap - 2024 - Q3
- Pereira, Filipa (Deactivated)
- Garozzo de Sobral, Wellington
- Raphael Ferreira Gomes
Document Status | done |
|---|---|
Document Owner(s) | @Pereira, Filipa (Deactivated) Paula winter |
Contributors | @Raphael Ferreira Gomes , @Taquari Fagundes, Andre |
High-level estimates Eng. team: include technical discovery, refinement and development.
Small (S) - up to 2 sprints (2 to 4 weeks)
Medium (M) - 3 to 4 sprints (6 to 8 weeks)
Large (L) - > = 5 sprints (10 weeks or more)
High-level estimates Design team: include design planning.
Small (S): 1 week
Medium (M): 2 weeks
Large (L) : > 2 weeks
These estimates do not include QA testing, production release and roll out plan.
Priority | Title | IREQ | Discovery status CLEAR PENDING INFO NO DETAILS YET | Description | Stakeholder | INTL Team (to align with) | Comments | High level estimates Engineering
| High-level estimates Design
| Status |
|---|---|---|---|---|---|---|---|---|---|---|
1 | Reduce address errors while placing the order | https://rbictg.atlassian.net/browse/IREQ-2336 and https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-1655 | PENDING INFO Metrics analysis to measure the current impacts. | Issue happening mainly in Portugal, with orders being cancelled due to wrong address issues. Inform customers that they’re far from the address. | eCommerce | Menu & Restaurant Delivery | Some customer choose the incorrect address as the information wasn’t filled properly. Many complains are not registered on customer support, because they’re managed directly with the restaurant. | L (very uncertain solution) | L Discovery is necessary (ex: user testing) | In DEV |
2 | MB way payment method | CLEAR | Add a new payment method, which is very important for this market. | BK PT Finance | Transactions |
| M | M | In DEV | |
3 | Order status update | https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-2365 | PENDING INFO Waiting for metrics to understand current frequency. Would we be able to change the operational process? | Currently, it’s possible to change order status from canceled to delivered (and vice-versa). Use cases:
| BK ES Operations | Transactions | As the EMEA system only receives one event update, the order status is not accurate and this also affects the refund processing Review which canceled cases shouldn’t automatically trigger refund.
| L Considering status review is already delivered by INTL team | L | Feature cancelled. INTL did not accept the change. |
4 | Admin tool - Improve loyalty offers assignation process | CLEAR | Be able to search by key words to easily / faster find the offers available. | Customer support | Loyalty |
| S (4 Weeks) | S | Dev Done Feature Flag to be activated on 17/09 for BK PT, BK ES, PLK ES | |
5 | Admin tool - add initial and final loyalty balance information | cleAR | Identify the initial and final total loyalty balance, after each transaction. Currently only the transaction balance is available | Customer support | Loyalty |
| M (8 weeks) | M | In DEV | |
6 | Payment improvements - error messages improvement | CLEAR it’s necessary to map existing error messages to identify the improvement opportunities | Map and improve the error messages to increase purchase conversion. | eCommerce | Transactions | This was on Q2 roadmap and was delayed for Q3. Possible synergy with an initiative managed by the fulfilment team. To be reviewed. | M | M (if we have the information about the existing errors) | In Refinement Friendly messages were defined but IBERIA needs to review, will happen on 16/09 | |
7 | Allow payment methods configuration on DOP | pending info Prioritization is being reviewed. Rules must be detailed. Can we consider only payment methods available in Iberia for now? | Be able to activate/deactivate the payment methods. Rules: at least one online payment method should be active. Restaurants want to autonomously manage the payment methods available.
| Operations | Transactions | This was on Q2 roadmap and was delayed for Q3. This is aligned with INTL strategy. Requirements and solution should be reviewed in advance to ensure a proper alignment.
| L | L | In DEV | |
| Bag Fee |
|
|
|
|
|
|
|
| Dev Done Feature Flag to be activated on 17/09 for BK PT
What about BK ES and PLK ES |
| Cash Limitation |
|
|
|
|
|
|
|
| Dev Done Feature Flag to be activated on 17/09 BK PT, BK ES (rules 1, 2 and 3) and PLK ES (rules 1 and 2) |
| Payment Improvements - Block User from closing windows |
|
|
|
|
|
|
|
| Dev Done Feature flag activation will depend on INTL fixing a bug that leaves Users on an infinite loop in the Payment Page Once this bug is fixed the flag will be planned to be activated |
| Fraudulent User Blocking |
|
|
|
|
|
|
|
| Dev Done Feature Flag to be activated on 17/09 for BK PT, BK ES, PLK ES |
| Visual Info of accepted cards |
|
|
|
|
|
|
|
| Dev Done Feature Flag to be activated on 17/09 for BK PT, BK ES, PLK ES |
| Service and Delivery fee |
|
|
|
|
|
|
|
| Dev Done Feature Flag to be activated on 17/09 for BK ES
What about BK PT and PLK ES? |
|
|
|
|
|
|
|
|
|
|
|
Capacity Limit |
| |||||||||
8 | Complete your combo (Completa tu menu) | https://rbictg.atlassian.net/browse/IREQ-1298 and https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-1655 | pending info More details here | Be able to evolve the cross-selling capabilities, adding items to a menu. | Marketing | Menu & Restaurant | This was on Q2 roadmap and was delayed for Q3. Dependency from INTL team Q2 developments. | L | L |
|
9 | Admin tool - add information of customer tier | clear | Be able to check the current customer tier (king & super king) Be able to check when it changed. | Customer support | CRM | We can get customer tiers information from here: https://www.google.com/url?q=https://rbictg.atlassian.net/wiki/spaces/COG/pages/4041605275/Loyalty%2BOffers%2BEvents%2BConversion%23Loyalty-Tiers&sa=D&source=editors&ust=1718362213518545&usg=AOvVaw3To5kH_Eok_dMY5lh6gCDo | L (12 weeks) | M |
| |
10 | Item order restrictions | https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-2366 | clear | Customers under 16/18 years old can’t purchase alcoholic/energetic drinks during certain periods and in specific regions. | Compliance | Menu & Restaurant | It’s important that we show a consent page. Configure sanity: restaurant details (Regions) Persist data to track orders with consent | L | L |
|
11 | Improvements on beverage QR ordering | https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-2367 | clear | Mobile ordering should show QR code on app and web If customers choose any mobile ordering delivery method, the QR isn’t sent, but customers must use it to access drinks in the restaurant. Web scope must be considered too, which was not in the initial deliverable. | eCommerce | Fulfilment |
|
| M |
|
12 | Cash limitations events | https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-2368 | clear | Be able to track:
| eCommerce | Fulfilment |
|
| S |
|
13 | Manually organize payments methods | https://rbictg.atlassian.net/servicedesk/customer/portal/53/IREQ-2304 | no details yet | Be able to change payment methods prioritization. | Marketing | Transactions | This was on Q2 roadmap and was delayed for Q3. |
|
|
|
14 | Payment improvements - secure payment |
| clear | Better communicate that the customer is waiting for the secure payment confirmation. | eCommerce | Transactions | This was on Q2 roadmap and was delayed for Q3. |
|
|
|
15 | Evolve the feature: Activate/ Deactivate products on DOP |
| pending info | The restaurant might require to stop selling specific items. Requirements:
| Operations | Menu & Restaurant |
|
| L
|
|
Support documents:
Admin tool requirements: https://docs.google.com/spreadsheets/d/1-rhdorDhPsSGoVbzDnikjt8nH2D4iz3-TLsrvk9o4mc/edit?gid=0#gid=0
High-level roadmap with capacity allocation: https://docs.google.com/spreadsheets/d/1ZQFe8m3ljsYPkGI3wvP8vRGgKKOlvN4SIntUp4Puovg/edit?gid=0#gid=0