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 for 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 Targets for more information).
- Starting up a Project process
- Project Product Description in PRINCE2 wiki
Written by Nader K. Rad
This is (and will be) a work in progress: More details will be added in the future, depending on the feedback.
This wiki is developed and managed by an accredited trainer, independent of AXELOS. While aligned with their guidelines, it’s not an official resource.