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 PRD Template v1.doc Page 1 of 8

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

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
Subscriptions
Help
OTHER

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

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

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

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 applicable) / New Requirements? Specify, if true / Report Timeframe

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 / PRD Template v1.doc / Page 7 of 8