- 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
Set up the PRINCE2 project controls
PRINCE2 In Bite-Sized Chunks.
Set up the project controls.
There are two aspects to be considered here, one the controls needed by the project board, and two, the controls used by the project manager related to the work to be undertaken by the specialist team or team managers. The level of control needed will depend upon the project’s scale, the amount of risk, how complex, and how important the project is.
Many controls will have already been defined in the creation of the project’s four strategy documents, but they may not have necessarily been set up yet.
The main project controls may include the frequency and format of communication, the number of stages – in particular the end stage assessments, the system and mechanisms to capture and analyse issues and project changes, the application of management by exception including tolerances for the different management levels, and how would be delegated authority from one level of management to another will be monitored.The Project Brief should be reviewed to clarify whether any corporate or programme management strategies, standards or practices that relates to controls need to be applied to this particular project. The four management strategies mentioned previously should be reviewed to identify which controls need to be established.
Lessons from similar previous projects relating to project controls should be sought and applied as appropriate, these may have already been captured in the Lessons Log.
The Risk and Issue Registers should be reviewed, as the aggregated value of issues and risks will determine the detail and complexity of the control activities. The project board should be consulted and agreement reached as to where and when the management stage boundaries needs to occur so that adequate control can be applied.
The project management team structure role descriptions should be checked and enhanced with any agreed decision making authority where appropriate. This may even mean enhancing all be allocating roles as required.
As part of management by exception, corporate or programme management will have set project level tolerances. The project board need to agree stage level tolerances and optionally the project manager may set tolerances at work package level (although this may not need to be done at this point in time). Where appropriate these need to be confirmed including any escalation procedures.
All controls should be summarised in the Project Initiation Documentation and project assurance should be consulted to check that the proposed project controls are appropriate for the nature of the project.
Project board approval should now be sought for the project controls, all the project board may prefer to review them later as part of the Project Initiation Documentation.
For more information CLICK HERE



