Managing a Stage Boundary Outputs
The main outputs of Managing a Stage Boundary are the End Stage Report, the Next Stage Plan and the update to the Project Plan and Business Case. And as you now know, the Exception Plan will be created instead of the Next Stage Plan.
I will now briefly explain these:
The End Stage Report provides a detailed report on the results of the current stage by comparing the performance of the stage to the original stage plan used at the beginning of the stage.
The Next Stage Plan is a detailed day-to-day plan for the next stage and needs to be approved by the Project Board.
The stage plan for next stage is created near the end of the current stage, so this means that the Managing a Stage Boundary process starts before the end of the Controlling a Stage process.
The Project Plan is updated to incorporate the actual progress from the current stage, and it should also include the forecast planning for the next stage and should update time and cost data.
The Business Case: The end of each stage is a good time to update the Business Case and check if the project is still viable and worth doing. The Project Board is also interested to know that the benefits of the project can still be realized within the agreed parameters, which are time, cost, quality, risk and scope.
The Exception Plan: This plan is created only when the current stage goes beyond its tolerance level (e.g.: taking 15% longer than planned), and the Project Manager must therefore get authorization to complete the current stage.
- 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