Projectgovernance 140730202345 Phpapp02
Projectgovernance 140730202345 Phpapp02
Projectgovernance 140730202345 Phpapp02
Project Governance
Project Management is a well defined concept found in many
guidebooks and Bodies of Knowledge. Putting these guides
and BOK’s to work for the benefit of the enterprise is the role
of Project Governance
+ 2
Program
Management
! gov⋅ern [guhv-ern] – verb
! to rule over by right of authority: to govern a nation.
! to exercise a directing or restraining influence over; guide: the
motives governing a decision.
! to hold in check; control: to govern one’s temper.
! to serve as or constitute a law for: the principles governing a case.
+ 5
Project Governance
Project governance is the framework which ensures the project has been
correctly conceived and is being executed in accordance with best project
management practice within the wider framework of the firms of
organizations governance processes.
Effective project governance ensures projects deliver the value expected of
them. An appropriate governance framework ensures that all expenditure is
appropriate for the risks being tackled.
Project governance is not about micro–management, it is about setting the
terms of reference and operating framework, defining the boundaries and
ensuring that planning and execution are carried out in a way which ensures
that the project delivers benefits.
+ 7
Governance
Project
Governance
3.
How
do
we
know
we
are
being
successful
at
what
we’re
supposed
to
be
doing?
2.
How
are
we
going
to
do
what
we
said
we
would
do?
1.
What
do
we
want
to
do?
" Business
and
Technical
" Deliverables
Based
" Measures
of
Performance
Strategy
Planning
(MoP)
" CapaciCes
Based
Planning
" Assessment
of
increasing
" Measures
of
EffecCveness
maturity
(MoE)
" ConnecCons
to
the
" DefiniCons
of
physical
" Measures
of
Physical
delivery
of
business
value
progress
of
plans
Percent
Complete
Project Governance is the Primary Role of the Program Management Office
(PMO)
+ What’s the difference between 10
A mechanism to assess the compliance of the completed project to its original Deliverables Plan connected to
objectives identifying all stakeholders with an interest in the project business case
A process for the management and resolution of issues that arise during the project Issue tracking system
A process for the recording and communication of risks identified during the
Risk management system
project
+ 14
! OGC P3M3
The OGC P3M3
V2.0 defines 5 ! Maturity model for Project, Program, Portfolio
levels of maturity Management Maturity Model
for project,
program, and ! This framework is simple, well formed and in
portfolio
use in the UK for council, township, county and
management
processes. regional governments for IT management
P3M3 is “owned”
by the same ! It is a maturity model in the same way CMMI is
organization that a maturity model
“owns” ITIL
www.ogc.gov.uk
+ 16
Level 3: Defined
Process characterized for the organization and
is proactive
Level 2: Managed
Process characterized for projects
and is often reactive
Level 1: Performed
Process unpredictable, poorly
controlled and reactive
+ 17
Governing Projects by
Getting to Level 3 of the
OGC P3M3
A mature organization has the ability to
manage portfolios, programs, and projects
based on standard, defined processes.
+ Project, Program, and Portfolio 20
Level 4 – Managed
Each organizational element obtains and retains specific measures on its
project performance. These measures used to improve the quality of projects
Level 3 – Defined
Each organizational element has a centrally controlled project processes.
Individual projects flex within these processes to suit a particular project
Level 2 – Repeatable
Ensure that each project is run on its own processes and procedures to a
minimum specified standard
Level 1 – Initial
Recognize projects and run them differently from the ongoing business
+ 21
P3M3
The 25 (2+11+12)
Process areas of
OGC P3M3 include
all core Knowledge
Areas of PMBOK
+ 24
! Increased productivity
! Improved quality
Measureable Improvements by
moving between the Maturity
Model Levels
Moving from One Level to the Next
L1 to L2 L2 to L3 L3 to L4
Reduced SW Defects 12% 40% 85%
Reduced Cycle Time 10% 38% 63%
Reduced Costs 8% 35% 75%
Schedule Variance 145% 24% 15%
Data presented at 5th Annual CMMI technology Conference & User Group,
Denver Colorado, November 2005
+ 27