| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | ||||||||||||||||||||||||||
2 | Done, Released to Production | |||||||||||||||||||||||||
3 | Work In Progress | Last updated date | ||||||||||||||||||||||||
4 | 7/Jun/2023 | |||||||||||||||||||||||||
5 | ||||||||||||||||||||||||||
6 | Domain | Q1 - Jan, Feb, Mar 23 | Q2 - Apr, May, Jun 23 | Q3 - Jul, Aug, Sep 23 | Q4 - Oct, Nov, Dec 23 | Future - Depending on Ecosystem Maturity | ||||||||||||||||||||
7 | Optimisation: Cost & Conversion | Map Cost Optimisation Addressing the need for cost savings and efficiency by a) using open source maps wherever possible without impacting the experience significantly b) reducing the number of expensive map apis used by optimising caching #lessMapsCost, #affordable | Map Cost Optimisation Addressing the need for cost savings and efficiency by a) almost eliminating the cost of maps for repeat rides b) use of low-cost and effective alternate options where we can't use open source maps and apis as is. #lessMapsCost, #affordable | Open Source Maps Contribution Addressing the need for cost savings and efficiency by optimizing maps cost and experience by contributing to the open source maps and apis with traffic, auto route and other useful information #lessMapsCost, #affordable, #enhancedOpenSourceMaps | Open Source Maps Contribution Addressing the need for cost savings and efficiency by optimizing maps cost and experience by continuing to contribute to open source maps and enabling the drivers and customers also to contribute to it. #lessMapsCost, #affordable, #enhancedOpenSourceMaps #communityParticipation | |||||||||||||||||||||
8 | Priority Areas Addressing the need for Autos to be a preferrable last-mile connectivity options by highlighting priority areas such as Metro, Hospital, Schools etc. This will enable the drivers to not cancel priority rides as per their commitment. Also, disabling nominal driver request for these priority areas upto certain distance (3km) will make this a special fare product. #betterRideAcceptance, #lessCancellations | Cloud Cost Optimisation Addressing the need for cost savings and efficiency by optimising the cloud cost by a) improving the performance of the application b) optimising & reducing the usage of data stores c) efficient auto scaling for better resource utilisaiton #lessCloudCost, #affordable | Cloud Cost Optimisation Addressing the need for cost savings and efficiency by optimising the cloud cost by a) further improving the performance of the application b) optimising the data analytics cost c) continuing to optimise the usage of data stores #lessCloudCost, #affordable | EV Battery Swapping/Charging Locations Addressing the need for supporting the EV move by a) showing battery swapping stations within the app b) allocating rides based on the battery swapping stations c) explaining the benefits of EV #moveToEV, #batterySwapping, #lowCost | ||||||||||||||||||||||
9 | Customer - Driver Matching Optimisations Addressing the need for better acceptance by a) increasing the number of search batches with lesser search radius in each batch b).including a driver who is already in namma yatri ride but about to drop c) adding an option to accept with a 5-10 minutes wait time d) improving the intelligence of choosing the drivers to broadcast e) showing ETA etc #betterRideAcceptance | Saved Preferences of Customers Addressing the need for improving customer convenience and reducing drops by saving the driver choice preferences such as faster, nearer or cheaper driver and automating the choice based on the saved preference. #affordable, #choiceOfDrivers | Ride Batching Addressing the need for more efficient and cost-effective transportation by enabling riders to share rides and split the cost with other passengers going in the same direction. #win-win, #lessForCustomersMoreForDrivers, #affordable | |||||||||||||||||||||||
10 | In-App Chat with Driver Addressing the need for better communication between riders and drivers by enabling in-app messaging for real-time updates especially before the ride start. #convenientCommunication, #lessCancellations | Simplified Driver Onboarding & Payments Addressing the need for a faster and smoother onboarding process for new drivers by a) simplifying the UX, documentation and verification process b) Adding the payment options for drivers to subscribe to the product #selfServiceOnboarding, #automatedVerification, #subscriptionPayment | Seamless Payment Options Addressing the need for convenient and secure payment options by allowing riders to easily pay for rides through payment options such as UPI, UPI Auto Pay, cards etc | |||||||||||||||||||||||
11 | ||||||||||||||||||||||||||
12 | Growth & Engagement | Open Data 2.0 Addressing the need to make transportation data more transparent by enhancing the open data website to include a) granual regions - wards in addition to assembly constituency b) historical trends c) conversion funnel #openData, #citizenParticipation | SDK for integrating in other apps Addressing the need for enabling booking through other apps by making namma yatri an SDK #interOperability, #bookFromOtherApps | Multimodal Transport - Phase II Addressing the need for more flexible and efficient transportation options by integrating and supporting multiple modes of transportation, such as cabs along with metro and auto. #nammaYatriCabs | Multimodal Transport - Phase III Addressing the need for more flexible and efficient transportation options by integrating and supporting multiple modes of transportation, such as a) bus along with autos, cabs and meto service b) Trip stitching multiple options for a route #nammaYatriBus, #multimodal, #tripStiching | |||||||||||||||||||||
13 | Multi City Support Addressing the need to make the app available easily as an extension in other cities by a) Pilot that is in progress in Kolkata. b) Merge of Kochi with Namma Yatri code base a) Allowing another city that are in conversations to be added easily | Express Booking Option Addressing the need to support booking first & allocating the driver next in usecases such as prepaid, airport queue etc by a) allowing express booking as a separate option and/or within a geo-fence b) allowing a coordinator to assign a driver with a rider where the driver might not have smart phones | ||||||||||||||||||||||||
14 | In-app Messaging Addressing the need to be in constant communication with the drivers to inform & train them without limitations by a) enabling an in-app messaging platform for drivers b) adding views and likes as a part of the messages c) enabling drivers to make and post training videos themselves with maker - checker d) automating posting daily messages such as top 10 drivers #constantCommunication, #driverTraining, #betterDriverEngagement | Customer Service Skill Development Training Addressing the need for driver skill development and upskilling that offers in-app training modules and resources for drivers to improve their customer service skills. #bestCustomerService, #driverTraining | Support for Multimodal Transport - Phase I Addressing the need for more flexible and efficient transportation options a) by integrating and supporting multiple modes of transportation, such as meto services along with autos b) enabling trip stitching to enable one booking for both metro and auto #multimodal, #tripStiching, #autoPlusMetro | Booking with Web / WhatsApp Addressing the need for easier and faster booking by enabling riders to book rides directly through Web / WhatsApp, eliminating the need for a separate app. #bookFromWeb, #bookFromWhatsApp | ||||||||||||||||||||||
15 | Referral Program Enhancements Addressing the need to enable drivers to refer customers by a) Linking a referral code & QR pasted in the auto with the driver b) Showing the number of customer referred and activated - rides taken c) adding options to claim different gifts based on milestone #driversReferCustomers, #driverOwnership | Earnings Screen 2.0 Addressing the need for a more comprehensive and detailed earnings screen for drivers to track their income and performance metrics. #performanceEvaluationTools, selfMotivation | Driver Leaderboard Addressing the need for gamification and incentivization by implementing a leaderboard to showcase and reward the top-performing drivers based on completed trips, customers referred and other metrics. #driverLeaderBoard, #motivation | Financial Well-being MVP Addressing the need for financial education and management support for drivers that provides access to financial planning tools, savings options, insurance and other financial resources to help drivers achieve greater financial stability and well-being. #driverFinancialStability, #savings, #insurance | ||||||||||||||||||||||
16 | ||||||||||||||||||||||||||
17 | Safety & Reliability | Enchanced Safety Features Addressing the need for safer transportation by implementing advanced safety measures such as real-time GPS tracking, driver verification, emergency response options, peer feedback on safety #safeRides | Automatic Repeat Rides Addressing the need for reliable repeat rides and guaranteed income to the drivers by a) automatically scheduling repeat rides b) allowing customers to choose a driver for repeat rides #repeatRides, #guaranteedIncome | Drive to Addresses Addressing the need for drivers to find potential riders in the addresses the drivers like to ride #driverPreference, #gotoAddresses | Show Demand Hotspots Addressing the need for drivers to find potential riders and increase their earnings by displaying real-time demand hotspots in the driver app. #hotspots | |||||||||||||||||||||
18 | Support for Scale Addressing the need for supporting scale & increase in traffic by a) vertical scaling b) supporting auto scale c) enhaced monitoring & alerts #autoScale | Voice Of Customer Addressing the need for better customer support by providing better resolutions, adding issues reported in the public forum & addressing them fully. #voc, #openCustomerTickets | Booking On Behalf of another person Addressing the need for greater flexibility and convenience by allowing users to book rides on behalf of another person, such as a family member, friend, or coworker who may not have access to the app or internet. | Namma Yatri Lite (works without internet) Addressing the need for reliable and accessible transportation information and booking services in areas with limited or no internet connectivity. Namma Yatri Lite aims to provide a solution for people who live in remote areas or have limited access to the internet to be able to book transportation and access essential travel information without the need for a reliable internet connection. | ||||||||||||||||||||||
19 | Improved Fare calculation Accuracy Addressing the need for calcualting fare accurately based on the actual distance travelled by a) Taking customer location information b) Provide Recalculate Options to the drivers c)verify accuracy of location updates & accordingly calculate or fallback to estimate #fareCalculationAccuracy | Route Optimisation Addressing the need for accurate route prediction with flexibility and convenience by a) estimating based on the shortest distance until the time is too high b) Nudging the driver to take same route by giving way points c) reroute configs to be based on distance than time d) allowing riders to add multiple stops during their ride. #predicatablePrice, #flexibleRides | Enhanced Digital Fare Meter - Phase II Addressing the need for more accurate and transparent fare calculations by implementing advanced fare metering technology that takes into account factors such as distance, time, traffic, and demand. #phoneAsMeter | Driver Trust Score Addressing the need for improved safety and reliability by implementing a driver trust score that takes into account factors such as driver ratings, completion rates, and compliance with safety protocols. | ||||||||||||||||||||||
20 | Improved Location Update Accuracy Addressing the need for getting location updates more frequently & accurately by a) enabling the health check service to restart locaiton updates b) implementing gRpc #locationUpdateAccuracy | Enhanced Digital Fare Meter - Phase I Addressing the need for more accurate and transparent fare calculations by implementing advanced fare metering technology that converts mobile into a meter #phoneAsMeter | Customer Trust Score Addressing the need for improved safety and reliability by implementing a customer trust score that takes into account factors such as rider ratings, payment history, and compliance with safety protocols. | |||||||||||||||||||||||
21 | ||||||||||||||||||||||||||
22 | Change Log | |||||||||||||||||||||||||
23 | Date | Change Log | By | |||||||||||||||||||||||
24 | 16-Mar-2023 | First version of Product Roadmap | Shan, Daya, Mags | |||||||||||||||||||||||
25 | 25-Mar-2023 | - Updated the status - Moved SDK to Q2 from Q3 as there is interest from other apps - Moved multimodel to Q3 from Q2 to accomodate SDK development - Added the changelog section - Added multi city support in Q1 - created a future section and moved EV and Booking without internet to it | Mags | |||||||||||||||||||||||
26 | 7-Jun-2023 | - Updated the status | Daya | |||||||||||||||||||||||
27 | ||||||||||||||||||||||||||
28 | ||||||||||||||||||||||||||
29 | ||||||||||||||||||||||||||
30 | ||||||||||||||||||||||||||
31 | ||||||||||||||||||||||||||
32 | ||||||||||||||||||||||||||
33 | ||||||||||||||||||||||||||
34 | ||||||||||||||||||||||||||
35 | ||||||||||||||||||||||||||
36 | ||||||||||||||||||||||||||
37 | ||||||||||||||||||||||||||
38 | ||||||||||||||||||||||||||
39 | ||||||||||||||||||||||||||
40 | ||||||||||||||||||||||||||
41 | ||||||||||||||||||||||||||
42 | ||||||||||||||||||||||||||
43 | ||||||||||||||||||||||||||
44 | ||||||||||||||||||||||||||
45 | ||||||||||||||||||||||||||
46 | ||||||||||||||||||||||||||
47 | ||||||||||||||||||||||||||
48 | ||||||||||||||||||||||||||
49 | ||||||||||||||||||||||||||
50 | ||||||||||||||||||||||||||
51 | ||||||||||||||||||||||||||
52 | ||||||||||||||||||||||||||
53 | ||||||||||||||||||||||||||
54 | ||||||||||||||||||||||||||
55 | ||||||||||||||||||||||||||
56 | ||||||||||||||||||||||||||
57 | ||||||||||||||||||||||||||
58 | ||||||||||||||||||||||||||
59 | ||||||||||||||||||||||||||
60 | ||||||||||||||||||||||||||
61 | ||||||||||||||||||||||||||
62 | ||||||||||||||||||||||||||
63 | ||||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||
68 | ||||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||
71 | ||||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | ||||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | ||||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | ||||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 |