SlideShare a Scribd company logo
Five Immutable Principles of Project Success 
Glen B. Alleman 
glen.alleman@niwotridge.com 
+1 303 241 9633
Today We Will Learn … 
There many – maybe too many 
– methods for successfully 
managing a project. 
LO1 
LO2 
LO3 
But, no matter how many, 
each must possess 5 
Immutable Principles to be 
successful , no matter the 
domain, context. 
We need to assure our work 
is guided by these 5 Project 
Management principles to 
increase the probability of 
success 
We need to remember, Yogi’s advice … 
In theory, there is no difference between theory and practice. In 
practice there is. 2/58
Why 
Are 
Deliverables 
the 
Best 
Measure 
of 
Progress? 
Because 
the 
customer 
contracted 
for 
a 
“Capability” 
We 
need 
the 
capability 
to 
fly 
to 
LOE, 
with 
4 
on 
board, 
dock 
at 
ISS, 
stay 
for 
90 
days, 
and 
return 
safely
The 5 Immutable 
Principles of Success 
Project success does not start with the PMBOK® contents. 
These are just a guide – as the name says 
PMBOK® shows us the components of a method, but does 
not show us how to put these components together.
Immutable Principles Project Success 
1. Where Are We Going? 
2. How Do We Get 
There? 
3. Do We Have Enough 
Time, Resources, And 
Money To Get There? 
4. What Impediments Will 
We Encounter Along 
The Way? 
5. How Do We Know We 
Are Making Progress? 
Glen B. Alleman, Copyright © 2012 5/34
Q1. Where Are We Going? 
Eliciting Requirements Is Highly Domain Dependent 
“Design and integrate 18 major weapon systems and platforms 
simultaneously within strict size and weight limitations, while 
synchronizing the development, demonstration, and production of 
as many as 157 complementary systems with the Future Combat 
System content and schedule.” (This is an actual requirement) 
“Implement the 8 stories for our new 
warehouse inventory tracking system 
using the existing web site platform as 
a starting point.” 
Glen B. Alleman, Copyright © 2012 6/34
Three 
steps 
to 
success 
! Plan 
– 
a 
strategy 
for 
the 
successful 
compleIon 
of 
the 
project. 
! Schedule 
– 
the 
steps 
needed 
to 
fulfill 
the 
Plan. 
! ExecuBon 
– 
the 
physical 
performance 
of 
the 
steps 
needed 
to 
deliver 
the 
results 
defined 
in 
the 
Plan. 
Glen B. Alleman, Copyright © 2012 7/34
Scheduling 
Always 
comes 
aOer 
Planning 
! What 
are 
the 
individual, 
dependent 
and, 
sequenIal 
steps 
needed 
to 
deliver 
these 
capabiliIes? 
! The 
schedule 
has 
duraIons, 
dependencies, 
Iming, 
dates, 
resources 
and 
other 
things 
related 
with 
the 
Plan. 
! The 
idea 
that 
these 
steps 
“emerge” 
is 
fanciful 
in 
many 
Glen B. Alleman, Copyright © 2012 situaIons. 
8/34
Q2. How Do We Get There? 
Some problems respond 
to lightweight 
approaches, like 
Scrum, DSDM, Crystal, 
and XP as product 
development methods. 
Others require more 
complex approaches, 
like a System of 
Systems (SoS) spiral 
development processes. 
In all cases a disciplined 
approach increases the 
probability of success – 
no matter the complexity 
of the problem or the 
solution 
This approach works 
well when we don’t 
know what “done” 
looks like with enough 
clarity 
So 
Does 
This! 
Glen B. Alleman, Copyright © 2012 9/34
Q3: Do We Have Everything We Need? 
Glen B. Alleman, Copyright © 2012 10/34
Q3. Do We Have Enough Time, Money, 
And Resources To Get There? 
In the resource management business, 
optimism is always the source of trouble 
A Common Problem A Simple Solution 
We have undue optimism 
Use documented procedures – no matter the 
method – for estimating and planning using 
historical data. 
We attempt to avoid risk and 
uncertainty 
Understand and prioritize risks for each critical 
component empowers management and staff. 
Use this knowledge to control your optimism. 
We rely too much on intuitive 
judgment 
Simple statistical models are more often correct 
than the human judgment. 
Have the number to back up your intuition. 
The Rational Planning of (Software) Projects, Mark C. Paulk, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 
15213–3890 
Glen B. Alleman, Copyright © 2012 11/58
Q4: What Are the Impediments to Getting There? 
Glen B. Alleman, Copyright © 2012 12/34
Q4. 
Five 
Fundamental 
Principles 
of 
Risk 
Management 
1. Hope 
is 
not 
a 
strategy 
2. No 
single 
point 
esImate 
of 
cost 
or 
schedule 
can 
be 
correct 
3. Cost, 
Schedule, 
and 
Technical 
Performance 
are 
inseparable 
4. Risk 
management 
requires 
adherence 
to 
a 
well 
defined 
process 
5. CommunicaIon 
is 
the 
Number 
One 
success 
factor 
Glen B. Alleman, Copyright © 2012 13/34
No 
Point 
EsBmate, 
By 
Itself, 
Can 
Be 
Correct 
Glen B. Alleman, Copyright © 2012 14/34
Risk 
Management 
Demands 
Direct 
CommunicaIon 
Between 
All 
ParIes 
Glen B. Alleman, Copyright © 2012 15/58
Q5: 
How Do We Know We Are 
Making Progress to Plan? 
Glen B. Alleman, Copyright © 2012 16/34
What are the Primary 
Measures of Progress 
17/34 
to Plan for this 
Project? 
Are We Done? 
When will we be Done? 
What will it cost to be Done? 
! What does Done look like for the 
customer? 
! How can we recognize Done when 
it arrives? 
! How can we be sure we can get 
to from here to Done? 
! What are the impediments to 
getting to done? 
Glen B. Alleman, Copyright © 2012
A Technical Performance Measure 
… 
! Tell us how well a system is achieving 
the planned performance requirements at 
the planned time, for the planned cost. 
! Use actual or predicted values from: 
– Engineering measurements 
– Tests 
– Experiments 
– Prototypes 
! For Example: 
– Response time 
– Range 
– Power 
– Weight 
Glen B. Alleman, Copyright © 2012 18/58
Q5. How Do We Know If We Are Making 
The Progress We Planned To Make? 
The only measure of progress is the Physical Percent 
Complete for the A planned deliverables 
Physical Percent Complete means tangible evidence of 
the outcomes that were planned – measured at the time 
they were planned to be delivered. 
B 
This is the basis for full Earned Value Management with 
physical percent complete. 
This is also a natural a fit with the agile approaches to 
software development. 
C 
All successful methods measure the evidentiary 
outcomes in units meaningful to the stakeholders. 
These units are usually “money” and “time.” 
D 
19/34
Trade Offs Between 
Cost, Schedule, 
and 
Technical 
Performance is a 
Ponzi Scheme 
When we’re on baseline, 
the algebraic relationship 
between C,S,P, means 
when there is a change 
everyone looses 
Charles Ponzi, 
Born March 3, 1882, Italy. 
Died Jan 18, 1949, Brazil. 
Served 5 years federal prison, 
9 year state prison, 
deported to Italy. 
Glen B. Alleman, Copyright © 2012 20/34
Glen B. Alleman, Copyright © 2012 21/58
Physical Percent Complete 
! Measuring physical percent complete is 
at the core of every project 
management method. 
! It answers the question of what “done” 
look like in units of measure meaningful 
to the decision makers. 
! It answers questions like: 
– What does done look like for today, this 
week? 
– What does done look like for entry/exit into 
the technical review? 
– What does done look like for quality control? 
– What does done look like for the customer? 
No stretching the truth 
allowed once we 
measure Technical 
Performance with 
tangible evidence. 
Glen B. Alleman, Copyright © 2012 22/34
The 5 Project Principles – Again … 
We have a defined Mission, Vision, Capabilities, 
and Requirements; 1 by which to create 
the Plan for fulfilling these capabilities and 
requirements and the Schedule for producing the 
needed outcomes to meet this Plan; and have 
2 
allocated enough Time, Money, and Resources to 
3 increase the probability of our project’s success; by 
knowing what Risks are in front of us and the 
4 retirement and mitigation plan; and we can 
measure progress as Physical Percent Complete for 
each planned Deliverable in our Plan “on or before” 
its planned time and “at or below” the planned cost. 
5 
Glen B. Alleman, Copyright © 2012 23/34
Glen B. Alleman, Copyright © 2012 24/34
Did We Learn Anything Useful? 
No matter our tolerance for risk, or the 
methods we use – the 5 immutable 
principles are always in place. 
Glen B. Alleman, Copyright © 2012 25/34
Glen B. Alleman 
Niwot Ridge Consulting 
4347 Pebble Beach Drive 
Niwot, Colorado 80503 
303.241.9633 
glen.alleman@niwotridge.com 
Performance-Based Project Management® 
Integrated Master Plan 
Integrated Master Schedule 
Earned Value Management Systems 
Risk Management 
Proposal Support Services 
Glen B. Alleman, Copyright © 2012 26/34

