Project KickStart Product Requirements Document Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint.

Slides:



Advertisements
Similar presentations
Planning an Onsite Training Seminar Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint. Project.
Advertisements

[Product Name] Marketing Plan
Project KickStart Event Planning Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint. Project KickStart.
Title Slide – Technology or Company Name
Company Newsletter Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint. Project KickStart is an.
Brought to you in association with 1 How to create a Successful Marketing Plan.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Top-Down Network Design Chapter Fourteen Documenting Your Network Design Copyright 2010 Cisco Press & Priscilla Oppenheimer.
SMALL BUSINESS PLAN GUIDE
Chapter 3 Project Initiation
PRODUCT FOCUS 6/9/14 – 6/20/14 INTRODUCTION Our Product Focus for the next two weeks is Microsoft Windows 8.1. Windows 8 was released in the Fall of.
PRODUCT FOCUS 2/3/14 – 2/14/14 INTRODUCTION Our Product Focus for the next two weeks is VMware. VMware is the current industry leader in server / data.
Requirements Structure 2.0 Clark Elliott Instructor With debt to Chris Thomopolous and Ali Merchant Original Authors.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
The Waterfall Model A Case Study
Business plan cum start-up competition Sample template
Marketing Plan.
Chapter 4 After Green Light. After the Green Light Contractual Agreement Marketing Requirements Document (MRD) Project DefinitionBudget Project Approval.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Business Plan Guidelines. Purpose of Business Plan  Set Goals and Objectives for the Business  Resource Planning  Secure Funding.
CONFIDENTIAL © 2013 IDA Singapore. All Rights Reserved. 1 Proposal Concept Submission Template 1. Problem Statement 1. Project Scope Target Users Business.
Course Overview B290 Fall 2014 What is a strategy? Context / Environment Political Regulatory Technological Resources Skills Knowledge Assets Capital.
Project Management Lecture 5+6 MS Saba Sahar.
Documenting Network Design
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Project Management Software
Web Development Process Description
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
A Typical Business Plan
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
What is SMEcollaborate Primarily developed for Small and Medium Companies who wish to collaborate together. It is a:- A resource center for collaborating.
Marketing Research Lecture 1. MARKETING Purpose of Marketing is to allow a firm to plan and execute the pricing, promotion and distribution of products.
Week One Chapter five “Develop a Business Plan”
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
Business Case Presentation Template. Business Case Presentation Components Why are we considering this proposal? – Strategic alignment – Opportunity summary.
Feasibility Study.
Major Parts in a Business Plan
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Software Requirements Engineering: What, Why, Who, When, and How
2010 Practice Management Annual Conference - LexisNexis Confidential - What’s New With PCLaw Alan Tuback September 15 th 2010 Las Vegas, NV.
What Marketing Brings to the Table & What Marketing Needs from Your Area MKTG 495.
NETE Computer Network Analysis and DesignSlide 1 Documenting Network Design NETE-4635 Computer Network Analysis and Design.
ODesk Product Management MRD. Solution Overview Summary description of proposed solution and basic rationale as to why it’s needed. Sets context for rest.
Today Q2Q3Q4 Q Q2Q3Q4 Q Phase 1 Kickoff 4/10/2014 Project Start 5/1/2014 Project Approved 7/31/2014 Implementation Finished 6/16/2015.
CISB 334 E-Business BUSINESS PLAN. What is Business Plan ?  A document that provides a framework for testing the business from conception through early.
[Title] Presented by [Name] [Date]. Market Problems [Problem 1] [Problem 2] [Problem 3]
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Systems Development Life Cycle
[Product Name] Marketing Plan
Team Skill 1 Analyzing the Problem
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
SitePro & Target Market Billy Pardo. Agenda Overview Target market Key features Key benefits Licensing.
Illuminating Britelite’s Internal Services for Success Strategy for Process Improvement.
Outlines Overview Defining the Vision Through Business Requirements
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
Preliminary Business Plan. Challenge, needs What is the business challenge your product offers a solution to? Describe the pains/costs of not using your.
Marketing Plan.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
ITEC 275 Computer Networks – Switching, Routing, and WANs Week 12 Chapter 14 Robert D’Andrea Some slides provide by Priscilla Oppenheimer and used with.
Today AprAugDec2016AugDec2017Aug Phase 1 Kickoff 4/10/2015 Project Start 5/1/2015 Project Approved 7/31/2015 Implementation Finished 6/16/2016.
 System Requirement Specification and System Planning.
New Product Development Management NPDM 3 Mohsen SADEGHI
CPMGT 300 Competitive Success/snaptutorial.com
CPMGT 300 Education for Service/snaptutorial.com.
CPMGT 300 Teaching Effectively-- snaptutorial.com.
Chapter 4 After Green Light
Downloadable Template
Presentation transcript:

Project KickStart Product Requirements Document Presenter Name #/#/200# Note: this project plan was exported from Project KickStart directly to PowerPoint. Project KickStart is an easy-to-use project management software for small and medium sized business projects. A Free Trial is available at Download Free TrialDownload Free Trial 2. Buy Project KickStartBuy Project KickStart 3. Project KickStart Product PageProject KickStart Product Page 4. Project KickStart TourProject KickStart Tour 5. Project KickStart TemplatesProject KickStart Templates 6. Contact Project KickStart (800) Contact Project KickStart Quick Links (Links are clickable only in slideshow mode, hit F5)

