Product Requirements Document

A lightweight PRD that explains the problem, the goal and the scope before the solution.

When to use itBefore a team starts building anything larger than a couple of sprints.
  1. Problem

    Who has the problem, how you know, and what it costs them today.

  2. Goals and non-goals

    What success looks like, with metrics. What this work will deliberately not do.

  3. Users and use cases

    The primary user and the three to five jobs they need to get done.

  4. Requirements

    Must, should and could. Write them as user needs, not UI.

  5. Open questions

    Unknowns, owners and the date you need an answer.

  6. Release plan

    Milestones, rollout approach and how you will measure the release.