More Related Content

PPTX
Kolesterol
DOCX
Manual de antigerencia, la teoria l
PDF
Curso-Taller en Materia de Agua_PROFEPA.pdf
PPTX
Perencanaan proyek
PPTX
Materi Sosialisasi PIRT.pptx
DOC
Cover makalah
PDF
PMO Frameworks
PDF
06 Kepemimpinan Tranformasional (Dr. Dewi Wahyuni, MP & Dr. Suharyanto, M.Si)
Kolesterol
Manual de antigerencia, la teoria l
Curso-Taller en Materia de Agua_PROFEPA.pdf
Perencanaan proyek
Materi Sosialisasi PIRT.pptx
Cover makalah
PMO Frameworks
06 Kepemimpinan Tranformasional (Dr. Dewi Wahyuni, MP & Dr. Suharyanto, M.Si)

Viewers also liked (20)

PDF
Forecasting cost and schedule performance
PDF
Agile in the government
PDF
Principles and Practices of Performance-Based Project Management®
PDF
Managing in the presence of uncertainty
PDF
Root cause analysis master plan
PDF
Nine Best Practices
PDF
Notes on balanced scorecard
PDF
21.5 Estimating Agile Softare Development
PPTX
Capabilities Based Planning
PDF
Evm+agile estimating
PDF
12.0 risk management agile+evm (v10.2)
PDF
Pseudo–science and the art of software methods
PDF
Capabilities based planning (v2)
PDF
Principles of program governance
PDF
Paradigm of agile project management
PDF
Project maturity flow is the incremental delivery of business value
PPT
Fundamentals of Project Management
PPTX
Fundamentals of project management sf discussion v1.0
PDF
Digital Project Management Fundamentals 01
PDF
Business Strategy & Alignment to Project Management
Forecasting cost and schedule performance
Agile in the government
Principles and Practices of Performance-Based Project Management®
Managing in the presence of uncertainty
Root cause analysis master plan
Nine Best Practices
Notes on balanced scorecard
21.5 Estimating Agile Softare Development
Capabilities Based Planning
Evm+agile estimating
12.0 risk management agile+evm (v10.2)
Pseudo–science and the art of software methods
Capabilities based planning (v2)
Principles of program governance
Paradigm of agile project management
Project maturity flow is the incremental delivery of business value
Fundamentals of Project Management
Fundamentals of project management sf discussion v1.0
Digital Project Management Fundamentals 01
Business Strategy & Alignment to Project Management
Ad

