PRINCE2® Overview
Course Description
This is a 2-day introductory course to PRINCE2® designed for those interacting with a PRINCE2® based project that require a sound understanding of how to commission, control or participate in a PRINCE2® project. It is a structured and practical introduction to PRINCE2® concepts and elements covering how PRINCE2® works in the real world. A variety of workshops and exercises are used to consolidate learning points and reinforce concepts.
Course Duration
2 days
Course Objectives
Following completion of this course delegates will be able to:
• Use PRINCE2® processes and templates to engage with the project community at start-up, during the running and at project close-out.
• Capture project scope in the Project Plan using Product Based Planning as a real world & real, practical, valuable tool (rather than the more common exam oriented approach).
• Ensure that Start-up and Initiation sets project controls (eg Change Control), project tolerances and
contingencies at the right level, and include auditable justified allowances for risk and change.
• Exercise project oversight: assessing the project’s performance from the perspective of Project Executive, Senior User, Senior Supplier and their project assurance responsibilities. Use the processes to hold the project to account.
• Use Management by Exception to retain project control without being overburdened by needless involvement.
• Fulfill the Senior User’s responsibilities to ensure a consensus view of the project’s end-point (i.e. outcomes) amongst the stakeholder community.
• Establish a control regime that balances formality (bureaucracy), agility, risk and cost.
• Close-out the project in an orderly fashion.
• Use PRINCE2® processes and templates to engage with the project community at start-up, during the running and at project close-out.
• Capture project scope in the Project Plan using Product Based Planning as a real world & real, practical, valuable tool (rather than the more common exam oriented approach).
• Ensure that Start-up and Initiation sets project controls (eg Change Control), project tolerances and
contingencies at the right level, and include auditable justified allowances for risk and change.
• Exercise project oversight: assessing the project’s performance from the perspective of Project Executive, Senior User, Senior Supplier and their project assurance responsibilities. Use the processes to hold the project to account.
• Use Management by Exception to retain project control without being overburdened by needless involvement.
• Fulfill the Senior User’s responsibilities to ensure a consensus view of the project’s end-point (i.e. outcomes) amongst the stakeholder community.
• Establish a control regime that balances formality (bureaucracy), agility, risk and cost.
• Close-out the project in an orderly fashion.
Course Content
PRINCE2® Overview
The Whole Thing On A Page; PRINCE2® Scope & Context; Main Elements of PRINCE2®; PRINCE2® Terminology; The Difference Between Management and Technical Stages; Planning Horizons
Process Models
Starting up a Process (SU)
The 10 Roles; 4 Levels of Controls; Organisation Structure Of The Project Board; Authorising Initiation (DP1)
Planning (PL)
Plans & Exceptions; Product Based Planning; The Steps Involved in Product-Based Planning; Product Based Planning Syntax; Plans: @Start, in Middle & @ End; Authorising a Project (DP2)
Controlling a Stage(CS) & Managing Product Delivery(MP)
Doing the work: CS1, 2, 9 & MP1, 2, 3; Exception Handling: CS3, 4, 8; Giving Ad-Hoc Advice (DP4); Day to Day Reporting & Steering: CS5, 6, 7
Managing Stage Boundaries(SB)
Authorising a Stage or Exception Plan (DP3)
Closing a Project (CP)
Confirming Project Closure (DP5); After the Project
Components & Related Elements
Organisation; Contents & Life-Span of a Business Case; Risk Concepts, Analysis and Management Processes; The Purpose of Controls; Tolerance; Controls @ Start, Middle & End of Stage or End of Project
Change (to/ from products)
Change Control Approach: Purpose & Technique ;Change & Issue Log Context; Change Authority; Link Between
Change Control and Configuration Management; Purpose of Configuration Management; Identification of Configuration Items; The Reasons For Version Control; Baseline & Release; Appendix E: The Filing Structure
Quality Review & Management
Purpose & Benefits of a Quality Review; Three Steps of a Quality Review 24.4.3; Quality Management Path
& Purpose; The Quality Management Responsibilities; The Project Quality Plan; The Product Description; Quality Depends on Specification; Customer’s Quality Expectations
Conclusion and Wrap-up
The Whole Thing On A Page; PRINCE2® Scope & Context; Main Elements of PRINCE2®; PRINCE2® Terminology; The Difference Between Management and Technical Stages; Planning Horizons
Process Models
Starting up a Process (SU)
The 10 Roles; 4 Levels of Controls; Organisation Structure Of The Project Board; Authorising Initiation (DP1)
Planning (PL)
Plans & Exceptions; Product Based Planning; The Steps Involved in Product-Based Planning; Product Based Planning Syntax; Plans: @Start, in Middle & @ End; Authorising a Project (DP2)
Controlling a Stage(CS) & Managing Product Delivery(MP)
Doing the work: CS1, 2, 9 & MP1, 2, 3; Exception Handling: CS3, 4, 8; Giving Ad-Hoc Advice (DP4); Day to Day Reporting & Steering: CS5, 6, 7
Managing Stage Boundaries(SB)
Authorising a Stage or Exception Plan (DP3)
Closing a Project (CP)
Confirming Project Closure (DP5); After the Project
Components & Related Elements
Organisation; Contents & Life-Span of a Business Case; Risk Concepts, Analysis and Management Processes; The Purpose of Controls; Tolerance; Controls @ Start, Middle & End of Stage or End of Project
Change (to/ from products)
Change Control Approach: Purpose & Technique ;Change & Issue Log Context; Change Authority; Link Between
Change Control and Configuration Management; Purpose of Configuration Management; Identification of Configuration Items; The Reasons For Version Control; Baseline & Release; Appendix E: The Filing Structure
Quality Review & Management
Purpose & Benefits of a Quality Review; Three Steps of a Quality Review 24.4.3; Quality Management Path
& Purpose; The Quality Management Responsibilities; The Project Quality Plan; The Product Description; Quality Depends on Specification; Customer’s Quality Expectations
Conclusion and Wrap-up
Who should attend?
This course is designed for delegates whose organisation uses a PRINCE2® based project management method. Alternatively, those wishing to introduce PRINCE2® to the organisation or whose sub-contractors or customers are using (or moving towards) PRINCE2® should attend this course.
Pre-requisites
None
Further information
This course is not intended to give formal PRINCE2® accreditation. For delegates wishing to obtain PRINCE2® accreditation, they should attend our PRINCE2® Foundation/Practitioner course.
