![](/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
The Team Manager Role
The Team Manager has the responsibility to produce the products that were assigned in work packages by the Project Manager, and to provide regular status reports on their progress. This allows the Project Manager to monitor their work. The Team Managers create their own team plans to manage the development of the assigned products.
For small projects, the Team Manager may not be required, so the team members will report directly to the Project Manager
The prince2 Process Model Diagram
Process Model Diagram Introduction
I presume you are looking at the Process Model diagram in color: At first the Process Model diagram might seem like a bit too much information all at once, but do not worry. This course will explain the different parts of the model and guide you through it step by step, starting with the “Project Mandate” document and ending with the “Closing a Project” process.
I
suggest
that
you
print
out the
full
PRINCE2
Process
Model
diagram
in
color
(A4
landscape)
and refer
to it
while
reading
this
book.
You
can
download
the PRINCE2
Process
Model
diagram
from
our website.
Corp..
Project mandateCorporate or Programme Management
www.Mgm tPlaza.com
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
Give ad hoc direction
Closure Notification
close soon
Auth. project closure
Management
Project Manager
Req. to Initiate a Project
Project Brief + IS Plan
Project Starts
Auth. To Initiate
Project Init Doc
Req. Deliver Project?
Authorize Project
Approved PID
Authorize stage
Exception Report
(Issue / Change & Risk)
Highlight Reports
Advice
Premature Close
Closure Recommend. End Project Report FAR, Lessons Rpt Draft Closure Notificat.
End Stage Report Next Stage Plan or Exception Plan
(SB) Managing a Stage Boundary
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 approved
Pre-Project Initiation Stages - Execution Close
Fig 2.1 The PRINCE2 Process Model
Тишковец ______________________
Антонова ______________________