How to write a PRD document

prod_req

 

At the high level product requirements development must be:
1. customer needs driven
2. every key requirement should ideally be contributing to creation of some sort of differentiation and
3. gathering should be done collaboratively ie. not only by product managers but in a team with other business units stakeholders

From what I have seen – the most common mistakes people make are not in the points 1 and 2 but in point 3.

Development of PRD should be a very detailed and involved process – involved in a sense that you should not be writing in alone.
Most of the time it’s the corporate product development framework that’s not really set up properly to allow this to happen smoothly – for example you may have mismatching KPIs for product and IT groups which lead to lack of collaboration or your business processes are not properly documented so key stakeholder do not understand the whole development process and each other’s roles.

If you are looking for PRD development structure and framework check out Parcus Group product management software and training – it provides a full end to end product development framework, workflow as well as over 60 software tools for every step of the process including requirements gathering and tracking. Link is: Product Management Software, Training and Consulting Services

Finally in terms of requirements capture you should also specify:
– The priority of every requirement
– Business drivers (eg. strategic, user experience, retention etc) and
– Traceablity factors (so that you can check on what has been delivered in later stages of the project)

I can not attach a full template but here is the summary of the key chapters in the one provided by Parcus Group (specifically for telecom products):

  1. Initiative Description
  2. Stakeholders, Roles and Responsibilities
  3. Business Drivers
  4. Business Requirements Priority
  5. Sales Channel
  6. Customer Eligibility
  7. Ordering, Fulfilment and Installation
  8. Customer Adds, Moves and Changes
  9. Customer Experience
  10. Product/Solution Features
  11. Infrastructure Requirements
  12. Pricing Capability
  13. Billing and Payment
  14. Credit Management
  15. Complaints
  16. Security and Quality
  17. Assurance and Support
  18. Legal and Regulatory
  19. Reporting and Analysis
  20. Deployment and Training
  21. External Data Inputs and Outputs
  22. Service Level Management
  23. Operations
  24. Documentation
  25. Business Process Requirements
  26. Other Business Requirements
  27. Future Business Requirements
  28. Business Requirements Assumptions
  29. Issues, Risks, Constraints
Share this:
facebooktwittergoogle_plusredditlinkedinmailfacebooktwittergoogle_plusredditlinkedinmail