- •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
Initiating a
Project (IP) Controlling a Stage (CS)
Closing a project (CP)
Delivery
Team Manager
-- Once during project-- Once per stage
-- Many times during stage
-- Once per Work Package
Notification -- Notification
Work Package
Work Package
Work Package Completed WP
MP Outputs Team Plans Checkpoint Reports
Auth.
-- Authorization
Managing Product Delivery (MP)
Quality Register
Com pleted WP
Mgmt Prod -- Management Product
Based on OGC PRINCE2® material. Reproduced under license from OGC
Products get created & quality checked
Pre-Project Initiation Stages - Execution
Fig 3.13 Controlling a Stage
The trigger for the “Controlling a Stage” process comes always from the Project Board Activity “Authorize a Stage or Exception Plan.”
Each Controlling a Stage process ends by triggering the process “Managing a Stage Boundary,” expect for the last stage, which most of the time is directly followed by the Closing a Project process.
Next, I will describe the relationship between Controlling a Stage and Managing Product Delivery, and the activity Authorize a Stage or Exception Plan.
Cs: Controlling a Stage / Managing Product Delivery
Assign Work to Teams using Work Packages
The Project Manager allocates Work Packages to the Team Leaders. A Work Package contains information on one or more products to be developed, which includes such information as product descriptions, planning data, and constraints. This becomes the agreement between the Project Manager and the Team Leader.
Corp..
Corporate or Programme Managementwww.Mgm tPlaza.com
Direction
Project Board
Project Notification
Authorize the project
Directing a Project (DP)
Authorize a Stage or Exception Plan
Give ad hoc direction
Ma na g ing P roduct De live ry
Work Package contains information on the products to be produced
Can happen many times in a stage
Management
Project Manager
Authorize Project
Approved PID
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
Advice
Ob jectives : Ma n a gin g P rod uct De live ryAgree work between PM & TM
Products are produced in the Activity “Execute a Work Package”
TM hands back complete work to PM
Tip : S m a ll P ro je c ts
No need for Team Manager
Team Members report directly to PM
Managing Product Delivery (MP)
Products get created & quality checked
Based on OGC PRINCE2® material. Reproduced under license from OGC