9/19/ /11/2007 2Product Requirements Document Agenda Project Phases Project Phases Project Schedule Project Schedule Total Cost Total Cost Tasks in Phases Tasks in Phases Gantt Chart Gantt Chart

9/19/ /11/2007 3Product Requirements Document Project Phases 1.Revision History 2.Approval History 3.Purpose of this document 4.Introduction 5.Purpose and Strategy 6.Goals - Key Benefits 7.Positioning 8.Target Market

9/19/ /11/2007 4Product Requirements Document Project Phases (Page 2) 9. Product Overview 10. Features and Functionality 11. Competitive Matrix 12. Constraints and Dependencies 13. Service Provisioning and Maintenance 14. Requirements 15. Future Plans

9/19/ /11/2007 5Product Requirements Document Project Schedule Project Start:9/19/2007 Project End:10/11/2007

9/19/ /11/2007 6Product Requirements Document 1. Revision History Document PRD revisions Document PRD revisions

9/19/ /11/2007 7Product Requirements Document 2. Approval History What people will need to approve PRD? What people will need to approve PRD? What dates should the approvals be due back on? What dates should the approvals be due back on?

9/19/ /11/2007 8Product Requirements Document 3. Purpose of this document Document the purpose of the Product Requirements Document Document the purpose of the Product Requirements Document Communicate the purpose of the PRD to stakeholders Communicate the purpose of the PRD to stakeholders

9/19/ /11/2007 9Product Requirements Document 4. Introduction Describes nature of product/service release as well as deployment details and communication Describes nature of product/service release as well as deployment details and communication

9/19/ /11/ Product Requirements Document 5. Purpose and Strategy Why is the product important? Why is the product important? Who are the target customers for this product/feature? Who are the target customers for this product/feature? Are there any schedule requirements with regard to releases? 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 strategy for the product from a product-marketing standpoint? What is the proposed implementation strategy: what modules/products will this feature interact with? What is the proposed implementation strategy: what modules/products will this feature interact with?

9/19/ /11/ Product Requirements Document 6. Goals - Key Benefits What problem is this product attempting to remedy? What problem is this product attempting to remedy? What key benefits will this product bring to any existing product suites? 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? 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. Include a section if this product/feature is a direct result of customer/user feedback or recommendation.

9/19/ /11/ Product Requirements Document 7. Positioning This section should describe the product positioning in terms of its competitors and features. This section should describe the product positioning in terms of its competitors and features.

9/19/ /11/ Product Requirements Document 9. Product Overview Describes what it is, what it does, how it works. Describes what it is, what it does, how it works.

9/19/ /11/ Product Requirements Document 10. Features and Functionality Describe the features and functionality and associated benefits. Describe the features and functionality and associated benefits.

9/19/ /11/ Product Requirements Document 11. Competitive Matrix The competitive matrix should clearly specify the landscape for this new service/feature. The competitive matrix should clearly specify the landscape for this new service/feature. Consider including competitor functionality matrix. Consider including competitor functionality matrix.

9/19/ /11/ Product Requirements Document 12. Constraints and Dependencies This section should detail any known or potential risks such as: resource constraints (Engineering or otherwise) or other implications of implementing feature. This section should detail any known or potential risks such as: resource constraints (Engineering or otherwise) or other implications of implementing feature.

9/19/ /11/ Product Requirements Document 13. Service Provisioning and Maintenance Describes how the service will be provisioned and maintained. Describes how the service will be provisioned and maintained.

9/19/ /11/ Product Requirements Document 14. Requirements Functional Requirements Functional Requirements External Interface Requirements External Interface Requirements Performance Requirements Performance Requirements Security Requirements Security Requirements Usability Requirements Usability Requirements Test Requirements Test Requirements Billing Requirements Billing Requirements Pricing Requirements Pricing Requirements

9/19/ /11/ Product Requirements Document 14. Requirements (Page 2) Reporting Requirements Reporting Requirements Distribution and Marketing Requirements Distribution and Marketing Requirements Documentation & Training Requirements Documentation & Training Requirements Support Requirements Support Requirements Installation & Maintenance Requirements Installation & Maintenance Requirements Environmental Requirements Environmental Requirements

9/19/ /11/ Product Requirements Document Gantt Chart

9/19/ /11/ Product Requirements Document Gantt Chart

9/19/ /11/ Product Requirements Document Gantt Chart

9/19/ /11/ Product Requirements Document Questions? For additional information on Project KickStart’s easy-to-use project management software, please visit: Sales: (800) Download Free TrialDownload Free Trial 2. Buy Project KickStartBuy Project KickStart 3. Project KickStart Product PageProject KickStart Product Page 4. Project KickStart TourProject KickStart Tour 5. Project KickStart TemplatesProject KickStart Templates 6. Contact Project KickStart (800) Contact Project KickStart Quick Links (Links are clickable only in slideshow mode, hit F5)