PRINCE2 methodology - processes
Processes in PRINCE2 describe:
- What decisions are required?
- Who takes decisions?
- What management products (e.g. plans or reports) support decision-making?
- When decisions are taken?
The PRINCE2 processes
are where the principles and themes within the methodology get applied. Processes within the PRINCE2 methodology equate to ‘Process Groups’ in the PMBOK Guide®
The PRINCE2 method has 7 processes:1. Starting up a project
Decides whether the project’s idea is good or not. This requires a project brief which answers why, what, how and who? (Equates to the Project Charter in the PMBOK Guide®
).2. Directing a project
The project board 'manages by exception' and receives regular and ad-hoc reports. It approves all major plans and commits resources. It authorises the project, management stages
and project closure.3. Initiating a project
The project manager plans the firm foundations for the management and control of the project. He/she develops a project initiation documentation (PID) for project board approval. (Equates to the Project Management Plan in the PMBOK Guide®). It answers detailed questions about: why, what, when, who, how much, what if?4. Controlling a stage
The project manager manages risks and issues day by day, assigns and checks work done by teams. He/she reports progress to the project board at regular intervals, escalates exceptions and takes corrective actions if needed.5. Managing product delivery
The team manager gets the team to design, build and test the 'specialist' products (e.g. an IT system). Hands products over as agreed. Reports regular progress to the project manager.6. Managing a stage boundary
The project manager plans the next stage and reports progress of the stage about to finish.7. Closing a project
The project manager checks whether users ‘accept’ the project's products. If so, hands products over to the customer. Reports lessons learned and the achievements of the project. Recommends closure to the project board. Closes and archives all project documentation.