The purpose of this product requirements document is to provide an overview to our team of what we intend to do, what the goals are behind the idea, and a general plan for how we will execute. This is a living document, so it can be altered as the team collaborates on our idea and comes up with new approaches and improvements.


Organization:

  1. Overview
  2. JTBD
  3. User Requirements
    1. Parent/Guardian Requirements
    2. Child Requirements
  4. Functional Requirements
  5. Non-Functional Requirements
  6. Requirements Breakdown Table
  7. Wireframe Sample
  8. Assumptions
  9. Risk Mitigation
  10. Success Metrics
  11. Summary

1.  Overview

We are building a ride hailing application that provides a safe and convenient transportation solution for children. Our app is designed to be used by both parents/guardians and children, with a focus on safety and ease of use. The app will allow parents to request rides for their children, track the ride in real-time, and receive notifications once the ride has been completed.

Note: This exercise only includes the order and rider side of the application. Drivers and administration are excluded.

2. Problem Space (Job to be done)

Modern ride-hailing applications like Uber are used globally and trusted to serve a demographic that is independent and teenage +. Currently, there isn’t a trusted solution to transport children that is safe and easy to user for both parents/guardians and children.

As a parent/guardian, I want to safely transport my child so that I can free up more of my own time and know that my child is arriving to his/her activities safe and sound.

3. User Requirements

3a. Parent/Guardian (Parent) Requirements