- 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
Update the PRINCE2 Project Plan and Business Case
PRINCE2 In Bite-Sized Chunks.
Update the Project Plan and Business Case.
The Project Plan and detailed Business Case first created in the initiation stage and form part of the Project Initiation Documentation. It is important therefore that both these key documents are kept updated particularly at the end of each management stage. The project board uses the Project Plan throughout the project for them to measure progress, whereas although the project manager created the Project Plan, he or she uses the Stage Plan as their main progress document as the project is released to them one stage at a time.

Once the next Stage Plan has been created then the Project Plan is updated to include actual progress on the stage that is about to finish. This will include information such as actual cost, actual timeframes, actual work effort, and products that have been completed and approved.
Once the actual data has been captured, then the Project Plan can now be re-forecast, to show the remaining duration, costs, resources, and products yet to be created.
Because the Project Plan represents the high-level view of the project, then as the next Stage Plan is created and more day to day level detail is known, then this too is used to update the forecasted information within the Project Plan.
If the Managing a Stage Boundary process is being triggered as a result of a request for an Exception Plan, then the Project Plan will be updated as mentioned above but to include the detailed information from the newly created Exception Plan.
As part of updating the Project Plan, the Project Product Description should be checked and updated with any changes, for example the acceptance criteria may need to be refined. Also, any current issues on the risks arising as a result of planning should also be added to the Project Plan usually in the form of extra activities and resources.
It may well be that new or modified Product Descriptions and their related Configuration Item Records will also need to be created and included within the project plan.
Any changes required to the information contained within the Project Initiation Documentation such as strategies, controls, or project management team structure should also be added as appropriate to the Project Plan.
One of the seven principles of PRINCE2 is that projects have continued business justification, and the project board are only authorised to continue providing that the project remains viable.
However, projects do not take place in a static environment, and even if the project is progressing to plan, the outside world or business environment may be changing and the Business Case needs to be updated to reflect these changes and reviewed to ensure that it is still viable.
Since the executive of the project board is responsible for the Business Case then the project manager should consult with them, all business assurance, when reviewing or updating the Business Case.
An important activity here is to check that the risk appetite of those organisations involved remains the same or whether risk tolerances need to be redefined, in which case the risk register needs to be assessed and updated.The Benefits Review Plan was created immediately after the detailed Business Case, and this too needs to be updated at the end of each stage to record any results of possible benefit reviews undertaken during the stage just completed.
It is likely that the benefits may be different in some way to those planned and this will include the impact of any approved changes or new and modified risks.
A key input to updating the Business Case is the Project Plan. In particular implementation dates and project costs. Another important part of the Business Case is the investment appraisal, and the relevant data from the Project Plan and ongoing operational and maintenance timescales and costs should be used to recast the full investment appraisal.
For more information CLICK HERE



