![](/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
What is a Programme?
A programme is a temporary flexible organization structure created to coordinate, direct and oversee the implementation of a set of related projects and activities in order to deliver outcomes and benefits related to the organization's strategic objectives.
That
is what you
call
a long
definition,
so a
simpler
way
to think
of this
is:
“a programme is a group of related projects in an organization”
If there is no programme in place, Corporate Management will be the top layer. This is the term that PRINCE2 uses to refer to a higher level of management in a company.
Organization Roles
The Project Board has three Roles, which are: The Executive, The Senior User and The Senior Supplier.
The Executive Role
The Executive is the main person responsible for the project, and is supported by the Senior User and Senior Supplier. The Executive represents the business interests of the project and owns the business case. The role of the Executive gives a single point of accountability for the project.
Usually the Executive is responsible for designing and appointing the project management team, including the rest of the Project Board and Project Manager.
Project Manager
Senior UserProject Board
Project Board
Senior User
Executive
Senior Supplier
Project Management Team
Executive Senior Supplier
Project Manager
Team Manager
Team Manager
![](/html/2706/242/html_IoQnVq4Jw2.2DWb/htmlconvd-RZJ79j_html_c7b97f5b42841083.gif)
The Senior User Role
The Senior User represents the user interests and is responsible for the specification. They specify the needs of the users and check that the final products meet the required specification. Their main concern throughout the project is “Will it work?”
The Senior User also specifies the expected benefits at the start of the project and reports to the project board on the benefits that are being realized during the project.
The Senior Supplier Role
The Senior Supplier represents the interests of those designing, developing, facilitating and implementing the project’s products. Their main concern throughout the project is “Can it be done?” and whether it can be done within the agreed time, cost and quality requirements.
The Project Manager Role
The Project Manager is appointed by the Executive with approval from Corporate or Project Management. The Project Manager runs the project on behalf of the Project Board on a day-to-day basis and has the responsibility to produce the required products to the required quality within the specified time and cost.
There are many different facets to the role of project management, such as Communication – in fact, it is estimated that more than 70% of a project manager’s time is spent on Communication, but also on Cost Management, Quality, Product Status, Changes, User Needs, Monitoring and Planning.