<Title1> <Title 2> Product Requirements Document. brainmates pty limited abn S 906, Lvl 9, 84 Pitt St Sydney, NSW 2000 Australia AUTHOR:

Transcription

1 brainmates pty limited abn S 906, Lvl 9, 84 Pitt St Sydney, NSW 2000 Australia <Title1> <Title 2> Product Requirements Document AUTHOR: CREATION DATE: LAST UPDATED: VERSION: DOCUMENT LOCATION: 1

2 Table of Contents 1 Introduction Background Product Objective Product Scope In Scope Out of Scope Assumptions Dependencies About This Document Purpose of This Document Authorisation Distribution List Amendment List Business Case Competitor Review Target market Market Problem Financial Impact Risks Issues User Personas Primary Persona Negative Persona Market Requirements Scenario 1: <TITLE> User Goal Scenario 2: <TITLE> User Goal Business Rules <Eligibility> <Other Rules> Product Requirements Title <Grouped by High Level Tasks> Operational Requirements <Service Levels> <Customer Support> <Title> Glossary of Terms

3 1 Introduction 1.1 Background <Provide any backgound information of how the project emerged. The project may have emerged as a direct result of a competitor threat, a new idea or decrease in sales numbers. Also detail if there are any other business activities that relate to this project.> 1.2 Product Objective <What are the product objectives? Will the product grow subscribers, revenue, reduce costs or is it a value add to the product?> 1.3 Product Scope In Scope <What features and functions are in scope when the product is delivered?> Out of Scope <What are the features and functions that the business would like delivered but are out of scope for the launch of this phase of the product? Note: Do not write requirements for out of scope functionality.> 1.4 Assumptions <List the existing business rules that the new product and its associated features and functions will be based on.> 1.5 Dependencies < List the existing project dependencies if any for this product to be delivered.> 3

4 2 About This Document 2.1 Purpose of This Document The purpose of this Product Requirements Document (PRD) is to detail the <Product Name> requirements. This document should be used to < initiate a process, document etc>. 2.2 Authorisation Approved By Approval Date 2.3 Distribution List Name Position Document Version Distributed Feedback Received 2.4 Amendment List Revision Date Description Author 4

5 3 Business Case This section describes the business opportunities gained from delivering this product. 3.1 Competitor Review <Describe at a high level what your competitors are offering.> <Product Name> Company Name Company Name Company Name <Feature 1> <Details of Feature> <Details of Feature> <Details of Feature> <Feature 2> <Price> 3.2 Target market <Describe the market at which the product is targeted.> Key Characteristics Customer Segment Reason for Segment Selection <Age:> <Gender:> <Marital Status:> <Geographic Region:> <Income:> <What Other Characteristics Are Important?> 3.3 Market Problem < This section shall include the problem that this product is trying solve. Note: The problem is a situation that exists in the marketplace and requires change.> <The financial impacts shall include the associated development costs of delivering the product and 3.4 Financial Impact the revenue gained or cost savings made.> 5

6 3.5 Risks <Describe the business and product risks associated with developing this product.> 3.6 Issues <Describe any known business and product issues that are uncovered as a result of developing this product.> 6

7 4 User Personas The section describes the characteristics of the primary user of this product and the characteristics of a user who will never use this product. <A user persona is a fictional character but is nevertheless created from factual information about the target market. The factual information is gained from conducting quantitative research or from statistical information Creating a user persona helps the Product Manager focus on the end user and the end user s goals and needs.> 4.1 Primary Persona Characteristics Persona Details <Personal Details:> <Address:> <Education:> <Employment:> <Income:> <Financial Status:> <Lifestyle:> <Recreational Activities:> <Travel Experience:> <Media Consumption:> <Internet Usage:> <Technology Usage:> <Characteristics Can Be Removed or Added> 4.2 Negative Persona <It may not be necessary to create a negative persona but it is a tool to help the Product Manager focus on the primary persona.> 7

8 5 Market Requirements This section describes each user scenario that is appropriate to this product and the tasks undertaken by the customer to use the product. The market requirement determines what the customer needs to achieve each task. <The market requirements section is the methodology that will help Product Managers create good Product Requirements document.> 5.1 Scenario 1: <TITLE> <Write the most typical scenario or story for the primary user of this product in this section before breaking down the scenario into a step by step user task. The benefit of doing this means that you see the product from the customer point of view before attempting to write the product requirements. It will help you deliver a product that the customer needs.> User Goal <What is the end user trying to achieve in this particular scenario? Go on a holiday, find a date, cook dinner, buy a car etc. Knowing the end user goal helps the Product Manager understand if the tasks performed will meet the user meet his or her goal.> Application User Tasks # Market Requirement 1. <Task 1> MR001 The user shall be able to. <What does the user require to achieve the specific task?> <Note: There may be more than 1 Market Requirement for each user task> Scenario 2: <TITLE> <User scenario> User Goal 1. <Task 1> Application User Tasks # Market Requirement MR008 The user shall be able to. <What does the user require to achieve the specific task?> 8

9 6 Business Rules This section describes the new business rules required to develop and implement the product. 6.1 <Eligibility> <Who can purchase or use this product? All your customers or a subset of your 1. customers?> <What other attributes must your customers have before purchasing, using this product?> <Other Rules>

10 7 Product Requirements This section describes the features and functions provided by the product. This effectively is a list of what the product does or has. 7.1 Title <Grouped by High Level Tasks> MR01 <Market Requirement 1> <Note: Market Requirement numbering may fall out of order> The solution shall <what and how will the product solution deliver to the market 1. requirement. > <Priority>

11 8 Operational Requirements This section describes the operational and non-functional requirements that are necessary to support the product. 8.1 <Service Levels> 1. <What are the minimum service levels that this product requires to function effectively for the customer?> 8.2 <Customer Support> <Title> 1. 11

12 9 Glossary of Terms <Provide description of terms, abbreviations etc used in this document.> Term Description 12