The 7 Processes of PRINCE2 Project Managementposted by John Spacey, February 07, 2011
PRojects IN Controlled Environments (PRINCE2) is a process-driven project management method.
The PRINCE2 methodology breaks projects into stages and each stage is managed separately. There are 7 processes for managing the project and project stages:
1. Starting up a projectThe project team is assembled, the project approach is decided and business justification is documented.
activities: assemble project management team, create project brief, agree upon project approach, plan for project initiation phase
check points: the project board approves the next phase of the project (project initiation)
2. Initiating a projectProject planning work is continued.
activities: document the project plan, business case, risks, project controls and the plan for the next stage of the project.
3. Directing a projectThe project board (project sponsors) controls the project. This involves a series of authorizations, giving ad-hoc direction and confirming project closure.
check points: project board authorizes project initiation, stage plans and exception plans
4. Controlling a stageThe project is broken down into stages and each stage is controlled separately.
activities: progress assessments, managing issues, status reviews and reporting, taking corrective actions, issue escalation, receiving completed work packages.
check points: work packages are authorized
5. Managing stage boundariesIncludes end of stage activities and planning for the next stage. Also decides what should be done for stages that have exceeded tolerance levels.
activities: stage planning, updating the project plan, updating the business case, updating the risk log, reporting the end of the stage end, creating a exception plan.
6. Managing product deliveryManaging the acceptance, execution and delivery of project work. Ensures that the work products are delivered to expectations and within tolerance.
activities: accept a work package, execute a work package, deliver a work package.
7. Closing a ProjectProject wrap up.
activities: formally de-commission the project, project evaluation, identify follow up actions
How to get RFPs wrong — every time.|
Quality management isn't about quality.|
It would be a lot easier to estimate projects if people were logic-processing robots but it wouldn't be nearly so much fun.|
A style of management that draws inspiration from mushroom farmers.|