Project Organization Introduction
Before we start the Process Model Introduction, it is necessary to take a brief look at the Project Organization. as these terms are used during the rest of this course.
This is a very simple overview and the diagram shows the four levels of a Project Management Structure (also called “Project Organization”).
The Project Management Team has just three levels. The top level is the Project Board level and the lower level is the Team Manager level. The project team is a temporary structure; it is created for the project and is disbanded once the project is completed.
Corp / Programme Management
Project Manager
Senior UserProject Board
Project Board
Senior User
Executive
Senior Supplier
Corp / Programme Management
Project Management Team
Four Levels of Management
Executive Senior Supplier
Project Manager
Team Manager
Team Manager
Fig 1.1 Project Management Structure / Project Organization
At the top of the Project Management Structure, you have the Corporate or Programme Management Level. This level is outside the project, so they do not participate in the project and therefore they are not a part of the project team. More and more companies now have PMO's, which stands for Programme Management Office, and can also have other names like Programme Office and Project Office.
The Project Board is responsible for the success of the project and has the necessary authority to take decisions and approve all major plans for the project. They approve the completion of each stage and authorize the start of the next. We refer to this as Directing a Project.
- 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