Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

PRD (product requirements document)

Status
Review
Version
1.0.0
Authority
Not stated
Applies to
Core
Markdown source

Definition

A PRD (product requirements document) is the requirements specification of a product written from the product side: the problem, the scenarios, the functional and quality requirements with stable ids, the acceptance criteria, the constraints and assumptions, and a list of what is out of scope. It is kept as one living file that the team updates as it learns.

PRD and SRS (software requirements specification) name the same discipline from two sides: the first is written for the product, the second for the engineers who build it.

Example

A table row such as FR-4 | When a visitor submits the search form, the site MUST show matching items, best first. | S-B. In a Hub project the PRD is project/PRD.md, written from templates/prd.md.

Sources