Glossary
Product Requirements Document (PRD)
A written description of what a product must do, for whom and why, shared by the whole team.
A product requirements document (PRD) describes what a product or feature must do and why: the problem, users, goals, scope and requirements. It gives product, design, engineering and stakeholders a shared reference before building starts.
A useful PRD states goals and non-goals, lists requirements as user stories with acceptance criteria, and records risks and open questions. It describes the what and the why, and leaves the how to the team.
It is a living document. Changes after sign-off should be tracked, ideally through a change request, so scope and cost stay visible.
Start in 60 seconds
Put this to work on your project.
Get an AI-assisted, architect-reviewed scope, cost range, and timeline. Free, no login.