Agile in Zomato like Apps
Learn how agile methodology is used in food delivery apps
Let’s say you are the PM at Zomato and Zomato is adding new features like rate/review restaurant, filters for search, online ordering, etc ( assuming these features are currently not there ) in line for next releases.
Considering, we have five steps: ideation, design, implementation, testing, and deployment. And let’s assume we have 3 developers, 1 Designer, 1 QA, and 1 scrum master that is our Product Manager in our team. Now, let’s see how the development of these features is done in an incremental and iterative way.
Day 1: Sprint 1
First, we will have a team meeting to allot the effort points and priority to all this product backlog made by the Scrum Master ( or Product Manager ). After discussion we come to the following results:
A. Epic: Rate/Review the restaurant
User stories:
As a user, I can rate the restaurant on the restaurant page by selecting stars. ( Effort points: 40 (10 designer+ 20 developer+ 10 QA, priority: P3)
As a user, I can review the restaurant on the restaurant page by entering my experience in a text box and then publishing it as a comment. ( Effort points: 50, priority: P4 )
B. Epic: Filters for search
User stories:
As a user, I can filter the search results based on the distance, price, offers, veg, and non-veg ( effort points: 40, priority: P3)
As a user, I can enable and reset filters on my search results.( effort points: 30, priority: P4)
C. Epic: Online ordering
User stores:
As a user, I can order my food online by selecting a dish and entering my address. ( effort points: 60, priority: P1)
As a user, I want the option to pay via a payment gateway that has options like Credit/debit card, UPI, e-wallets, etc. ( effort points: 100, priority: P1)
As a user, I want a screen where I can view my current order status ( effort points: 50, priority: P2)
As a user, I want a screen to view my past orders. ( effort points: 60, priority: P2)
As a user, I want the number of restaurant and delivery partners for additional instructions or contacting purposes. ( effort points: 40, priority: P3)
As a user, I would like to know the accurate ETA of my order. ( effort points: unknown, priority: P3)
Day 2: Design Sprint ( 3–4 days )
- The first version of UI designs of all the 3 epics will be done in this sprint.
Day 8 : ( Week 2 — Week 5) — Development Sprint Starts
Developers start working on each epic separately.
With help of Continuous Integration and Development code testing is also done regularly with the QA on minor releases.
Day 36: Week 6
- Testing is done by QA
Day 43: Week 7
Deployment on the production server, done, cheers!
