- •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 actions for Project Manager in Closing a Project
The Project Manager may first close the three register files and the daily log.
The Project Manager also creates a draft Project Closure Notification for the Project Board. This will be the notification document that will be sent out later to stakeholders by the Project Board once they have decided to close the project.
The last thing the Project Manager does is to Recommend Project Closure to the Project Board.
This can only be done once all other activities in Closing a Project have been done.
Dp: Authorize project closure
Project Board activities in “Authorize project closure”
Closing a Project correctly is the responsibility of the Project Board, while the Project Manager will prepare and provide the Project Board with the majority of the information required.
Corp..
Corporate or Programme Managementwww.Mgm tPlaza.com
Direction
Project Board
Directing a Project (DP)
Authorize a Stage or Exception Plan
Management
Project Manager
Exception Report
(Issue / Change & Risk)
End Stage Report Next Stage Plan or Exception Plan
(SB) Managing a Stage Boundary
Highlight Reports
Give ad hoc directionClosure Notification
close soon
Auth. project closure
Authorize P ro je c t Clos ure
Compare PID with Actuals
Closure Recommend. End Project Report FAR, Lessons Rpt Draft Closure Notificat.
Confirm Follow-on Action RecommendationsReview Lessons Report
Confirm products acceptance & handover
Review & Approve Benefits Review Plan
Confirm project has met Business Case
Approve End Project Report (ERP)
Advice
Premature Close
Controlling a Stage (CS)Closing a project (CP)
Outputs
Project Closure Notification (Output)
Distribute Lessons Report
Distribute Follow on Action Recommendations0
Delivery
Team Manager
Based on OGC PRINCE2® material. Reproduced under license from OGC
Stages - Execution
Close
Fig 3.22 Authorize project closure
PRINCE2 recommends the following actions for the Project Board:
Review the End Project Report, and compare it to the original plan.
Confirm who should receive the Follow on Action Recommendations. e.g.: the persons responsible for the maintenance
Review the Lessons Report and pass it on so it can benefit future projects.
Confirm that products have been handed over, and confirm user acceptance and maintenance for each product.
Review and approve the Benefits Review Plan, as reviewing the benefits will continue to be done after the project shuts down.
Confirm that the project has met the Business Case by comparing the current Business Case to the original one, comparing the Benefits, Cost, Risks, and Return on Investment.