1. 13/11/2018
PRINCE2
Pedro Alexander Romero
Dublin 2017

2. 13/11/2018
AGENDA
Overview
Methodology & Principles
Themes
Process

3. Project Management is ?
Is the planning, delegating, monitoring and control of all aspects of the project.
Aim, to achieve the project objectives within the expected performance targets for:
Time
Cost
Quality
Scope
Benefits and
Risk

4. Project Management and PRINCE2
PRINCE2 method does not cover all skills needed by the Project Manager to control a project.
PRINCE2 is a methodology that was developed by Project Managers asking themselves “Why do projects fail?”
Corporate
Ethos, values, standards,
procedures, strategic objectives
Project
Leadership / People skills
Financial
Project Management
PRINCE2

5. Why do project fail ?
Lack of leadership or senior management ownership
Poor or no communication with stakeholders
Lack of attention to benefit
Poor or no controls within the project
Poor measurable objectives
Insufficient definition of quality …
“Happy families are all alike; each unhappy family is unhappy in its own way.”
Tolstoy

6. PRINCE2
Standing for PRojects IN Controlled Environments, PRINCE2 is the world’s most adopted project management framework, with over one million practitioners.
It provides invaluable guidance that gives individuals and organizations alike the essentials of running a project.
Best of all, PRINCE2 is easy to learn and flexible enough to adapt to all types of project.
Owner
AXELOS is a joint venture set up in 2014 by the Government of the United Kingdom and Capita, to develop, manage and operate qualifications in best practice, in methodologies formerly owned by the Office of Government Commerce 

7. PRINCE2 The PRINCE2 Definition of a project:
A temporary organization that is created for the purpose of delivering one or more business products according to an agreed Business Case
Key benefits of PRINCE2:
Ensures projects are delivered to agreed quality, within budget and timescale
BUDGET
Desired targets met, on time every time. No surprises, just seamless project management
TIMESCALE
QUALITY
Proven methods and globally-recognized solutions, for total success
Flexible enough to fit in with any budget – regardless of project size

8. PRINCE2 Uses a four-step procedure to control the project
Plan
Delegate
Monitor
Control
Plan: We agree work with our subordinates
Delegate: We authorize the subordinates to perform the work
Monitor: We keep an eye on the agreed work to make sure all is going as planned - our subordinates need to inform us as soon as they forecast that this will not be the case (allowing us to Manage By Exception)
Control: When alerted to an actual or forecast deviation of the agreed work we step in to authorize corrections

9. It is NOT a magic formula for success
What PRINCE2 is Not
Project Management Software
Just for large formal projects in large Organizations
About Techniques
About people & leadership skills, financial controls
It is NOT a magic formula for success

10. PRINCE2: Can you afford not to use it ?
Each and every project you work on has a lot riding on it. Deadlines have to be met, solutions have to be found. That’s where PRINCE2 comes in.
In the fast-moving world of 21st century business, Governments and Business both benefit from the true global best practice standards delivered through PRINCE2.
So here’s the question: can you afford not to benefit from all that PRINCE2 offers you?

11. PRINCE2 Benefits: Product focused Process based
Recognized best practice
Tailorable, scalable and flexible
Widely used in public and private sector
There is not license fee

12. Benefits for an Organization
Improved
communication
effectiveness
Improved cost
control
Improved focus
Unite teams and processes
Influence
the organizational
culture
Improved trust
alignment
PRINCE2: improved project
delivery, improved performance,
improved business results

13. Benefits: FOR AN INDIVIDUAL
PRINCE2: successful project
management, improved project
delivery, enhanced career
advancement.
Qualifications
recognized
around
the world
How to start
Your projects
Improve your
position
How to improve
your delivery
Terminology that
is common
How to close
your
projects
Clearly
understand
your role
How to
structure
a project
Structured
approach

14. Methodology & Principles
13/11/2018
AGENDA
Overview
Methodology & Principles
Themes
Process

15. Methodology (1/2)
To be a true PRINCE2 delivery, seven principles need to apply to any project (whatever the size). These key themes resonate throughout each project, with processes tailored across a wide variety of sectors and different roles providing a solid framework to deliver the desired result: on time, on budget and always to the very highest standard.
The PRINCE2 Project Methodology consists of…
7 Principles
7 Themes
7 Processes

16. Methodology (2/2) If a Project was a cake PRINCIPLES THEMES PROCESSES
Wash your hands
Be careful with
Knives
Measure carefully
THEMES
Ingredients:
Chocolate
Egg
Sugar
PROCESSES
Directions:
Heat Oven
Grease tin
Mix ingredients
Cook 20 min
Tailor
Adjust for size
and situation

17. Tailoring PRINCE2 for your projects (1/3)
Tailoring is Not…
Cherry-picking parts of the method
Ignoring the principles
Leaving out process or themes

18. Tailoring PRINCE2 for your projects (2/3)
THEMES
Adding additional themes
Procurement HR
Communications
Legal
Financial
Health and Safety
THE 7 PROCESS
Adjust formality to project size
Start up a project + Initiate a project
Control a stage + Manage Product delivery

19. Tailoring PRINCE2 for your projects (3/3)
Documentation / Information
Scope
Size
Detail
Roles and Responsibilities
Adjust to project size
Adjust to power structure

