Engineering
  • Welcome!
  • First Principles
  • Communication tools
  • Acronyms
  • Vital reading material
  • Engineering Onboarding
    • Onboarding Guide
    • Mobius onboarding Guide
    • Lessons
      • 001 - Function Purity
      • WIP - Shared Mutable State
  • System design & Architecture
    • Introduction
    • Refactoring
    • Architecture Decision Records
  • Meetings
    • Iteration Planning Meetings
    • Daily Standup Meetings
    • Retro meetings (retrospective)
  • Release Engineering
    • Introduction
    • Git commit messages
    • Code reviews & pull requests
    • Trunk-based development
      • Our methodology
    • Service Dependencies
    • Tooling & infrastructure
    • Git commands & workflows
  • Project Management
    • Product Requirements Document
    • Pivotal Tracker
Powered by GitBook
On this page

Was this helpful?

  1. Project Management

Product Requirements Document

PreviousGit commands & workflowsNextPivotal Tracker

Last updated 5 years ago

Was this helpful?

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.

Typically, a PRD is created from a user's point-of-view by a user/client. The requirements are then analyzed by a (potential) maker/supplier from a more technical point of view, broken down and detailed.

References

Wikipedia