Similar to Immutable principles of project management (utah pmi)(v1)(no exercise) (20)

PPTX
Getting to Done and Some Issues Along the Way
PPTX
Immutable principles of project management
PDF
The 5 Immutable principles of project management
PDF
Five immutable principles of project success
PDF
5 immutable principles of project success (Denver PMI)
PDF
Heliotropic Abundance
PPTX
Immutable Principles of Project Management (Toronto PMI)
PDF
PDF
5 immutable principles webinar
PDF
Immutable Principles Of Project Management (V7 Final Cmu)
PDF
The Five Immutable Principles of Project DSuccess
PDF
A Guide for Capital Project Mamnagers
PPTX
Showing how to Increase the Probability of Project Success by applying the ...
PPTX
Five Immutable Principles of Project of Digital Transformation Success
PDF
5 immutable principles of project success (v2)(notes)
PPTX
Mash Up fpr Two Emerging Ideas
PDF
5 immutable principles of project success (v3)(notes)
PDF
You don’t need agile to avoid the seven deadly sins of pm
PDF
Project Success: The Basis of the Five Immutable Principles
PDF
Nine best practices of project management
Getting to Done and Some Issues Along the Way
Immutable principles of project management
The 5 Immutable principles of project management
Five immutable principles of project success
5 immutable principles of project success (Denver PMI)
Heliotropic Abundance
Immutable Principles of Project Management (Toronto PMI)
5 immutable principles webinar
Immutable Principles Of Project Management (V7 Final Cmu)
The Five Immutable Principles of Project DSuccess
A Guide for Capital Project Mamnagers
Showing how to Increase the Probability of Project Success by applying the ...
Five Immutable Principles of Project of Digital Transformation Success
5 immutable principles of project success (v2)(notes)
Mash Up fpr Two Emerging Ideas
5 immutable principles of project success (v3)(notes)
You don’t need agile to avoid the seven deadly sins of pm
Project Success: The Basis of the Five Immutable Principles
Nine best practices of project management
Ad

