As a Product Owner, the goal is to define a clear product backlog for the MVP release. This is broken into Epics (Large Features) and corresponding User Stories with Acceptance Criteria to guide development.

​

• Epic: User Registration & Authentication

  • User Story 1: OTP-Based Registration & Login: As a new user, I want to sign up and log in using my phone number and OTP, so that I can quickly access the app without remembering passwords.

  • Acceptance Criteria:

    • User enters a valid phone number and receives an OTP.

    • OTP is auto-filled if permission is granted; else, user enters it manually.

    • If OTP is incorrect, an error message is shown.

    • If OTP is correct, user proceeds to profile setup.

    • App securely stores authentication tokens for session management.

 

• ​Epic: Ride Booking

  • User Story 2: Select Pickup & Drop Location: As a rider, I want to enter my pickup and drop-off locations, so that I can book a ride.

  • Acceptance Criteria:

    • Users can manually enter locations or select from a map.

    • Recent and saved locations are available for quick selection.

    • If an address is incomplete, the app suggests corrections.
       

  • User Story 3: Fare Estimation & Ride Confirmation: As a rider, I want to see the estimated fare before booking, so that I know the expected cost.

  • Acceptance Criteria:

    •  The app calculates the estimated fare based on distance.

    • Fare breakdown is displayed (base fare + per km charge).

    • Surge pricing is not included in MVP.

​

• User Story 4: Ride Request & Driver Matching: As a rider, I want to request a ride and get matched with a driver, so that I can start my journey.

• Acceptance Criteria:

  • Once confirmed, the system finds the nearest available driver.

  • If no driver is available, a retry mechanism is triggered.

  • Rider receives driver details upon match.

  • Rider can cancel within 30 seconds without penalty.

​

​

• Epic: Ride Execution

  • User Story 5: Driver Navigation & Arrival: As a driver, I want to navigate to the pickup location, so that I can reach the rider on time.

  • Acceptance Criteria:

    • Driver gets a notification for a new ride request.

    • Upon acceptance, Google Maps navigation opens with the route.

    • ETA is displayed for both rider & driver.

    • If a driver cancels, the ride request is sent to another driver.

​

​

• User Story 6: Start & Complete Ride: As a driver, I want to start and end the ride properly, so that the fare can be calculated.

• Acceptance Criteria:

  • Driver swipes “Start Ride” only when at the pickup location.

  • Rider is notified when the ride starts.

  • Driver swipes “End Ride” only at the drop-off location.

  • The app calculates the final fare.

​

​

• Epic: Payments

  • User Story 7: Cash & UPI Payments: As a rider, I want to pay via cash or UPI, so that I have flexibility in payment options.

  • Acceptance Criteria:

    • After ride completion, payment screen appears.

    • Cash option confirms ride completion instantly.

    • UPI (Google Pay, Paytm, PhonePe) option triggers a payment request.

    • Confirmation message is shown upon successful payment.

​

• Epic: Ratings & Feedback

  • User Story 8: Rate Driver & Provide Feedback: As a rider, I want to rate my driver and leave feedback, so that I can share my ride experience.

  • Acceptance Criteria:

    • After ride completion, the app prompts for rating (1-5 stars).

    • Optional text feedback box is available.

    • If 1-2 stars are given, the app asks for a reason.

    • Drivers also rate riders, impacting future ride requests.

​

​

• Epic: Driver Earnings & Payouts

  • User Story 9: Driver Wallet & Payout System: As a driver, I want to track my earnings and withdraw funds, so that I can get paid for my work.

  • Acceptance Criteria:

    • Drivers see a daily/weekly earnings summary.

    • Minimum withdrawal amount is set (e.g., ₹500).

    • UPI is used for instant payouts.