- 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
Review the PRINCE2 Work Package Status
PRINCE 2 in Bite-sized Chunks
The Actual Heart of PRINCE2
The ‘Review Work Package Status’ activity
The job of the project manager is the first plan the work then to give it out to the team. This is done via the PRINCE2 work package. Once the team have accepted the Work Package they will then start creating the specialist products (executing a work package), and as a result of that, give regular progress reports to the project manager in the form of a Checkpoint Report.
This ensures that the project manager receives a regular assessment of the status of the work packages.

Of particular importance, is the progress being made in the creation of the specialist products. There are broadly three steps to this: first the product is created, and this would result in its draft status, then the quality check or quality review is carried - out independently from those who created the product, and finally approval is given by the appropriate person.
How often the Checkpoint Reports are created will be stated in the work package, and this also includes how formal such activities are to take place. For example it may be a simple e-mail sent perhaps once a week or it may be a meeting. The formality and regularity of the checkpoint reports will depend upon the level of risk, complexity, and experience and knowledge of the specialist team creating the products.
The project manager will want to gather progress information contained within the checkpoint reports in order to determine the progress being made.
The project manager will also want to assess the estimated time and effort used thus far, and also the estimated time and effort remaining for any unfinished work. This unfinished work may include current tasks or tasks yet to be started.
As part of accepting the work package, the Team Manager, or the team members themselves may have created a Team Plan. This Team Plan may have been passed in full detail to the project manager.
But if commercial circumstances and questions of confidentiality are considered, the project manager may only receive a milestone extract from the Team Plan.. The project manager will use this information to determine whether the work is being completed on time and to budget.
In addition, the Project Manager will ensure that the specialist products are meeting their quality criteria as laid out in their Product Descriptions, and that issues and risks are being managed appropriately.
The project manager will review entries in the quality register to determine the actual current status of all quality management activities that have been undertaken, and liaise with the configuration management people (Project Support), to confirm that the Configuration Item Records for every products matches its current real-world status.
The project manager will also review the risk and issue registers and if required update them with the latest status.
Throughout the stage the project manager will use the stage plan as the baseline reference points against which to manage monitor and control the stage. Therefore the stage plan should be updated at regular points with the latest status, current forecasts, and any adjustments needed to reflect future progress.
There is another activity, called a review of the stage status which I shall be discussing in another article. However it is important that you understand that this activity, review the work package status, will now be used to review the stage status to ensure that the stage is continuing on plan and within tolerances.
For more information CLICK HERE



