Project Product Description
The Project Product Description is a especial Product Description that explains the scope and quality of the final product of the project. Upfront definition of the quality elements such as customer quality expectation is the same in adaptive and predictive projects, while the scope is different: it should be high-level, to allow adaptation.
When the scope is defined very high-level, it automatically shifts from the output to describing the outcome, which is desired in Agile.
When describing the scope, it's a good idea to use MoSCoW Prioritization, or any other kind of system to explain which parts are mandatory, and even allow for more adaptation.
It's common in Agile to say that quality is not negotiable (more on this in the Quality Theme), and it's helpful if this mindset is reflected in the Project Product Description. PRINCE2 Agile suggests setting the quality tolerance to zero, to reflect this in PRINCE2, which is based on a common definition of tolerance and in contrast to the PRINCE2 definition (see Tolerances for more information).
- SU: Starting up a Project Process
- IP: Initiating a Project Process
- SB: Managing a Stage Boundary Process
- CP: Closing a Project Process
- (DP): Directing a Project Process (note that not all activities in this process are shown in this diagram)
- The above image assumes that Scrum is used in the delivery level, which is not necessary.
- The number of stages, releases, and Sprints are just examples, as well as the exception in the third stage.
- The diagram is schematic and many details are not shown.
- Starting up a Project Process
- Project Product Descriptio at PRINCE2 wiki