Prince2 Process Outline

Prince2 is made up of 7 Processes and 7 Themes, projects run under Prince2 use all the processes.  The key to successful use of the process model is to look at the extent and detail to which each process is used. It is important that all processes are used in every project but only to the extent required.

Directing a Project (DP)

This process is aimed at the Project Board the people responsible for the project and making key decisions, the process supports the concept of “Management by Exception”. This process covers the whole project from the starting phase to closing a project. The major stages of this process are:

1. Authorizing the SU the preparation of the Project Plan and Business Cases for the project.
2. Approving the project to begin
3. Checking the project is on track and viable at the stages or other relevant points.
4. Monitoring progress and giving advice.
5. Closing the project.

Starting up a Project (SU)

This is the process that outlines the project and consists of six main objectives:

1. Appoint the Project Management team
2. Define and articulate the objectives and scope of the project.
3. Decide on the project approach.
4. Define customer quality expectations.
5. Outline the Business value for the project.
6. Begin the contract outlines and requirements between the suppliers and customers.

Initiating a Project (IP)

This process is to establish a solid foundation for the project to begin the PID (Project Initiation Document) is created during this process. Key Activity’s are:

1. Planning Quality
2. Planning the Project
3. Refining the Business Cases
4. Putting project controls
5. Setting up the Project Files

Controlling a Stage (CS)

This process includes all the elements that the project manager has to control and monitor when running the project and is made up of continually undergoing the process of:

1. Authorizing work to be done.
2. Updating the projects progress.
3. Looking for changes in the project and risks.
4. Reporting on Progress
5. Taking action to keep project on track.

Managing Product Delivery (MP)

This process manages the relationship between the Project Manager and the specialist/2^nd party teams. This covers the specification on task, quality, date these are combined in to a Working Pack which is agreed between the team and the project manager. The key practices are:

1. Defining the Work Package
2. Planning the work of the team.
3. Making sure that the work is done.
4. Verifying products against the Quality Criteria
5. Reporting on the quality to the Project Manager
6. Accepting the product

Managing a Stage Boundary (SB)

The reason for this process is to provide the project board with all the information that they need to review the current stage and approve the updated project plan for the next stage. This process normal happens near the end of the stage.

1. Verify that all work from the current stage is finished.
2. Finalise the planning for the next stage.
3. Update the project, business plan and risks.
4. Report on outcome of current stage.
5. Obtain approval for next stage.

Closing a Project (CP)

The process is used to close the project either at the natural end of the project or at a premature end. This process will:

1. Define the extent that the project has achieved its goals.
2. Confirm the projects products are satisfactory
3. All planning has been done for future requirements and maintain of the project.
4. Follow on Recommendations for projects
5. Document Lessons Learned
6. Report on the project management process.

Popularity: 27% [?]

Related posts:

1. Basic Risk Management
2. Project Start Up – Feasibility Study – Outline
3. Prince2 2009
4. Essentials of Project Planning
5. Prince2 2009 Interesting Video