Clarifying Some Key Points
This section runs through a few areas that those learning PRINCE2 sometimes misunderstand or find hard to follow. For each point, have a look at the first few sentences and if you understand the area well, leave the rest and move on to the next point. If you don’t understand the area, the text may help, but you’ll also benefit from putting the point on your revision list, digging into PRINCE2 For Dummies, and reading the relevant part of the PRINCE2 manual.
Understanding the focus on appropriate quality
PRINCE2 doesn’t insist on the very highest level of quality for every project. A project to refit the stationery cupboard doesn’t have safety-of-life implications – well, not usually. However, a new computer system to control air traffic across the southern part of the UK does have implications for human safety. The quality level is going to be very different for the two projects, then. In PRINCE2, the difference between projects is reflected in the fact that there are Customer Quality Expectations, project Acceptance Criteria and a Quality Management Strategy for each project. The important things are to determine what quality level is appropriate for each individual project, how that quality will be achieved (the strategy), and to check that it’s been achieved. PRINCE2 covers all of those things with an approach that maps through to the acceptance of products.
Planning the quality management
Planning quality is focused on achieving the required quality ...