Product Requirements Document (PRD)

A Product Requirements Document (PRD) is a requirements document that contains product requirements.

• Context:
  • It can be the output of a Product Requirements Analysis.
  • It can (typically) be read by a Business Owner and by a System Designer.
  • It can holistically describe the role of the Computing System in the facilitation of a Business Process.
  • It can contain: Use Cases, Business Rules, ...
• Example(s):
  • a Chatbot PRD.
  • …
• Counter-Example(s):
  • Market Requirements Document (for a market requirements analysis).
  • Technical Requirements Document.
  • Functional Specifications Document.
  • SWOT Analysis Document (for a SWOT analysis).
  • Product Roadmap.
• See: Product Management Task, Requirements Analysis.

---

---

References

2020

• (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/product_requirements_document Retrieved:2020-12-9.
  • A product requirements document (PRD) is a document containing all the requirements to a certain product.

    It is written to allow people to understand what a product should do. A PRD should, however, generally avoid anticipating or defining how the product will do it in order to later allow interface designers and engineers to use their expertise to provide the optimal solution to the requirements.PRDs are most frequently written for software products, but can be used for any type of product and also for services.

    Typically, a PRD is created from a user's point-of-view by a user/client or a company's marketing department (in the latter case it may also be called Marketing Requirements Document (MRD)). The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down and detailed in a Functional Specification (sometimes also called Technical Requirements Document).

---