Writing a PRD is a crucial part of the planning process for any product team. Investing time into writing clear PRDs help your team, executives, and stakeholders align on the "why" and "how" of achieving product success.
Depending on if you're a waterfall or agile team, the document will be more static or dynamic (respectively).
A PRD will include:
- Why you're building a product (purpose & value)
- The features/functions that fulfills the value
- Relevant user stories for justifying requirements
- Basic prioritization to give readers an idea of how the project will shape up
- Defined success metrics (select from the many available
on this website).
- Relevant mock-ups, prototypes at various levels of fidelity
Great PMs should know that a good PRD isn't necessarily an extremely detailed one. Knowing which areas should be more vague/more detailed will keep the team focused on varying levels of details throughout the project.
