Pure PRINCE2 - Directing a Project Flashcards
What is the overall goal of the DP process and what principle does it support?
It concerns the overall management of the project by the PB, not the day-to-day running of the project by the PM.
The Directing a Project (DP) process enables the PB to remain responsible for the project, ensure continued business justification and exercise overall control, whilst delegating day-to-day managing and non-critical decisions to less senior employees (manage by exception).
The PB must ensure the project remains aligned with all stakeholder needs.
What are the five objectives of the DP process?
- Ensure there is proper authority to initiate, lead and close a project
- Ensure there is proper authority to deliver the project products
- Ensure the project directed and controloled throughout the project lifecycle
- Ensure Continued Business Justification
- Review post-project benefits of product
When does the Directing a Project (DP) process start and end?
The Directing a Project (DP) process starts when the PB approves the Project Brief at the end of SU (SU and IP stage boundary) and continues until project closure.
How does the DP process work?
There should be no progress meetings and the PM should only contact the PB at regular, previously-agreed intervals, and when an exception has been hit.
What are the four points PRINCE2 Agile and feed into PRINCE2 Agile?
- Authorising Project Initiation
- Authorising a Stage Boundary or Exception Plan
- Authorising Project Closure
- Ad hoc advice
What are the PB and PM responsibilities at Authorising Project Initiation?
A PM must:
- Create a new PID and submit to the PB
- Prepare the Benefits Review Plan
- Obtain the required resources.
PB must:
- Review the PBr and PID to assess the viability of a project and if it is ready to start.
- One CBJ has been measured, they approve the IP stage plan, approve progression through the stage boundary, authorise the PM to start the project and inform all SH’s of project initiation
What are the PB and PM responsibilities at Authorising a Stage Boundary or Exception Plan?
A project can only move from one stage to the next with approval from the PB. At the end of each stage, the PB reviews the performance of the project against the BC, assesses CBJ and plans the next stage before making their decision.
During a stage, if the project deviates outside of the tolerances set by the PB, the PM must submit an Exception Report to the PB. This triggers the Stage Boundary process.
At each stage boundary, the PB must:
- Review the End Stage Report to outline project performance against the BC
- Review the Risk Register to check if risk exposure is still within tolerable limits
- Check any completed products falls within the original scope, and if changed, that the changes are compliant with the Change Management Approach (ChMA).
- Review the plan of the next stage or Exception Report and check if it is in line with the BC and is achievable
- Set tolerances for the next stage
- Approve or reject the stage plan / Exception Report. This either leads to project progression or project closure
- Inform C/P of the status and progress of the project
If PB has to escalate a tolerance exceeded, the Project Executive needs to raise this with the person that raised the Project Mandate.
What are the PB and PM responsibilities at Authorising Project Closure (APC)?
Normally occurs at the end of a project, but can occur sooner if approved by the PB.
APC is the last activity undertaken by the PB. It may require endorsement from C/P.
During APC, the PB must:
- Review the original and current PID to understand project baselines, controls and quality requirements
- Review the End Project Report (EPR) to assess a projects performance and plan follow-up steps stated in the EPR
- Review and distribute the Lessons Log.
- Verify the handover of the products in line with the CMA, and checking all changes fall within the ChMA
- Ensures the Project Benefits Review Report (PBRR) is completed and covers product performance and future realisation of expected benefits that cannot be measured yet
- Confirms the current BC and SH needs have been satisfied
- Review and issue a Project Closure Notification that requests the resources to close a project
What are the PB and PM responsibilities when giving Ad Hoc Guidance?
The PB may give informal advice to the PM team at any time, particularly during IP and at SB’s, in many formats:
- Informal request - seek advice from the C /P and assist the PM
- Escalated Issue Report - make decisions that fall within tolerances, but escalate to C/P if needed
- Exception Report - Change to a key area of the project. Seek advice from C/P if necessary. Approve or decline the change, or terminate the project
- Highlight report - Review project to ensure it is within specification and on-time, and report back to the C/P
- General advice - Keep the PM informed of any relevant changes that may impact the project
The PM is responsible for deciding whether to escalate information to the PB.