Agile in Zomato — a hypothetical PM
Zomato is a pioneer in online food ordering apps present in both web and mobile platform. As a hypothetical Product Manager of Zomato, will explore how to adopt the agile methodology to implement some of the niche features down the line in a few sprints.
As with agile approach, all the to do items are listed, prioritized in backlogs.In planning phase, the features are taken in a release considering the resource constraints, technical dept etc. Let’s analyze some of the epic items.
Rate/Review restaurant: It is an important value proposition to develop this feature. This is to rate a restaurant after ordering the food. The rating is based on few points: — 1. speed of delivery 2. taste 3. Ease of ordering 4. behavior of the delivery boy. There are 2 stages to rate a restaurant. First is immediately after ordering and the next is after receiving the order.
Then the review comes after actually tasting the food. So the user notified for review after three hours as mail, mobile push notification. The notification also would be when the user logs to the respective platform. The user can snooze it or ignore to provide review or ratings.
So, there are two different stages for ratings and review. so let us enunciate the features we deliver in iterations:-
1. As a user, immediately after ordering the food from the app, I would be redirected to a page to rate ( 5 stars) from one to five for ease of ordering experience. The user can ignore by skip hyperlink option on the page.
As a user, immediately after receiving the order, I would be notified via mobile app, email, and the web for rating for below parameters. Each option to rate ( 5 stars) each in a separate page for the app and one page in the web portal.
1. Food Taste
2. Delivery Speed
3. The behavior of Delivery Person.
As a user, three hours after receiving the order, it would be notified via mobile app, email and web portal for reviewing the orders not less than a month old. It would open up a text box with a 500-word limit to enter the text inside. The ratings if entered earlier would also be displayed. The user can ignore by skip hyperlink option on the page.
Filters for search: This is a very important feature to get the user narrow down their requirement from the huge options available on the platform. The filter options should be exhaustive enough for a better user experience. Options are 1. veg/no veg/Jain food options, 2. Distance, 3. delivery time 4. restaurant closed/open 5. delivery charge ( free /paid) in sorted order, 6. pay by cash or online payment ( card/wallet).
Here each option could be taken in the subsequent iterations.
For all the features enumerated above, we do not know how the customer would react to those; so it would all have to go through the prototyping, design, develop and user testing phases in several sprint cycles to validate the initial assumption in a iterative manner. So by end of each release cycle, a little incremental feature could be released. It would result in ease of learning for customers without any disruption.
This is an incremental feature.The online ordering involves the integration of payment gateway to the existing system.It is a feature which should be released in entirety, so cannot be released incrementally in small phases. But it could be developed incrementally and with several internal testing for validating the assumptions, the entire feature could be released. The phases of design sprint could figure out the selection of a 3rd party payment gateway or in-house development of same. The decision to develop the U/X and option to pay by cash as well could be validated with a prototype.
Also note that there is a feature in search filters which is dependent upon online ordering. So the stories are prioritized accordingly so that there is more coordinated and less disruptive features developed and released.