20. Principles Ensure continuous business justification
Learn from experience
Define roles and responsibilities
Manage by stages
Manage by exception
Focus in products
Tailor to the project environment

21. Principles and Themes relationship
ORGANIZATION
PRINCE2
Defined roles and
responsibilities
QUALITY
PLANS
Focus on
products
Manage by
stages
BUSINESS CASE
Continued business
justification
PROGRESS
Manage by
exception
CHANGE
Apply to all Themes
RISK
Tailoring
Learn from
experience

22. 13/11/2018
AGENDA
Overview
Methodology & Principles
Themes
Process

23. Themes PRINCE2’S core themes apply to every type of project.
Business Case
Explain the purpose and justification of the Project
Organization
Describes essentials roles and responsibilities
Quality
How the project requirements and specifications will be
defined
Plans
Shows what a plan should contain and how it should be developed
Risk
The procedures followed to effectively manage
risks
Change
How issues and changes will be managed
Controls
Defines the stages, tolerance, and reporting arrangements for the project
PRINCE2’S core themes apply to every type of project.

24. Themes: Business Case (1/2)
Written to justify starting a Project
Updated to reflect current status
Suggestion of type of information we could include:
Reasons
Options
Expected Benefits
Expected Dis-benefit
Timescale
Costs
Major Risks

25. Themes: Business Case (2/2)
Lifecycle
Create an Outline Business Case to justify starting a project
Approve the Business case after start up, after initiation and each stage boundary
Refine the Outline into a full Business Case
Update the Business Case to reflect the project progress at the end of a stage
If risks or issues arise, review the business case for impact
Review the Business Case to assess if any benefits have been achieved and identify benefits to to be measured post project
Starting up a Project
Directing a Project
Initiating a Project
Managing a Stage Boundary
Controlling a Project
Closing a Project

26. Themes: Organization
Roles need to be clearly assigned and responsibilities defined before any
work is attempted on the project
Project Board
Senior User(s) Project Executive Senior Supplier(s)
Project Assurance
Change Authority
User Business Supplier
Project Manager
Team Manager Project Support

27. Themes: Quality
The key to getting the quality aspects right in a project is to start by
understanding what your customer's quality expectations are.
Product Specifications:
Defines criteria that should be met for the deliverable to be considered
acceptable to the customer
Acceptance Criteria:
The mínimum specifications needed by customers for them to “accept”
the product/solution
High Level Project Requirements
Quality Management Strategy

28. Themes: Plans (1/2) When is it all going to happen ?
How much will it cost ?
How long will it take ?

29. Themes: Plans (2/2) Steps to create a Plan Design the plan
Define and analyse products
Indentify activities and dependencies
Prepare estimates
Prepare the schedule
Analyse the risks
Document the plan

30. Themes: Risk (1/2)
An uncertain event or set of events that if they were to occur, would have
either a positive or negative impact on the project
Threat: Negative Impact
Opportunity: Positive Impact
Risk Register
Issue Register

31. Themes: Risks (2/2) Managing Project Risks Identify Assess Plan
Implement the Plan
Communicate the status

32. Themes: Change (1/2)
Despite the best planning, our customers sometimes want to add in something
extra or change something.
Request for Change Issue:
When a customer decides they want to change, add, or remove something
from an agreed specification
Off-Specification Issue:
Where a product has been created and has failed to meet the
specification defined
Problem Issue:
A general type of issue covering any people, money, or time problems
that arise and have to be dealt with.

33. Themes: Change (2/2) Managing Issues Capture the issue in the register
Examine the issue
Propose the best solution
Decide on next course of action
Implement the solution

34. Themes: Controls
Addresses how the reporting and monitoring arrangements will be handled
on a project
Defines:
Tolerances for the project
Where the stages will be

35. 13/11/2018
AGENDA
Overview
Methodology & Principles
Themes
Process

36. Processes (1/3) The activities that need to be done on a project
Start Up a Project (SU): This is a very short pre-project process that gathers the necessary data to start the project.
Directing a Project (DP): This process is for Senior Management and this course will show how the senior management controls the project.
Initiating a Project (IP): This process examines the justification of the project and creates the Project Initiation documents, which include the Project Plan.
Managing a Stage Boundary (SB): This process provides a controlled way to complete a stage and plan the next one.
Controlling a Stage (CS): This process describes the Project Manager’s day-to-day monitoring and control activities. This is where the Project Manager spends most of their time during a project.
Managing Product Delivery (MP): This process delivers the products. It is where the products (Specific Products) that the users will use get produced by the team members.
Closing a Project (CP): This process confirms delivery of the products and the Project Manager prepares the project for closure.

37. Processes (2/3) DP SB SB CP IP CS CS MPD MPD SU
1 Starting up a Project
2 Initiating a Project
3 Directing a Project
4 Controlling a Stage
5 Managing Product Delivery
6 Managing Stage Boundaries
7 Closing a Project
Example of where process would fit into a four stage project DP
Directing SU SB SB CP
Managing IP CS CS
MPD
MPD
Delivering
Stages of a project

38. Processes (3/3)
The activities that need to be done on a project

39. 13/11/2018
thanks you.