Scribd
Upload
36 views3 pages

Product Reqs Document (PRD) Template

This document provides a template for a product requirements document (PRD) including sections for an overview, goals, success metrics, assumptions, requirements, UX mocks, questions, and out of scope items. The template is intended to help capture all necessary information for a project in a single document.

Uploaded by

Mochammad Rafi Fauzi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
36 views3 pages

Product Reqs Document (PRD) Template

This document provides a template for a product requirements document (PRD) including sections for an overview, goals, success metrics, assumptions, requirements, UX mocks, questions, and out of scope items. The template is intended to help capture all necessary information for a project in a single document.

Uploaded by

Mochammad Rafi Fauzi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 3

To use this template, first make a copy. For advice on using the template, watch this video.

Template by Dante Alvarado-Leon.

Template: [Project Name] PRD


Document owner: Your Name | Last Updated: [Insert date]
Jira Epic [Link the epic link for reference - helpful to track engineering team’s progress]

Delivery Date [When is this planned to ship?]

Document Status [What is the current status of this document? i.e.On track, at risk, delayed, etc.]

Product Lead [Your name - usually the PM]

Engineering Lead [Your tech lead’s name]

Designer Lead [Your product designer’s name]

Quality Assurance (QA) Lead [Your testing/QA lead’s name]

Relevant Documents [Link any related documents, confluence or wiki pages, etc]

Table of Contents
1. Overview
2. Goals
3. Success Metrics
4. Assumptions & Dependencies
5. Requirements
6. UX Mocks
7. Questions
8. Out of Scope

Overview
● [Provide background information about the problem]
○ Why are we doing this?
■ How do we know this is a real problem and worth solving?
○ How does this fit into the overall company objectives?
○ What problem is this solving?
■ Who are we solving for?
■ What are the user benefits?

Goals
● [What is the outcome we are trying to achieve? What does success look like?]
Success Metrics
● [Include key metrics that your team will track to measure success]
○ How do we know if we’ve solved this problem?
■ We will track the following metrics to measure success:
● Metric 1
● Metric 2
● Metric 3

Assumptions & Dependencies


● [List any assumptions you or your team might be making]
● [Include any dependencies on other internal systems or teams]

Requirements
● List or link to the user stories involved. Also link to customer interviews, and include
screenshots of what you've seen. Provide enough detail to make a complete story.

# Title User Story Acceptance Criteria Priority Jira Link Notes

1 [Insert short As a _____, I want to be [List out all the steps in the Must have [Insert link to [Use this section to:
title] able to _____ so that I workflow that need to be vs. Jira ticket] - List open questions
can _______. completed in order to fulfill the Nice to or action items
user story] have - Link relevant docs]

When the user clicks on ___they


will be presented with __:

2 EXAMPLE As a zoom host, I want When the host clicks on the “share Must have www.jira.com - We need to further
to be able to share my screen” button they will be /UIUX-100 discuss this with
Desktop screen, so that I can presented with a screen: Engineers_Name.
Screen ● Select a screen they want
collaborate with my
to share -See research done on
Sharing team on a ● All active screens are screen sharing by Itzel
presentation. eligible for selection - Desktop Focus
● The user can select Group Insights
whiteboard, as well as
share phone screens via
cable
● etc...

UX Mocks
● [Work with your designer to include any mockups or wireframes here. Also, include a link
to the main figma or sketch file here for reference.]
Questions
[Create a table to document any questions that the team may have, this will be helpful as
stakeholders may have the same types of questions and this can become an FAQs you can refer
them to.]

Question Outcome

Out of Scope
● [What are the things we are not doing as part of this project and why]

You might also like