More from Glen Alleman (20)

PDF
Managing risk with deliverables planning
PDF
A Gentle Introduction to the IMP/IMS
PDF
Increasing the Probability of Project Success
PDF
Process Flow and Narrative for Agile+PPM
PDF
Practices of risk management
PDF
Principles of Risk Management
PDF
Deliverables Based Planning, PMBOK® and 5 Immutable Principles of Project Suc...
PDF
From Principles to Strategies for Systems Engineering
PDF
NAVAIR Integrated Master Schedule Guide guide
PDF
Building a Credible Performance Measurement Baseline
PDF
Integrated master plan methodology (v2)
PDF
IMP / IMS Step by Step
PDF
DHS - Using functions points to estimate agile development programs (v2)
PDF
Making the impossible possible
PDF
Capabilities based planning
PDF
Process Flow and Narrative for Agile
PDF
Building the Performance Measurement Baseline
PPTX
Program Management Office Lean Software Development and Six Sigma
PDF
Policy and Procedure Rollout
PDF
Integrated Master Plan Development
Managing risk with deliverables planning
A Gentle Introduction to the IMP/IMS
Increasing the Probability of Project Success
Process Flow and Narrative for Agile+PPM
Practices of risk management
Principles of Risk Management
Deliverables Based Planning, PMBOK® and 5 Immutable Principles of Project Suc...
From Principles to Strategies for Systems Engineering
NAVAIR Integrated Master Schedule Guide guide
Building a Credible Performance Measurement Baseline
Integrated master plan methodology (v2)
IMP / IMS Step by Step
DHS - Using functions points to estimate agile development programs (v2)
Making the impossible possible
Capabilities based planning
Process Flow and Narrative for Agile
Building the Performance Measurement Baseline
Program Management Office Lean Software Development and Six Sigma
Policy and Procedure Rollout
Integrated Master Plan Development

Recently uploaded (20)

PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PDF
NewMind AI Monthly Chronicles - July 2025
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
PPTX
Big Data Technologies - Introduction.pptx
PDF
Spectral efficient network and resource selection model in 5G networks
PDF
Approach and Philosophy of On baking technology
PPTX
Understanding_Digital_Forensics_Presentation.pptx
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PDF
GamePlan Trading System Review: Professional Trader's Honest Take
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PDF
Empathic Computing: Creating Shared Understanding
PPTX
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
PDF
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
PDF
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
PDF
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
NewMind AI Monthly Chronicles - July 2025
Advanced methodologies resolving dimensionality complications for autism neur...
20250228 LYD VKU AI Blended-Learning.pptx
Big Data Technologies - Introduction.pptx
Spectral efficient network and resource selection model in 5G networks
Approach and Philosophy of On baking technology
Understanding_Digital_Forensics_Presentation.pptx
Mobile App Security Testing_ A Comprehensive Guide.pdf
GamePlan Trading System Review: Professional Trader's Honest Take
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
Empathic Computing: Creating Shared Understanding
PA Analog/Digital System: The Backbone of Modern Surveillance and Communication
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf

