- 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 Progress reporting
PRINCE2 In Bite Sized Chunks.
Project progress reporting.
How often progress reporting is done, depends upon how much control is needed on the project. For example:
During the design stage for example, looser control may be needed than during later management stage, if the team is highly experienced then less frequent reporting may be appropriate, whereas for an inexperienced team the Project Manager may wish to increase the frequency of reporting until sufficient confidence has been gained on the capability of the team.
Within PRINCE2, the following are the management products that are used:
Checkpoint Report. The Team Manager will produce this to provide the Project Manager with details of progress against the Work Package which will include the frequency of Checkpoint Reports required. The Project Manager will consolidate Checkpoint Reports and use these as part of the progress assessment when reviewing stage status and leading to the creation of Highlight Reports.Highlight Report. The Project Manager produces this report on management stage progress for the Project Board. The Project Board will determine the frequency of Highlight Reports required, either for the whole project or stage by stage, and document this in the Communication Management Strategy.
The Highlight Report allows members of the Project Board to manage by exception between end stage assessments as they are aware of the time to consider or reject the recommendations in the Issue Report.
If an Exception Plan is requested, the Project Board will conduct an exception assessment, similar to the end stage assessment, to review and approve the Exception Plan. The Project Board may also remove the cause, accept and adjust tolerance, or request more time to consider or reject the recommendations in the Issue Report.
Project-level exceptions. If project tolerances to be exceeded, the Project Board no longer has the authority to manage the project and must escalate this to corporate or programme management for a decision. The Project Board may request the Project Manager to produce an Exception Plan for the project.
Work-Package-level exceptions. Having agreed Work Package tolerances with the Team Manager, the Project Manager will be kept informed of progress through regular Checkpoint Reports. If a Work Package is forecast to exceed its tolerances, the Team Manager should bring this to the attention of the Project Manager by raising an issue. The Project Manager will advise of any corrective actions if required.
Stage-level exceptions. If the stage is forecast to exceed its tolerances, the Project Manager
should first produce an Issue Report to capture and analyse the details of the deviation and then provide an Exception Report for the Project Board. Based on information in this report, the Project Board may request that the Project Manager produces an Exception Plan to replace the plan that was forecast to exceed tolerance.
Within the Communication Management Strategy, the Project Board can request copies of the Highlight Report be sent to other interested parties outside the project. They may also issue the Highlight Report (or a summary of it) to corporate or programme management End Stage Report. End Stage Report. This is produced by the Project Manager towards the end of each management stage, providing the Project Board with the information on the progress to date, the overall project situation and, along with the next Stage Plan, sufficient information to ask for a Project Board decision on what to do next with the project
End Project Report. This is produced by the Project Manager towards the end of the project, during the Closing a Project process, and is used by the Project Board to evaluate the project and authorize closure.
For more information CLICK HERE



