- Pass The PRINCE2 Exam First Time
- PRINCE2 In Bite-Sized Chunks.
- Key Foundation and Practitioner Learning Points - PRINCE2
- Change Management
- Managing and Controlling a PRINCE2 Delivery Stage
- PRINCE2 Project Closure
- PRINCE2 Starting Up A Project Process
- Using PRINCE2 Initiating A Project Process
- PRINCE2 Authorizing Initiation
- The PRINCE2 Controlling a Stage Process
- Appoint The Executive and Project Manager
- Authorising a PRINCE2 Project
- Authorize a Stage or Exception Plan
- Authorize a Work Package
- Capture and Examine Issues and Risks
- Change Control
- Change control procedures
- Configuration Management
- Configuration Management and Change Control
- Controlling a stage
- Create the PRINCE2 Communication Management Strategy
- Creating a PRINCE2 Plan
- Design and appoint the Project Management Team
- Execute a PRINCE2 Work Package
- Give Ad-hoc direction in a PRINCE2 project
- Hand over products and evaluate a PRINCE2 project
- Managing A Stage Boundary
- Managing Product Delivery process
- PRINCE2 - Authorise Project Closure
- PRINCE2 - Directing a Project PRocess
- PRINCE2 Configuration Management and Change Control
- PRINCE2 Controls and Tolerance
- PRINCE2 Estimating Techniques
- PRINCE2 Management Stages
- PRINCE2 Plans
- PRINCE2 Principles
- PRINCE2 Product-based Planning video
- PRINCE2 Product-based planning technique
- PRINCE2 Progress reporting
- PRINCE2 Quality Theme
- Plan The Next Stage or Exception Plan
- Plan the Initiation Stage in PRINCE2
- Prepare the PRINCE2 Quality Management Strategy
- Prepare the Risk Management Strategy
- Prepare the outline Business Case
- Product Based Planning
- Project Board and Project Manager PRINCE2 Controls
- Project Startup
- Quality Expectations and Acceptance Criteria
- Quality Management Strategy
- Quality review technique
- Report Highlights
- Reporting PRINCE2 Stage End
- Select the project approach and assemble the Project Brief
- Set up the PRINCE2 project controls
- Simple Study Aid
- Tailoring PRINCE2 Themes
- Take corrective action
- The Closing a Project Process
- The Controlling a Stage Process
- The Core Seven
- The Only PRINCE2 Sample Practitioner Exam Paper On The Internet!
- The PRINCE2 Business Case
- The PRINCE2 Change Theme
- The PRINCE2 Initiating a project process
- The PRINCE2 Process Sequence
- The PRINCE2 Processes
- The PRINCE2 Quality Review Technique
- The PRINCE2 Risk Management procedure
- The PRINCE2 Themes
- The Prince2 Process Sequence
- The risk management procedure
- prepare for planned or premature closure
- The PRINCE2 Article Library
- 38 Speedy Power Keys For Your PRINCE2 Project Health Check.
- Carrying out a PRINCE2 Quality Check
- The Product Description
- The plans theme and product based planning
- Creating a PRINCE2 Product Description
- PRINCE2 - Keeping Your Project On track - Part 2
- PRINCE2 Article Database
- PRINCE2 – Keeping Your Project On Track – PART 1
- Tailoring PRINCE2 for a feasibility study.
- Tailoring PRINCE2 with Agile (DSDM Atern)
- The Benefits Review Plan
- The PRINCE2 Risk Theme – Uncertainty Mastered!
- The PRINCE2 Work Package
- The Secrets Of tailoring PRINCE2
- The Use and Content of the Issue Register and Issue Report
- Applying earned value calculations to PRINCE2.
- PRINCE2 Foundation and Practitioner Exam Tips
- Using Project Sc ale In A PRINCE2 Project
- Creating a PRINCE2 Exception Report
- Agile verses PRINCE2 - a new species in evolution
- PART TWO of my Configuration Management In PRINCE2 Video
- PRINCE2 Quality
- Real-World PRINCE2 Planning
- Reviewing the progress on a PRINCE2 project
- Risk management
- Things You Might Not Know About PRINCE2
- The PRINCE2 Project Board and Governance
PRINCE2 The Controlling a Stage Process
Controlling A Stage
I'm sure if you've referred to the PRINCE2 Manual, that the process "Controlling a Stage" is a key part of understanding the method. Reading through the detail, it is fairly clear that this is a well thought-through and structured process. As you dive into the detail of each activity again, the thinking is clear and the details make good sense.
The problem may be however, in the diagram of the Controlling a Stage process. It is obviously drawn to fit on the page and does not give a clear understanding of how the activities work together. It occurred to me, that since this process is obviously all about the day-to-day management of a stage, then the flow and sequence of the sub processes could be better understood when starting from the perspective of a project manager.In essence, the project manager needs gather information to determine what has actually been done (or not done!) - and then to consider what yet remains to be done. In summary - gathering data and forecasting.
The next action of the project manager is to capture actual data, a completed Work Package as one example. Of course, it is never as simple as this in the real world, other information that will help project manager determine the true status so far such as, the Risk Log, the Quality Log, Checkpoint Reports,etc.
The project Manager will want to refer to the main plans and the Business Case also...
Of special interest, are the arrival of issues. These can arrive from anyone at any time, and it is important that they are logged, categorised, and an analysis carried out of their impact. The result of this impact analysis will almost certainly change " the road ahead".
The project manager enters all actual information into the Stage Plan, and will almost certainly be some form of planning tool to assist with this, and to help forecast the remainder of the stage work to be carried out, and the products yet to be created and approved.
The next step is to look at the remainder of the stage, and the project. As above, information from the Logs, Stage Plan, Project Plan, and Business Case, will assist in determining what remains to be done and checking that appropriate plans, products, resources, and activities are in place.
That summarises the " thinking" part of a project managers control - now it is time to take action. If everything is going well, then the project manager has the option of " doing nothing"!
But life is not normally like that...
When the project board approve the next stage plan, they will set the Tolerance for the stage and tell the project manager how often they wish to receive the regular Highlight Reports. Therefore, a regular job of the project manager is to gather sufficient information, then create and send the highlight report to the project board.Work packages should be sent on a regular basis as needed during the stage, to the specialist team or team manager. These need to be first agreed with the specialist team concerned before work can start. Once underway, regular Checkpoint Reports are given to the project manager to help determine the status of product creation and approval.
It is rare that progress during the stage ever goes exactly to plan, and it is quite normal for a project manager needing to take some form of corrective action. This may be done as a simple verbal instruction to issue a new or modified work package to the team. Such corrective actions will only ever be taken when the stage is forecast to remain within Tolerance.
As part of the stage day-to-day management, the project manager will be constantly ensuring that tolerance will not be exceeded. However, the first moment that tolerance is forecast to be exceeded, the project manager must create an Exception Report and send it to the project board for their consideration and future action.
This last step is using the "Management By Exception" element of PRINCE2.
Well, that sums it up, when you now refer to the detail in the PRINCE2 Manual - hopefully it will make better sense!
For more information CLICK HERE




