We recommend to use MVP approach to have a balance between business value and smooth roll out of the product. This is also more agile so we will be portioned better to adapt to changes. Along with that, it also benefits the system by mitigating risks, sustainability and strategy alignment.
Following is an example of one of the possibilities to release features into phases. This must be adapted to align with strategic roadmap of the product.
| Functionality Area | Phase 1: MVP | Phase 2: Maturity | Phase 3: Beyond |
|---|---|---|---|
| Booking Entry | Manual entry | Email listener, poller | Users can add other users to their trips |
| Booking Trackers | Manual updates | Automatic updates | Integrate analytics to indicate chances of delays/cancellations for trips, optimize tracking frequency |
| UI | Trip dashboard | Journey Experience Suggestion Integration | Gamification (Review, Survey, Invites) |
| Notification | Booking Time based notification, app notification, email notification | Booking update/cancellation notification, Vicinity notification, SMS | Weather |
| Analytics | Providing raw data with standard support | Extending support for data sharing mechanism (kafka, SFTP, API) | Travel Analytics Factory |
| Integration | GDS, Travel Agencies | Local Transport Systems, Cab services | |
| Help | Travel agency | Local Emergency System |
| 🏠 home |