Cs: Controlling a Stage – Give ad hoc direction
The Controlling a Stage process has two main outputs, which are inputs to the Project Board Activity “Give ad hoc direction.” These are the Highlight Report and the Exception Report. There is also one input from the Give ad hoc direction activity, which is “Guidance and Advice.” Here is a bit more about these.
The Highlight Report
This is a regular report on the stage progress. It is created by the Project Manager and sent to the Project Board on a time-driven frequency, e.g.: every two weeks.
The report provides a summary of the stage versus the stage plan, and also information on tolerances, potential issues, products completed, next work packages and corrective actions.
The Exception Report
This report is only created if the current stage will not finish according to the plan and within tolerances, so the Project Manager must alert the Project Board.
The Exception Report provides an overview of why the stage will most likely go out of tolerance, and then includes different options to get the project back on track. It also assesses the impact on the business case, as this issue will most likely increase the cost of the project.
The Project Manager recommends one of the options in the Exception Report to the Project Board
Note: If the Project Board agrees with the Exception Report (if they agree with the recommended options or one of the other options), they will request an Exception Plan, which will replace the current Stage Plan and therefore allow the Project Manager to complete the current stage.
Corp..
Corporate or Programme Managementwww.Mgm tPlaza.com
- Version 1.0g
- The tag Introduction to prince2
- Course Objectives – Classroom Preparation Course
- Course Contents
- Organization
- Project Organization Introduction
- What is a Programme?
- Organization Roles
- The Executive Role
- The Senior Supplier Role
- The Project Manager Role
- The Team Manager Role
- The prince2 Process Model Diagram
- Process Model Diagram Introduction
- Direction
- Initiating a
- Delivery
- Process Model Using Color
- Four Management Levels
- Process Model – Processes
- Initiating a Project (ip)
- Exercise Diagram
- Work Package mp Outputs
- The prince2 Process Model
- Direction
- Delivery
- Project Mandate Contents
- Direction
- Delivery
- Su: Starting Up a Project
- Starting Up a Project: Three main deliverables
- Starting Up a Project Activities
- Direction
- Delivery
- Su: Project Approach
- Direction
- Delivery
- Карпова ______________________
- Su: Assemble Project Brief
- Direction
- Delivery
- Su: Plan the Initiation Stage
- Plan the Initiation Stage Tasks
- Direction
- Delivery
- Request to Initiate a Project
- Dp: Authorize initiation
- Direction
- Ip: Initiation Stage
- Initiating a Project Process introduction
- Direction
- Delivery
- Initiating a Project Process – 8 Activities
- Ip: Project Initiation Documentation (pid)
- Project Initiation Documentation
- Project Initiation Documentation Contents
- Direction
- Delivery
- Sb: Managing a Stage Boundary after the Initiation Stage
- Direction
- Delivery
- Inputs:
- Dp: Authorize the project
- Direction
- Delivery
- Cs: Controlling a Stage
- Direction
- Initiating a
- Delivery
- Cs: Controlling a Stage / Managing Product Delivery
- Assign Work to Teams using Work Packages
- Direction
- Delivery
- Initiation Stages - Execution
- Managing Product Delivery Objectives
- Mp: Managing Product Delivery: Outputs
- Direction
- Delivery
- Initiation Stages - Execution
- Cs: Controlling a Stage – Give ad hoc direction
- Direction
- Delivery
- Initiation Stages - Execution
- Cs: Project Manager Day to day activities
- Direction
- Delivery
- Work Package
- Initiation Stages - Execution
- Sb: Managing a Stage Boundary
- Managing a Stage Boundary and Objectives
- Direction
- Delivery
- Initiation Stages - Execution
- Managing a Stage Boundary Outputs
- Dp: Authorize a Stage or Exception Plan
- Authorize a Stage or Exception plan
- Direction
- Delivery
- Initiation Stages - Execution
- Exception Plans - Authorize a Stage or Exception Plan Activity
- Last Controlling a Stage Process
- Cp: Closing a Project: Introduction and Objectives
- Closing a Project and Premature Close
- Direction
- Delivery
- Closing a Project Objectives
- Cp: Closing a Project Outputs
- Closing a Project Outputs
- Direction
- Delivery
- Last actions for Project Manager in Closing a Project
- Dp: Authorize project closure
- Project Board activities in “Authorize project closure”
- Direction
- Delivery
- “Authorize project closure” activity outputs
- Summary
- Course Summary
- Direction
- Initiating a
- Delivery
- Learn Thru Questions
- Introduction
- About Learn Thru Questions
- Introduction to prince2
- Acknowledgements
- Distribution Copyright
- Customize this book
- About the Author
- The prince2 Training Manual: Book
- About tag
- The Process Model Learn Thru Questions
- Appendix a
- Appendix b Simple Glossary
- Issue Register