- •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
Direction
Project Board
Initiation Notification
Starting up a Project (SU)
Authorize initiationProject Notification
Authorize the project
Directing a Project (DP)
Authorize a Stage or Exception Plan
Management
Project Manager
Req. to Initiate a Project
Project Brief + IS Plan
Project Starts
Auth. To Initiate
Project Init Doc
Req. Deliver Project?
Authorize stage
End Stage Report Next Stage Plan
(SB) Managing a Stage Boundary
Ma na g ing a S ta ge B ounda ry
Check that planned products are produced
Assure the Project Board work is done
Create Lessons Report (optional)
Create the “End Stage Report”
Initiating a
Delivery
Team Manager
-- Once during project-- Once per stage
Ma in Inputs
Init. Stage Plan Project Initiation Documentation
Outputs
SB End Stage Report Next Stage Plan
-- Many times during stage
-- Once per Work Package
Notification -- Notification
Up d a te d
Project Init. Doc's
Auth.
-- Authorization
Business Case
Risk & Issue Register...
Mgmt Prod -- Management Product
Based on OGC PRINCE2® material. Reproduced under license from OGC
Pre-Project Initiation
Fig 3.11 Managing a Stage Boundary process after IP
Inputs:
The main inputs are:
the Project Initiation Documentation to compare with Initiation Stage Plan
the Initiation Stage Plan
and of course, all the register files (Quality, Issue, Risk)
Outputs:
The Stage Boundary’s outputs are:
the End Stage Report (a report on the stage just completed, the Initiation Stage)
the Next Stage Plan
Dp: Authorize the project
Authorize the project is the 2nd control point and 2nd Activity for the Project Board. The end of the Initiation Stage is the trigger for the “Authorize the project” activity. The Project Board confirms the project’s objectives and the scope is clearly defined and understood. They can decide to stop the project, ask for further information, or give authorization for the project to continue.
The “Authorize the project” activity has the following input and outputs:
Inputs
Project Initiation documentation
Request to Deliver a Project
Outputs:
As you can see in the diagram, there is one authorization, one approval and one notification
Authorization : Authorize the Project so the project can start
Approval : Approve the Project Initiation Documentation
Notification : To the Corporate or Programme Management that the project has started
Corp..
Project mandateCorporate or Programme Management
www.Mgm tPlaza.com