PRINCE2 Agile 2016
Previous Section   Next Section

A.21 Project product description

A.21.1 Purpose

The project product description is a special form of product description that defines what the project must deliver in order to gain acceptance. It is used to:

  • Gain agreement from the user on the project’s scope and requirements
  • Define the customer’s quality expectations
  • Define the acceptance criteria, method and responsibilities for the project.

The product description for the project product is created in the Starting up a Project process as part of the initial scoping activity, and is refined during the Initiating a Project process when creating the project plan. It is subject to formal change control and should be checked at stage boundaries (during Managing a Stage Boundary) to see if any changes are required. It is used by the Closing a Project process as part of the verification that the project has delivered what was expected of it, and that the acceptance criteria have been met.

A.21.2 Composition

  • Title Name by which the project is known
  • Purpose This defines the purpose that the project’s product will fulfil and who will use it. It is helpful in understanding the product’s functions, size, quality, complexity, robustness etc.
  • Composition A description of the major products to be delivered by the project
  • Derivation What are the source products from which this product is derived? Examples are:
    • Existing products to be modified
    • Design specifications
    • A feasibility report
    • Project mandate
  • Development skills required An indication of the skills required to develop the product, or a pointer to which area(s) should supply the development resources
  • Customer’s quality expectations A description of the quality expected of the project’s product and the standards and processes that will need to be applied to achieve that quality. They will impact on every part of the product development, and thus on time and cost. The quality expectations are captured in discussions with the customer. Where possible, expectations should be prioritized
  • Acceptance criteria A prioritized list of criteria that the project’s product must meet before the customer will accept it – i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to key stakeholders (and, in particular, the users and the operational and maintenance organizations). Examples are: ease of use, ease of support, ease of maintenance, appearance, major functions, development costs, running costs, capacity, availability, reliability, security, accuracy or performance
  • Project-level quality tolerances Specifying any tolerances that may apply for the acceptance criteria
  • Acceptance method Stating the means by which acceptance will be confirmed. This may simply be a case of confirming that all the project’s products have been approved or may involve describing complex handover arrangements for the project’s product, including any phased handover of the project’s products
  • Acceptance responsibilities Defining who will be responsible for confirming acceptance.
Previous Section   Next Section