PROJstudy Process Chart Document and Reporting Structure Corporate or Programme Management Project Board Project Manager Team Manager Corporate/Programme Organisational Structure Important Points: Project Board Executive (1) Senior User (S) Senior Supplier (S) Project Assurance Change Authority Work Package Project Manager (1) User Assurance Business Assurance Supplier Assurance Team Manager (S) Project Support Quality Assurance Project Stakeholder Business User Supplier The Project © 2011 PROJstudy.com Ÿ Project Manager can be the Team Manager and/or Project Support for small projects Ÿ Project Assurance is independent of Project Manager. The roles of Business Assurance, User Assurance and Supplier Assurance should be done by 3 separate individuals. In small projects, Project Assurance can be done by the Project Board. Ÿ Quality Assurance is independent of project management team and is the responsibility of the corporate. Ÿ Project Manager can be the Change Authority for Work Packages. Ÿ The roles of Executive and Project Manager cannot be combined. Ÿ There can be only one Executive and one Project Manager. Project tolerances Stage tolerances Project Exception Highlight Report End Stage Report, Issue Report & Stage Exception Customer = Business + User ® So PRINCE2 projects are done in Customer/Supplier Environment Work package tolerances Check Point Report Raise an Issue
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
PROJstudy Process Chart
Document and Reporting Structure
Corporate or Programme Management
Project Board
Project Manager
Team Manager
Corporate/Programme
Organisational Structure
Important Points:
Project Board
Executive (1) Senior User (S) Senior Supplier (S)
Project Assurance
Change AuthorityWork PackageProject Manager (1)
User AssuranceBusiness Assurance Supplier Assurance
Team Manager (S)
Project Support
Quality Assurance
Project Stakeholder
Business
User
Supplier
The Project
© 2011 PROJstudy.com
Ÿ Project Manager can be the Team Manager and/or Project Support for small projects
Ÿ Project Assurance is independent of Project Manager. The roles of Business Assurance, User Assurance and Supplier Assurance should be done by 3 separate individuals. In small projects, Project Assurance can be done by the Project Board.
Ÿ Quality Assurance is independent of project management team and is the responsibility of the corporate.
Ÿ Project Manager can be the Change Authority for Work Packages.
Ÿ The roles of Executive and Project Manager cannot be combined.
Ÿ There can be only one Executive and one Project Manager.
Project tolerances
Stage tolerances
Project Exception
Highlight Report End Stage Report, Issue Report & Stage Exception
Customer = Business + User®
So PRINCE2 projects are done in Customer/Supplier Environment
Work packagetolerances
Check Point Report
Raise an Issue
PROJstudy Process Chart
Stage Plan
Mnemonics
Six Variables of Project
CostTimescaleQualityScopeRiskBenefits
CTQSRB
Processes
Starting up a Project Directing a ProjectInitiating a Project Controlling a StageManaging Product DeliveryManaging a Stage BoundaryClosing a Project
SDICPBC
------------- ----------------
----------------- ---------------
----- ---
------------------
------------ ------------------------
-------- -----------------------------
-------------------------- ------------------------------
----
--- ------
------------------------------
----------------- -----------------------
------------ -----
-------------------
------------- -------
-------- ----- -----
------ -------
---------------
-----------
SDICPBC
CTQSRB
ARFTASEER
BERSEPT
COQPRCP
Themes
Business Case Organization Quality Plans Risk Change Progress
COQPRCP
Principles
Continued Business justification Learn from Experience Defined Roles and Responsibilities Manage by StagesManage by Exception Focus on Products Tailor to suit the Project Environment
BERSEPT
Threat
Threat andOpportunity
Opportunity
Risk Responses
Avoid Reduce Fa
r Accept Share Exploit Enhance Reject
llback Trasfe
ARFTASEER
Hint:1. Refer 1st page of Appendix A for management products Types of management products: 1. Baseline management products:Define aspects of the project and once approved, are subject to change control. Benefits Review Plan Business Case Communication Management Strategy Configuration Management Strategy Plan Product Description Project Brief Project Initiation Documentation Project Product Description Quality Management Strategy Risk Management Strategy Work Packages
© 2011 PROJstudy.com
2. Records:Dynamic management products that maintain information regarding project progress. Configuration Item Records Daily Log Issue Register Lessons Log Quality Register Risk Register
3. Reports:Provide a snapshot of the statusof certain aspects of the project. Checkpoint Report End Project Report End Stage Report Exception ReportHighlight Report Issue Report Lessons Report Product Status Account
Starting up a Project Initiating a Project
Stage Plan for Initiation (First Stage)
Stage Plan for stage 2
Stage Plan for stage 3
Stage Plan for Final Stage + Plan for Closing theProject
Closure activities
Project Brief Project InitiationDocument & ProjectPlan
Stage 2 Stage 3 Final Stage
SB = Managing a Stage BoundaryCP = Closing a Project
SB SB SB CP
Initiating a Project
Types of issue Definition
Request for change A proposal for a change to a baseline.
Off-specification Something that should be provided by the project, but currently is not (or is forecast not to be) provided. This might be a missing product or a product not meeting itsspecification.
Problem/concern Any other issue that the Project Manager needs to resolve or escalate.
Related Documents
