Milestones
Assumption that the Loyalty programme mechanics has been locked as part of Project 1. Define the Loyalty programme
Milestone | Name | Outcome | Work required | How to test | Owner | Status |
---|---|---|---|---|---|---|
1 | Scope defined | Scope of the project has been agreed between BK DE, Smoothr and RBI |
|
| Anna | IN PROGRESS |
2 | Test environment ready | A testing environment has been provided to Smoothr for them to develop and test against |
|
| Valentina | NOT STARTED |
3 | Integration developed | Integration from Smoothr to RBI Loyalty (via Loyalty Middleware) is developed and tested in Staging environments. |
|
| Valentina Silvia | IN PROGRESS |
4 | Integration readiness (Staging) | The Smoothr > RBI Loyalty integration has been thoroughly tested by the business in Staging and all identified issues have been fixed |
|
| Silvia BK DE: TBC | NOT STARTED |
5 | Personalised offers on Kiosk | Smoothr kiosks are able to show and allow users to redeem personalised offers |
|
| Valentina | NOT STARTED |
6 | Integration readiness (Production) | New version of Smoothr Kiosk (loyalty-enabled and with personalised offers) is working in Production in at least one store. |
|
| Silvia BK DE: TBC | NOT STARTED |
Note: going live with loyalty will happen on a different project because we need to coordinate Mobile ordering and In-store (all of the Kiosk providers plus Toshiba) [insert link]
Notes
In order to show Personalised Offers in the Kiosk:
Smoothr will need to start sending the
loyalty id
of the offer selectedThis means the
loyalty engine id
, not thesanity id
(what they use today to query rewards and offers). We may need to teach them how to find this value and not mix it up with the config offer's loyalty id/sanity id
RBI will need to expose this new field and when Smoothr sends it, we use the new id they send to tell engine what offer is being redeemed