0% found this document useful (0 votes)
295 views8 pages

Project Title Product Requirements Document (PRD) : Version #.# Product Manager (Author)

This document outlines the requirements for a new product feature. It includes sections on objectives, key dates, use cases, functional requirements, non-functional requirements, and metrics. The objectives section describes the goal of the feature and how success will be measured. It also addresses scalability, dependencies, and impacted areas. The use cases section ranks different user scenarios by importance and outlines descriptions of the top two cases. The functional requirements sections specify requirements around releases, installation, and platforms. The non-functional sections cover performance, integration, notifications and databases. Metrics define what must be measured to determine if objectives are met on release day one.

Uploaded by

Jason Canada
Copyright
© Attribution Non-Commercial (BY-NC)
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
0% found this document useful (0 votes)
295 views8 pages

Project Title Product Requirements Document (PRD) : Version #.# Product Manager (Author)

This document outlines the requirements for a new product feature. It includes sections on objectives, key dates, use cases, functional requirements, non-functional requirements, and metrics. The objectives section describes the goal of the feature and how success will be measured. It also addresses scalability, dependencies, and impacted areas. The use cases section ranks different user scenarios by importance and outlines descriptions of the top two cases. The functional requirements sections specify requirements around releases, installation, and platforms. The non-functional sections cover performance, integration, notifications and databases. Metrics define what must be measured to determine if objectives are met on release day one.

Uploaded by

Jason Canada
Copyright
© Attribution Non-Commercial (BY-NC)
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/ 8

Project Title

Product Requirements Document (PRD)


Version #.#

Product Manager (Author)

Key Dates
Date Objective
PRD Due

Revision History
Date Version Description PM
1.0

Ketera – Confidential – Do Not Distribute 51741133.docx Page 1 of 9


Table of Contents
1. OVERVIEW..........................................................................................................................................................2
1.1 OBJECTIVE OF FEATURE SUMMARY................................................................................................................2
1.2 KEY DATES.....................................................................................................................................................2
1.2.1 Objectives/Goals of the feature; Scalability implications......................................................................2
1.2.2 Dependencies..........................................................................................................................................2
1.2.3 Functional Areas Impacted....................................................................................................................2
1.2.4 Use Cases & Virality..............................................................................................................................2
1.3 OVERALL FLOW DIAGRAM..............................................................................................................................3
2. USE CASES THEME – DETAILED DESCRIPTIONS...................................................................................4
2.1 HOST CATALOG – NEW SUPPLIER USER.........................................................................................................4
2.1.1 Use Case Description:-..........................................................................................................................4
3. NON-FUNCTIONAL REQUIREMENTS.........................................................................................................5
3.1 INTRODUCTION................................................................................................................................................5
3.2 PERFORMANCE REQUIREMENTS......................................................................................................................5
3.3 PLATFORM REQUIREMENTS.............................................................................................................................5
3.4 SCALABILITY/FAILOVER REQUIREMENTS.......................................................................................................5
3.5 LOGGING/AUDIT TRAILS.................................................................................................................................5
3.6 INTEGRATION REQUIREMENTS........................................................................................................................5
3.7 NOTIFICATION REQUIREMENTS.......................................................................................................................5
3.8 DATABASE REQUIREMENTS.............................................................................................................................5
4. RELEASE REQUIREMENTS............................................................................................................................6
4.1 INTRODUCTION................................................................................................................................................6
4.2 BACKWARD COMPATIBILITY REQUIREMENTS.................................................................................................6
4.3 UPGRADE/MIGRATION REQUIREMENTS..........................................................................................................6
4.4 INSTALLATION REQUIREMENTS.......................................................................................................................6
4.5 PLATFORM REQUIREMENTS.............................................................................................................................6
5. DEPENDENCIES.................................................................................................................................................7

Ketera Confidential – Do Not Distribute 51741133.docx Page 1 of 9


1. Overview

1.1 Summary/Objective of Feature


Brief summary of the feature and objectives so reader can understand quickly.

1.2 Objectives/Goals of the feature


Required = How do we measure success of the feature? Specific numbers, dates, $, users, etc. The first row should be the key measure. Optional
= Do we have baseline measures for any goal? Specify within this section. Do we have a way to measure this? Specify.

Key Objective(s) Measure + Expected Results Vs. Baseline and Timeframe


On Day 1+ post-release of this feature,
how do we measure success,
specifically?

1.3 Scalability implications


How does this feature scale within a year or more?

Scalability Measure Expected Result


Within 1 year – how does this feature
scale?
>1 year – how does this feature scale?

1.4 Other Feature Dependencies


Required = Any specific dependencies towards 1) scope completion 2) requirement start 3) development start 4) feature launch 5) measurement
Optional = Leave blank if no dependencies
Dependency Details

1.5 Functional Areas Impacted


Required = Any major functional areas of Ketera require development + testing effort.
Optional = Add areas that are not specified in the table below, but impacted (e.g. Salesforce)
Area Impact
ePro
Sourcing
Catalog
Spend
Invoicing
KSCM
Supplier
Connect
Marketing
E-mail
Trackling
Subscription
s
Help
OTHER

Ketera Confidential – Do Not Distribute 51741133.docx Page 2 of 9


1.6 Overall Flow Diagram
Required = Flow diagram of pages, user/cases.

1.7 Use Cases


Required = Rank use cases by % of users, importance to meeting objectives. Be inclusive of key edge cases, but at secondary priority only.
Virality is defined as one member inviting another member into the site/Network.
Optional = “Non-applicable” use cases – only for scope illustrative purposes (e.g. “we do not support X user login, only Z users can login.”)

1.7.1 Use Case #1

1.7.1.1 User definition

1.7.1.2 Objective

1.7.1.3 % of user, revenue, etc.

1.7.1.4 Description

Ketera Confidential – Do Not Distribute 51741133.docx Page 3 of 9


1.7.2 Use Case #2

1.7.2.1 User definition

1.7.2.2 Objective

1.7.2.3 % of user, revenue, etc.

1.7.2.4 Description

Ketera Confidential – Do Not Distribute 51741133.docx Page 4 of 9


2. Release Requirements

2.1 Primary Requirements


This sections describes the release requirements for the <Product Name> for <Number> release

2.2 Secondary Requirements (Should Have, Optional)


These are not Must Have requirements

2.3 Backward Compatibility Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

2.4 Upgrade/Migration Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

2.5 Installation Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

2.6 Platform Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

Ketera Confidential – Do Not Distribute 51741133.docx Page 5 of 9


3. Metrics/Reporting
Required = What we must measure to determine if we meet objective (as listed above) on Day 1 of release.
Optional = Other reporting requirements, in priority order; these may/not be available to be captured or measured.

Measurement Current Measure (if New Requirements? Specify, Report Timeframe


applicable) if true

Ketera Confidential – Do Not Distribute 51741133.docx Page 6 of 9


4. Non-Functional Requirements

4.1 Performance Requirements

4.2 Platform Requirements

4.3 Scalability/Failover Requirements

4.4 Logging/Audit Trails


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

4.5 Integration Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

4.6 Notification Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

4.7 Database Requirements


ID FUNCTIONAL REQUIREMENT PRIORITY Scope

Ketera Confidential – Do Not Distribute 51741133.docx Page 7 of 9

You might also like