![](/user_photo/2706_HbeT2.jpg)
- •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
Last Controlling a Stage Process
Normally the project would continue to the next stage and this cycle would continue until all stages have been completed and the necessary products have been produced.
So let us assume that we have done a number of stages and the project will go from Controlling a Stage to the Closing a Project process, as the Managing a Stage Boundary process is normally not used at the end of the last stage (except if an Exception Plan needs to be created).
Юдина ______________________
Богданова ______________________
Cp: Closing a Project: Introduction and Objectives
Closing a Project and Premature Close
Normally
a Project
closes
after
all
the products
have
been produced
and delivered.
The
Closing
a Project
process
becomes
part
of the
last
stage
and the
Project
Manager
will
take
the necessary
action
to prepare
for
project
closure,
but
only
the
Project
Board
can
actually
close
a project.
Corp..
Corporate or Programme Managementwww.Mgm tPlaza.com
Direction
Project Board
Directing a Project (DP)
Authorize a Stage or Exception Plan
Give ad hoc direction
Closure Notification
close soon
Auth. project closure
Management
Project Manager
Authorize stage
Exception Report
(Issue / Change & Risk)
Highlight Reports
End Stage Report Next Stage Plan or Exception Plan
(SB) Managing a Stage Boundary
Controlling a Stage (CS)
Work Package
Work Package
Delivery
Team Manager
Work Package Completed WP
Managing Product Delivery (MP)
Advice
Premature Close
Closure Recommend. End Project Report FAR, Lessons Rpt Draft Closure Notificat.
Closing a project (CP)
Clos in g a P ro je c t (CP )
CP is part of last stage
Done instead of SB at end of project
Premature Close at any time
Premature Close triggered by Board
PM is resposible to prepare CP
Clo s in g a P ro ject: Ob jectives
Confirm products deliver & accepted
Handover products (see CM strategy)
Capture lessons learned (for future)
Ensure product support after project
Evaluate the project (EPR)
Prepare information for Board
Products get created & quality checked
Based on OGC PRINCE2® material. Reproduced under license from OGC
Stages - Execution
Close
Fig 3.20 Closing a Project
It’s also important to note that the Project Board can decide to shut down the project before its expected end. This is referred to as a Premature Close. This can happen at any time during the project. For instance, the project board might see that the business case is no longer valid, as the market price for such a product has reduced by 30% or there has been a change in government legislation that would reduce the future lifetime of the product.
A clear project end is necessary to avoid wasted resources and not allow the project to drag on. It also provides the opportunity for the Project Board to review the project against the Initial Project Plan.