Program Management and Project Management
Program Management and Project Management
Program Management and Project Management
Management
Chapter 3
4th Edition
Programme
management and
project evaluation
2
©The McGraw-Hill Companies, 2005
Main topics to be covered
• Programme management
• Benefits management
• Project evaluation
– Cost benefit analysis
– Cash flow forecasting
• Project risk evaluation
3
©The McGraw-Hill Companies, 2005
Programme management
• One definition:
‘a group of projects that are managed
in a co-ordinated way to gain benefits
that would not be possible were the
projects to be managed independently’
Ferns
4
©The McGraw-Hill Companies, 2005
Programmes may be
• Strategic
• Business cycle programmes
• Infrastructure programmes
• Research and development
programmes
• Innovative partnerships
5
©The McGraw-Hill Companies, 2005
Programme managers versus project
managers
Programme manager Project manager
– Many simultaneous – One project at a time
projects – Impersonal
– Personal relationship relationship with
with skilled resources resources
– Optimization of – Minimization of
resource use demand for
– Projects tend to be resources
seen as similar – Projects tend to be
seen as unique
6
©The McGraw-Hill Companies, 2005
Projects sharing resources
7
©The McGraw-Hill Companies, 2005
Strategic programmes
• Based on OGC approach
• Initial planning document is the Programme
Mandate describing
– The new services/capabilities that the programme should
deliver
– How an organization will be improved
– Fit with existing organizational goals
• A programme director appointed a champion for
the scheme
8
©The McGraw-Hill Companies, 2005
Next stages/documents
• The programme brief – equivalent of a feasibility
study: emphasis on costs and benefits
• The vision statement – explains the new capability
that the organization will have
• The blueprint – explains the changes to be made to
obtain the new capability
9
©The McGraw-Hill Companies, 2005
Benefits management
developers users organization
use for
the
benefits
application
build
to
deliver
•Providing an organization with a capability does not guarantee
that this will provide benefits envisaged – need for benefits
management
12
©The McGraw-Hill Companies, 2005
Benefits - continued
• Risk reduction
• Economies
• Revenue enhancement/acceleration
• Strategic fit
13
©The McGraw-Hill Companies, 2005
Quantifying benefits
Benefits can be:
• Quantified and valued e.g. a reduction
of x staff saving £y
• Quantified but not valued e.g. a
decrease in customer complaints by x%
• Identified but not easily quantified –
e.g. public approval for a organization
in the locality where it is based
14
©The McGraw-Hill Companies, 2005
Cost benefit analysis (CBA)
21
©The McGraw-Hill Companies, 2005
Internal rate of return
22
©The McGraw-Hill Companies, 2005
Dealing with uncertainty: Risk
evaluation
• project A might appear to give a better return than B
but could be riskier
• Could draw up draw a project risk matrix for each
project to assess risks – see next overhead
• For riskier projects could use higher discount rates
23
©The McGraw-Hill Companies, 2005
Example of a project risk matrix
24
©The McGraw-Hill Companies, 2005
Decision trees
25
©The McGraw-Hill Companies, 2005
Remember!
• A project may fail not through poor
management but because it should never
have been started
• A project may make a profit, but it may be
possible to do something else that makes
even more profit
• A real problem is that it is often not possible
to express benefits in accurate financial terms
• Projects with the highest potential returns are
often the most risky
26
©The McGraw-Hill Companies, 2005