Chapter 1: Starting Up a Project (SU)

Chapter 2: Initiating a Project (IP)

Chapter 3: Directing a Project (DP)

Chapter 4: Controlling a Stage (CS)

Chapter 5: Managing Product Delivery (MP)

Chapter 6: Managing Stage Boundaries (SB)

Chapter 7: Closing a Project (CP)

Chapter 8: Planning (PL)

Chapter 9: Business Case

Chapter 10: Project Organization

Chapter 11: Plans

Chapter 12: Project Controls

Chapter 13: Quality

Chapter 14: Risk

Chapter 15: Change Control

Chapter 16: Configuration Management

Chapter 17: Product-Based Planning

Chapter 18: Quality Review

Introduction

There are two key principles of PRINCE2 that you should grasp as the basis for your understanding of the method:

• A project should be driven by its business case. You should not start a project unless there is a sound business case for it. At regular intervals in the project you check to see that the project is still viable and stop the project if the justification has disappeared.

• PRINCE2 is product based. PRINCE2 focuses on the products to be produced by the project, not the processes to produce them. This affects its method of planning, many of its controls and its approach to ensuring quality.

Structure of the PRINCE2 method

There are three parts to the structure of the method itself:

• processes

• components

• techniques.

PRINCE2 offers a set of processes that provide a controlled start, controlled progress and a controlled close to any project. The processes explain what should happen and when it should be done.

PRINCE2 has a number of components...