Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
147 views3 pages

Product Requirements Document Template

This document provides a template for product requirement documents (PRDs) with sections for introduction, customer needs, business model, expected results, marketing, functional requirements, non-functional requirements, design, and technical specifications. It instructs the user to copy the document and replace the instructions with their own text. A link is also provided to an app that can automatically generate PRD templates from a roadmap.

Uploaded by

Md.Sakib-Bin-Kashem Ony
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
147 views3 pages

Product Requirements Document Template

This document provides a template for product requirement documents (PRDs) with sections for introduction, customer needs, business model, expected results, marketing, functional requirements, non-functional requirements, design, and technical specifications. It instructs the user to copy the document and replace the instructions with their own text. A link is also provided to an app that can automatically generate PRD templates from a roadmap.

Uploaded by

Md.Sakib-Bin-Kashem Ony
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

How to use this template: Make a copy of the document by clicking “File -> Make a copy”.

Remove this text and replace the yellow marked instructions with your own text. For automated
and clean creation of these templates from a roadmap consider using our app
https://www.getshipit.com.

PRD: <Title>

Changelog
● 01/01/2020 - Initial version

Related Documents
Use this section to link to other relevant documents, such as other PRDs, market research etc.

● Link to Document 1
● Link to Document 2

Introduction
General introduction to the particular product initiative.

Customer needs, market and business model

Known customers and customer requests


If you have customers who have asked for the functionality covered, list them here with details,
e.g. links to customer call notes, or link to PRD.

Quantitative customer data


If you have any numbers, for example how many customers have asked for feature x.

Business model and pricing

1
getshipit.com
How will this initiative be priced? Part of standard pricing plans? An extension, or add-on? A
whole new business model?

Expected results
Write here in a few sentences and with a few numbers what you expect when launching the
initiative. For example “We expect in the first 3 months after launch 25 customers will sign up for
this feature” or “We expect revenue will increase by 2% in the first 6 months”. This is useful to
check back later on initial assumptions.

(Product) Marketing and Communication

Key metrics
How do you measure success and adoption for the product initiative? List concrete metrics to
track here.

Terms, wording, and copy


The key words and terms to use in/for the product. Links to additional materials.

Personas
Customer or user personas.

Functional Requirements
Description of key functional aspects on a very high level, for example Epic level. Detailed user
stories will go into your ticketing system (Such as Jira, Github, Trello etc.). You can also link
(some of) them here.

Non-Functional Requirements
This is often forgotten: things such as: how many users are expected to be supported at peak?
Any latency expectations (page load in x ms) etc.?

2
getshipit.com
Design
Any high level UX/UI considerations to mention, but primarily link to any UX research or any
prototypes as things progress.

Technical Specifications
Anything that’s relevant for/from engineering. Such as key technical challenges or risks.

3
getshipit.com

You might also like