Immutable principles of project management (utah pmi)(v1)(no exercise)

  • 1. Five Immutable Principles of Project Success Glen B. Alleman glen.alleman@niwotridge.com +1 303 241 9633
  • 2. Today We Will Learn … There many – maybe too many – methods for successfully managing a project. LO1 LO2 LO3 But, no matter how many, each must possess 5 Immutable Principles to be successful , no matter the domain, context. We need to assure our work is guided by these 5 Project Management principles to increase the probability of success We need to remember, Yogi’s advice … In theory, there is no difference between theory and practice. In practice there is. 2/58
  • 3. Why Are Deliverables the Best Measure of Progress? Because the customer contracted for a “Capability” We need the capability to fly to LOE, with 4 on board, dock at ISS, stay for 90 days, and return safely
  • 4. The 5 Immutable Principles of Success Project success does not start with the PMBOK® contents. These are just a guide – as the name says PMBOK® shows us the components of a method, but does not show us how to put these components together.
  • 5. Immutable Principles Project Success 1. Where Are We Going? 2. How Do We Get There? 3. Do We Have Enough Time, Resources, And Money To Get There? 4. What Impediments Will We Encounter Along The Way? 5. How Do We Know We Are Making Progress? Glen B. Alleman, Copyright © 2012 5/34
  • 6. Q1. Where Are We Going? Eliciting Requirements Is Highly Domain Dependent “Design and integrate 18 major weapon systems and platforms simultaneously within strict size and weight limitations, while synchronizing the development, demonstration, and production of as many as 157 complementary systems with the Future Combat System content and schedule.” (This is an actual requirement) “Implement the 8 stories for our new warehouse inventory tracking system using the existing web site platform as a starting point.” Glen B. Alleman, Copyright © 2012 6/34
  • 7. Three steps to success ! Plan – a strategy for the successful compleIon of the project. ! Schedule – the steps needed to fulfill the Plan. ! ExecuBon – the physical performance of the steps needed to deliver the results defined in the Plan. Glen B. Alleman, Copyright © 2012 7/34
  • 8. Scheduling Always comes aOer Planning ! What are the individual, dependent and, sequenIal steps needed to deliver these capabiliIes? ! The schedule has duraIons, dependencies, Iming, dates, resources and other things related with the Plan. ! The idea that these steps “emerge” is fanciful in many Glen B. Alleman, Copyright © 2012 situaIons. 8/34
  • 9. Q2. How Do We Get There? Some problems respond to lightweight approaches, like Scrum, DSDM, Crystal, and XP as product development methods. Others require more complex approaches, like a System of Systems (SoS) spiral development processes. In all cases a disciplined approach increases the probability of success – no matter the complexity of the problem or the solution This approach works well when we don’t know what “done” looks like with enough clarity So Does This! Glen B. Alleman, Copyright © 2012 9/34
  • 10. Q3: Do We Have Everything We Need? Glen B. Alleman, Copyright © 2012 10/34
  • 11. Q3. Do We Have Enough Time, Money, And Resources To Get There? In the resource management business, optimism is always the source of trouble A Common Problem A Simple Solution We have undue optimism Use documented procedures – no matter the method – for estimating and planning using historical data. We attempt to avoid risk and uncertainty Understand and prioritize risks for each critical component empowers management and staff. Use this knowledge to control your optimism. We rely too much on intuitive judgment Simple statistical models are more often correct than the human judgment. Have the number to back up your intuition. The Rational Planning of (Software) Projects, Mark C. Paulk, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213–3890 Glen B. Alleman, Copyright © 2012 11/58
  • 12. Q4: What Are the Impediments to Getting There? Glen B. Alleman, Copyright © 2012 12/34
  • 13. Q4. Five Fundamental Principles of Risk Management 1. Hope is not a strategy 2. No single point esImate of cost or schedule can be correct 3. Cost, Schedule, and Technical Performance are inseparable 4. Risk management requires adherence to a well defined process 5. CommunicaIon is the Number One success factor Glen B. Alleman, Copyright © 2012 13/34
  • 14. No Point EsBmate, By Itself, Can Be Correct Glen B. Alleman, Copyright © 2012 14/34
  • 15. Risk Management Demands Direct CommunicaIon Between All ParIes Glen B. Alleman, Copyright © 2012 15/58
  • 16. Q5: How Do We Know We Are Making Progress to Plan? Glen B. Alleman, Copyright © 2012 16/34
  • 17. What are the Primary Measures of Progress 17/34 to Plan for this Project? Are We Done? When will we be Done? What will it cost to be Done? ! What does Done look like for the customer? ! How can we recognize Done when it arrives? ! How can we be sure we can get to from here to Done? ! What are the impediments to getting to done? Glen B. Alleman, Copyright © 2012
  • 18. A Technical Performance Measure … ! Tell us how well a system is achieving the planned performance requirements at the planned time, for the planned cost. ! Use actual or predicted values from: – Engineering measurements – Tests – Experiments – Prototypes ! For Example: – Response time – Range – Power – Weight Glen B. Alleman, Copyright © 2012 18/58
  • 19. Q5. How Do We Know If We Are Making The Progress We Planned To Make? The only measure of progress is the Physical Percent Complete for the A planned deliverables Physical Percent Complete means tangible evidence of the outcomes that were planned – measured at the time they were planned to be delivered. B This is the basis for full Earned Value Management with physical percent complete. This is also a natural a fit with the agile approaches to software development. C All successful methods measure the evidentiary outcomes in units meaningful to the stakeholders. These units are usually “money” and “time.” D 19/34
  • 20. Trade Offs Between Cost, Schedule, and Technical Performance is a Ponzi Scheme When we’re on baseline, the algebraic relationship between C,S,P, means when there is a change everyone looses Charles Ponzi, Born March 3, 1882, Italy. Died Jan 18, 1949, Brazil. Served 5 years federal prison, 9 year state prison, deported to Italy. Glen B. Alleman, Copyright © 2012 20/34
  • 21. Glen B. Alleman, Copyright © 2012 21/58
  • 22. Physical Percent Complete ! Measuring physical percent complete is at the core of every project management method. ! It answers the question of what “done” look like in units of measure meaningful to the decision makers. ! It answers questions like: – What does done look like for today, this week? – What does done look like for entry/exit into the technical review? – What does done look like for quality control? – What does done look like for the customer? No stretching the truth allowed once we measure Technical Performance with tangible evidence. Glen B. Alleman, Copyright © 2012 22/34
  • 23. The 5 Project Principles – Again … We have a defined Mission, Vision, Capabilities, and Requirements; 1 by which to create the Plan for fulfilling these capabilities and requirements and the Schedule for producing the needed outcomes to meet this Plan; and have 2 allocated enough Time, Money, and Resources to 3 increase the probability of our project’s success; by knowing what Risks are in front of us and the 4 retirement and mitigation plan; and we can measure progress as Physical Percent Complete for each planned Deliverable in our Plan “on or before” its planned time and “at or below” the planned cost. 5 Glen B. Alleman, Copyright © 2012 23/34
  • 24. Glen B. Alleman, Copyright © 2012 24/34
  • 25. Did We Learn Anything Useful? No matter our tolerance for risk, or the methods we use – the 5 immutable principles are always in place. Glen B. Alleman, Copyright © 2012 25/34
  • 26. Glen B. Alleman Niwot Ridge Consulting 4347 Pebble Beach Drive Niwot, Colorado 80503 303.241.9633 glen.alleman@niwotridge.com Performance-Based Project Management® Integrated Master Plan Integrated Master Schedule Earned Value Management Systems Risk Management Proposal Support Services Glen B. Alleman, Copyright © 2012 26/34