Embed Size (px)
Citation preview
Project KickStart Project KickStart Product Requirements DocumentProduct Requirements Document
Presenter NamePresenter Name#/#/200#
Note: this project plan was exported from Project KickStart directly Note: this project plan was exported from Project KickStart directly to PowerPoint. to PowerPoint.
Project KickStart is an easy-to-use project management software for Project KickStart is an easy-to-use project management software for small and medium sized business projects. A Free Trial is available small and medium sized business projects. A Free Trial is available
at at www.ProjectKickStart.comwww.ProjectKickStart.com
1. Download Free Trial
2. Buy Project KickStart
3. Project KickStart Product Page
4. Project KickStart Tour5. Project KickStart Templates6. Contact Project KickStart (800) 678-7008
Quick Links (Links are clickable only in slideshow mode, hit F5)
www.ProjectKickStart.com
9/19/2007 - 10/11/2007 2Product Requirements Document
AgendaAgenda
Project PhasesProject Phases Project ScheduleProject Schedule Total CostTotal Cost Tasks in PhasesTasks in Phases Gantt ChartGantt Chart
9/19/2007 - 10/11/2007 3Product Requirements Document
Project PhasesProject Phases
1.1. Revision HistoryRevision History
2.2. Approval HistoryApproval History
3.3. Purpose of this documentPurpose of this document
4.4. IntroductionIntroduction
5.5. Purpose and StrategyPurpose and Strategy
6.6. Goals - Key BenefitsGoals - Key Benefits
7.7. PositioningPositioning
8.8. Target MarketTarget Market
9/19/2007 - 10/11/2007 4Product Requirements Document
Project PhasesProject Phases (Page 2) (Page 2)
9.9. Product OverviewProduct Overview
10.10. Features and FunctionalityFeatures and Functionality
11.11. Competitive MatrixCompetitive Matrix
12.12. Constraints and DependenciesConstraints and Dependencies
13.13. Service Provisioning and MaintenanceService Provisioning and Maintenance
14.14. RequirementsRequirements
15.15. Future PlansFuture Plans
9/19/2007 - 10/11/2007 5Product Requirements Document
Project ScheduleProject Schedule
Project Start:9/19/2007Project Start:9/19/2007
Project End:10/11/2007Project End:10/11/2007
9/19/2007 - 10/11/2007 6Product Requirements Document
1. Revision History1. Revision History
Document PRD revisionsDocument PRD revisions
9/19/2007 - 10/11/2007 7Product Requirements Document
2. Approval History2. Approval History
What people will need to approve PRD?What people will need to approve PRD? What dates should the approvals be due What dates should the approvals be due
back on?back on?
9/19/2007 - 10/11/2007 8Product Requirements Document
3. Purpose of this document3. Purpose of this document
Document the purpose of the Product Document the purpose of the Product Requirements DocumentRequirements Document
Communicate the purpose of the PRD to Communicate the purpose of the PRD to stakeholdersstakeholders
9/19/2007 - 10/11/2007 9Product Requirements Document
4. Introduction4. Introduction
Describes nature of product/service Describes nature of product/service release as well as deployment details and release as well as deployment details and communicationcommunication
9/19/2007 - 10/11/2007 10Product Requirements Document
5. Purpose and Strategy5. Purpose and Strategy
Why is the product important?Why is the product important? Who are the target customers for this Who are the target customers for this
product/feature?product/feature? Are there any schedule requirements with Are there any schedule requirements with
regard to releases?regard to releases? What is the proposed strategy for the What is the proposed strategy for the
product from a product-marketing product from a product-marketing standpoint?standpoint?
What is the proposed implementation What is the proposed implementation strategy: what modules/products will this strategy: what modules/products will this feature interact with?feature interact with?
9/19/2007 - 10/11/2007 11Product Requirements Document
6. Goals - Key Benefits6. Goals - Key Benefits
What problem is this product attempting What problem is this product attempting to remedy?to remedy?
What key benefits will this product bring What key benefits will this product bring to any existing product suites?to any existing product suites?
What functionality will this provide that What functionality will this provide that will address an issue or improve the will address an issue or improve the customer experience?customer experience?
Include a section if this product/feature is Include a section if this product/feature is a direct result of customer/user feedback a direct result of customer/user feedback or recommendation.or recommendation.
9/19/2007 - 10/11/2007 12Product Requirements Document
7. Positioning7. Positioning
This section should describe the product This section should describe the product positioning in terms of its competitors and positioning in terms of its competitors and features.features.
9/19/2007 - 10/11/2007 13Product Requirements Document
9. Product Overview9. Product Overview
Describes what it is, what it does, how it Describes what it is, what it does, how it works.works.
9/19/2007 - 10/11/2007 14Product Requirements Document
10. Features and Functionality10. Features and Functionality
Describe the features and functionality Describe the features and functionality and associated benefits.and associated benefits.
9/19/2007 - 10/11/2007 15Product Requirements Document
11. Competitive Matrix11. Competitive Matrix
The competitive matrix should clearly The competitive matrix should clearly specify the landscape for this new specify the landscape for this new service/feature.service/feature.
Consider including competitor Consider including competitor functionality matrix.functionality matrix.
9/19/2007 - 10/11/2007 16Product Requirements Document
12. Constraints and Dependencies12. Constraints and Dependencies
This section should detail any known or This section should detail any known or potential risks such as: resource potential risks such as: resource constraints (Engineering or otherwise) or constraints (Engineering or otherwise) or other implications of implementing other implications of implementing feature.feature.
9/19/2007 - 10/11/2007 17Product Requirements Document
13. Service Provisioning and 13. Service Provisioning and MaintenanceMaintenance Describes how the service will be Describes how the service will be
provisioned and maintained.provisioned and maintained.
9/19/2007 - 10/11/2007 18Product Requirements Document
14. Requirements14. Requirements
Functional RequirementsFunctional Requirements External Interface RequirementsExternal Interface Requirements Performance RequirementsPerformance Requirements Security RequirementsSecurity Requirements Usability RequirementsUsability Requirements Test RequirementsTest Requirements Billing RequirementsBilling Requirements Pricing RequirementsPricing Requirements
9/19/2007 - 10/11/2007 19Product Requirements Document
14. Requirements14. Requirements (Page 2) (Page 2)
Reporting RequirementsReporting Requirements Distribution and Marketing RequirementsDistribution and Marketing Requirements Documentation & Training RequirementsDocumentation & Training Requirements Support RequirementsSupport Requirements Installation & Maintenance RequirementsInstallation & Maintenance Requirements Environmental RequirementsEnvironmental Requirements
9/19/2007 - 10/11/2007 20Product Requirements Document
Gantt ChartGantt Chart
#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Task Name
Revision History
Document PRD revisions
Approval History
What people will need to approve PRD?
What dates should the approvals be due back on?
Purpose of this document
Document the purpose of the Product Requirements Document
Communicate the purpose of the PRD to stakeholders
Introduction
Describes nature of product/service release as well as deployment details and communication
Purpose and Strategy
Why is the product important?
Who are the target customers for this product/feature?
Are there any schedule requirements with regard to releases?
What is the proposed strategy for the product from a product-marketing standpoint?
What is the proposed implementation strategy: what modules/products will this feature interact with?
Goals - Key Benefits
What problem is this product attempting to remedy?
What key benefits will this product bring to any existing product suites?
What functionality will this provide that will address an issue or improve the customer experience?
Include a section if this product/feature is a direct result of customer/user feedback or recommendation.
Positioning
This section should describe the product positioning in terms of its competitors and features.
Target Market
Product Overview
Describes what it is, what it does, how it works.
Features and Functionality
Describe the features and functionality and associated benefits.
Competitive Matrix
The competitive matrix should clearly specify the landscape for this new service/feature.
Consider including competitor functionality matrix.
Constraints and Dependencies
Days
1
1
2
1
1
2
1
1
1
1
5
1
1
1
1
1
4
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
Start
9/19/07
9/19/07
9/20/07
9/20/07
9/21/07
9/20/07
9/20/07
9/21/07
9/20/07
9/20/07
9/20/07
9/20/07
9/21/07
9/24/07
9/25/07
9/26/07
9/20/07
9/20/07
9/21/07
9/24/07
9/25/07
9/20/07
9/20/07
9/21/07
9/20/07
9/20/07
9/20/07
9/20/07
9/20/07
9/20/07
9/21/07
9/20/07
Finish
9/19/07
9/19/07
9/21/07
9/20/07
9/21/07
9/21/07
9/20/07
9/21/07
9/20/07
9/20/07
9/26/07
9/20/07
9/21/07
9/24/07
9/25/07
9/26/07
9/25/07
9/20/07
9/21/07
9/24/07
9/25/07
9/20/07
9/20/07
9/21/07
9/20/07
9/20/07
9/20/07
9/20/07
9/21/07
9/20/07
9/21/07
9/20/07
Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed
16-Sep 23-Sep 30-Sep 7-Oct
Product Requirements Document
1/31/2008 1 of 3
9/19/2007 - 10/11/2007 21Product Requirements Document
Gantt ChartGantt Chart
#
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Task Name
This section should detail any known or potential risks such as: resource constraints (Engineering or otherwise) or other implications of implementing feature.
Service Provisioning and Maintenance
Describes how the service will be provisioned and maintained.
Requirements
Functional Requirements
External Interface Requirements
Performance Requirements
Security Requirements
Usability Requirements
Test Requirements
Billing Requirements
Pricing Requirements
Reporting Requirements
Distribution and Marketing Requirements
Documentation & Training Requirements
Support Requirements
Installation & Maintenance Requirements
Environmental Requirements
Future Plans
Days
1
1
1
14
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Start
9/20/07
9/20/07
9/20/07
9/21/07
9/21/07
9/24/07
9/25/07
9/26/07
9/27/07
9/28/07
10/1/07
10/2/07
10/3/07
10/4/07
10/5/07
10/8/07
10/9/07
10/10/07
10/11/07
Finish
9/20/07
9/20/07
9/20/07
10/10/07
9/21/07
9/24/07
9/25/07
9/26/07
9/27/07
9/28/07
10/1/07
10/2/07
10/3/07
10/4/07
10/5/07
10/8/07
10/9/07
10/10/07
10/11/07
Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed
16-Sep 23-Sep 30-Sep 7-Oct
Product Requirements Document
1/31/2008 2 of 3
9/19/2007 - 10/11/2007 22Product Requirements Document
Gantt ChartGantt Chart
#
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Task Name
This section should detail any known or potential risks such as: resource constraints (Engineering or otherwise) or other implications of implementing feature.
Service Provisioning and Maintenance
Describes how the service will be provisioned and maintained.
Requirements
Functional Requirements
External Interface Requirements
Performance Requirements
Security Requirements
Usability Requirements
Test Requirements
Billing Requirements
Pricing Requirements
Reporting Requirements
Distribution and Marketing Requirements
Documentation & Training Requirements
Support Requirements
Installation & Maintenance Requirements
Environmental Requirements
Future Plans
Days
1
1
1
14
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Start
9/20/07
9/20/07
9/20/07
9/21/07
9/21/07
9/24/07
9/25/07
9/26/07
9/27/07
9/28/07
10/1/07
10/2/07
10/3/07
10/4/07
10/5/07
10/8/07
10/9/07
10/10/07
10/11/07
Finish
9/20/07
9/20/07
9/20/07
10/10/07
9/21/07
9/24/07
9/25/07
9/26/07
9/27/07
9/28/07
10/1/07
10/2/07
10/3/07
10/4/07
10/5/07
10/8/07
10/9/07
10/10/07
10/11/07
Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun Mon Tue WedThu
30-Sep 7-Oct 14-Oct 21-Oct 28-Oct 4-Nov
Product Requirements Document
1/31/2008 3 of 3
9/19/2007 - 10/11/2007 23Product Requirements Document
Questions?Questions?
For additional information on Project KickStart’s For additional information on Project KickStart’s
easy-to-use project management software, please visit: easy-to-use project management software, please visit:
www.ProjectKickStart.comwww.ProjectKickStart.com
Sales: (800) 678-7008Sales: (800) 678-7008
1. Download Free Trial 2. Buy Project KickStart3. Project KickStart Product Page
4. Project KickStart Tour
5. Project KickStart Templates6. Contact Project KickStart (800)
678-7008
Quick Links (Links are clickable only in slideshow mode, hit F5)
www.ProjectKickStart.com
