Prince2: Product Description
The Product Description is a separate document from the Project Initiation Document. It defines what a project should deliver to gain acceptance and like the outline Business Case supports two of the Prince2 Principles, the Focus on Products , key deliverables and the Continued Business Justification.
As part of Start up the Project Manager consults with the Senior User and Executive to define what the project is to deliver and to create the Project Product Description and it is subject to formal change control.
- Capture the customer’s quality expectations hence the reason it is written by the users as they have a clearer understanding of what the product should be.
- Capture and agree the project’s acceptance criteria
- Check feasibility of the timescale requirements from the Project Mandate or as required by the outline Business Case
- Determine any new risks in the Daily Log
- Review the risks captured in the Daily Log affecting viability of the project in the outline Business Case.
systems, the attractive off the shelf product seldom fits and making assumption of how things work can be a very expensive lesson.
In a Prince2 project the Product description It has been my experience that too often projects are undertook without understanding the projects products and how they integrate with each other. With so many bespoke corporate
A Product Description could also be used to provide the basis for an Invitation to Tender document.
Product Description Content
- Purpose of the product
- Scope of the product
- Details of the product
- Product identifier
- Product name
- Composition (content)
- Derivation (inputs)
- Format and presentation
- Delivery of the product
- Quality criteria
- Quality criteria (acceptance)
- Quality method
- Quality tolerance
- Quality checking requirements.
- Review process
Elements to remember
- Details about the information held for each Project Product Description is held in the Configuration Management Strategy
- The Project Product Description should contain the Customer’s Quality Expectations.