Three immutable variables, statistically coupled, for all projects. Each to level - Cost, Schedule, and Technical Performance are loosely coupled.
The drivers of each of these are listed as well.
All elements are in play and are probabilistic.
Managing in the presence of this uncertainty is the primary role of all project management.
Understanding the five immutable principles to project success will help project managers deliver on time, on budget when talking projects of any size, in any domain
Every tool, process, and practice has a dark side. Knowing these is a Critical Success Factor to the integration of EVM and Agile at the desired Maturity Level.
Both Earned Value Management and Agile have Dark Sides. Things that are not talked about in public.
But when they are Integrated, each provides a solution for the problems of the other.
Assess current and desired Maturity for Agile and EVM is the starting point for integrating these two processes.
ERP, PDM, CRM, and EDM system critical success factors (CSF) have significant impacts on the success or failure of the project.
What are these CSF’s and how can a project asses their compliance against them?
Performance based planning in a nut shell (V5)Glen Alleman
Step by step activtiies to increase the probability of success for all projects, no matter the project domain. These principles and practices can be found in all successful projects.
Understanding the five immutable principles to project success will help project managers deliver on time, on budget when talking projects of any size, in any domain
Every tool, process, and practice has a dark side. Knowing these is a Critical Success Factor to the integration of EVM and Agile at the desired Maturity Level.
Both Earned Value Management and Agile have Dark Sides. Things that are not talked about in public.
But when they are Integrated, each provides a solution for the problems of the other.
Assess current and desired Maturity for Agile and EVM is the starting point for integrating these two processes.
ERP, PDM, CRM, and EDM system critical success factors (CSF) have significant impacts on the success or failure of the project.
What are these CSF’s and how can a project asses their compliance against them?
Performance based planning in a nut shell (V5)Glen Alleman
Step by step activtiies to increase the probability of success for all projects, no matter the project domain. These principles and practices can be found in all successful projects.
Getting To Done - A Master Class WorkshopGlen Alleman
The Principles, Processes, Practices, and Tools to Increase the Probability of successfully completing Project's On-Tiem, On-Budget, and Needed Capabilities
Project driven organization require lifecycle management to successfully deliver value to those paying for the outcomes of the project effort. This involves processes and data for Executive processes, Enterprise Governance, Program Management Office activities, Applications that enable the delivery of value, and overarching processes and data.
The management of risk is a critical success factor of any project or program. This document is a collection of risk management categories that are used to ask the question “did you think about this risk and its impact on our probability of success?”
The Role of the Architect in ERP and PDM System DeploymentGlen Alleman
The architect’s role in the development of an ERP or PDM system is to maintain the integrity of the vision statement produced by the owners, users, and funders of the system.
Starting with an EIA–748–C compliant Earned Value Management System, integrating an Agile Software Development Lifecycle (Agile) is straightforward when there is a Bright Line between the Performance Measurement Baseline (PMB) and the Sprints and Tasks of the Agile Software Development Process.
Increasing the Probability of Project Success with Five Principles and PracticesGlen Alleman
There are many approaches to managing projects in every domain.
This seminar lays the foundations for increasing the probability of project success, no matter the domain, what technology, what approach to delivering the outcomes of the project.
The principles of this approach are immutable.
The practices for implementing the principles are universally applicable.
Each chart in this presentation, contains guidance that can be applied to your project, no matter the domain.
In our short hour here, we’re going to cover a lot of material.
The bibliography contains the supporting materials we can tailor to your individual project
Showing how to Increase the Probability of Project Success by applying the ...Glen Alleman
All projects ‒ Traditional and Agile ‒ operate in the presence of uncertainty that creates risk.
Five Immutable Principles and their supporting Processes and Practices can be used to increase the probability of success in the presence of these uncertainties.
Start with defining the deliverables to produce the capabilities needed for project success. Then what work is needed, the order of that work, and the defined outcomes of that work become obvious. Sequence that work, assign durations and resources and you've generated the plans and schedule for success
From WBS to Integrated Master ScheduleGlen Alleman
A step by step guide to increasing the Probability of Program success starting with the WBS, developing the Integrated Master Plan and Integrated Master Schedule, risk adjusting the IMS, and measuring progress to plan in units of measure meaningful to the decision makers.
Recent College of Performance Management Webinar on using Technical Performance to inform Earned Value Management. Six steps to building a credible Performance Measurement Baseline to connect the dots between all the elements of the program
Managing in the presence of uncertaintyGlen Alleman
Uncertainty is the source of risk. Uncertainty comes in two types, aleatory and epistemic. It is important to understand both and deal with both in distinct ways, in order to produce a credible risk handling strategy.
Getting To Done - A Master Class WorkshopGlen Alleman
The Principles, Processes, Practices, and Tools to Increase the Probability of successfully completing Project's On-Tiem, On-Budget, and Needed Capabilities
Project driven organization require lifecycle management to successfully deliver value to those paying for the outcomes of the project effort. This involves processes and data for Executive processes, Enterprise Governance, Program Management Office activities, Applications that enable the delivery of value, and overarching processes and data.
The management of risk is a critical success factor of any project or program. This document is a collection of risk management categories that are used to ask the question “did you think about this risk and its impact on our probability of success?”
The Role of the Architect in ERP and PDM System DeploymentGlen Alleman
The architect’s role in the development of an ERP or PDM system is to maintain the integrity of the vision statement produced by the owners, users, and funders of the system.
Starting with an EIA–748–C compliant Earned Value Management System, integrating an Agile Software Development Lifecycle (Agile) is straightforward when there is a Bright Line between the Performance Measurement Baseline (PMB) and the Sprints and Tasks of the Agile Software Development Process.
Increasing the Probability of Project Success with Five Principles and PracticesGlen Alleman
There are many approaches to managing projects in every domain.
This seminar lays the foundations for increasing the probability of project success, no matter the domain, what technology, what approach to delivering the outcomes of the project.
The principles of this approach are immutable.
The practices for implementing the principles are universally applicable.
Each chart in this presentation, contains guidance that can be applied to your project, no matter the domain.
In our short hour here, we’re going to cover a lot of material.
The bibliography contains the supporting materials we can tailor to your individual project
Showing how to Increase the Probability of Project Success by applying the ...Glen Alleman
All projects ‒ Traditional and Agile ‒ operate in the presence of uncertainty that creates risk.
Five Immutable Principles and their supporting Processes and Practices can be used to increase the probability of success in the presence of these uncertainties.
Start with defining the deliverables to produce the capabilities needed for project success. Then what work is needed, the order of that work, and the defined outcomes of that work become obvious. Sequence that work, assign durations and resources and you've generated the plans and schedule for success
From WBS to Integrated Master ScheduleGlen Alleman
A step by step guide to increasing the Probability of Program success starting with the WBS, developing the Integrated Master Plan and Integrated Master Schedule, risk adjusting the IMS, and measuring progress to plan in units of measure meaningful to the decision makers.
Recent College of Performance Management Webinar on using Technical Performance to inform Earned Value Management. Six steps to building a credible Performance Measurement Baseline to connect the dots between all the elements of the program
Managing in the presence of uncertaintyGlen Alleman
Uncertainty is the source of risk. Uncertainty comes in two types, aleatory and epistemic. It is important to understand both and deal with both in distinct ways, in order to produce a credible risk handling strategy.
ERP System Process and Data Flow in Gane & Sarson NotationGlen Alleman
Gane and Sarson is the predecessor of IDEF0.
In this notation, nouns and verbs are captured to describe the data and process flow of the system. Along with the constraints and mechanisms used to implement the system
The management of software development is fraught with risk: technical risk, market risk, requirements risk, and financial risk. This paper describes nine (9) key management principles for
guiding the development of a software project. These principles are not original. They are taken directly from the work of Norm Brown, the founder and executive Director of the Software Program Managers Network (SPMN).
Introduction to monte-carlo analysis for software development - Troy Magennis...Troy Magennis
Forecasting and managing software development project risks & uncertainty. Monte-carlo analysis is the tool of choice for managing risk in many fields where risk is an inherent part of doing business. This paper examines how to use monte-carlo techniques to understand and leverage risk in Software Development projects and teams.
Making decision in the presence of uncertainty requires estimating the impact of the outcome of those decisions. Here;s a collection of resources can can be used to guide that process
The integrated master plan and integrated master scheduleGlen Alleman
The Integrated Master Plan (IMP) and Integrated Master Schedule( (IMS) provide a strategy for the incremental delivery of program outcomes through increasing maturity assessments with Measures of Effectiveness, Measures of Performance, Technical Performance Measures, and Key Performance Parameters.
These assessment assure the needed capabilities of the project are met at each assessment point to confirm physical percent complete as planned in the Integrated Master Plan
Earned Value Management Meets Big DataGlen Alleman
The Earned Value Management System (EVMS) maintains period–by–period data in its underlying databases. The contents of the Earned Value repository can be considered BIG DATA, characterized by three attributes – 1) Volume: Large amounts of data; 2) Variety: data comes from different sources, including traditional data bases, documents, and complex records; 3) Velocity: the content is continually being updated by absorbing other data collections, through previously archived data, and through streamed data from external sources.
With this time series information in the repository, analysis of trends, cost and schedule forecasts, and confidence levels of these performance estimates can be calculated using statistical analysis techniques enabled by the Autoregressive Integrated Moving Average (ARIMA) algorithm provided by the R programming system. ARIMA provides a statistically informed Estimate At Completion (EAC) and Estimate to Complete (ETC) to the program in ways not available using standard EVM calculations. Using ARIMA reveals underlying trends not available through standard EVM reporting calculations.
With ARIMA in place and additional data from risk, technical performance and the Work Breakdown Structure, Principal Component Analysis can be used to identify the drivers of unanticipated EAC.
Forecasting cost and schedule performanceGlen Alleman
For credible decisions to be made, we need confidence intervals on all the numbers we use to make decisions.
These confidence intervals come from the underlying statistics and the related probabilities.
Statistical forecasting, using time series analysis of past performance, is mandatory for any credible discussion of project performance in the future.
Information Technology Risk ManagementGlen Alleman
The concept of managing the development or deployment of an Information Technology (IT) system using deterministic, linear, and causal analysis contains several pitfalls. As IT systems grow in complexity, the interaction between their components becomes non–linear and indeterminate, creating many opportunities for failure.
Performance-Based Project Management® id s deliverables based approach to project success. Deliverables start with the needed capabilities that the project produces to meet the mission objectives or fulfill a business case.
These deliverables fulfill the requirements, assessed through Measures of Effectiveness and Measures of Performance
EAI-748-C asks us to objectively assess accomplishments at the work performance level. As well §3.8 of 748-C tells us Earned Value is a direct measurement of the quantity of work accomplished. The quality and technical content of work is controlled by other processes. To provide visibility to integrated cost, schedule, and technical performance, we need more than CPI and SPI. We need measures of increasing technical performance.
Using Earned Value Management Concepts to Improve Commercial Project PerformanceLewisFowlerLLC
Lewis Fowler Principal Consultant Scott Brunton presented this deck at the 2015 Houston PMI Conference & Expo. Scott explores the historical roots of EVM and offers practical advice for implementing EVM practices to maximize the business value of projects.
Chapter 0 of Performance Based Project Management (sm)Glen Alleman
Defining the needed capabilities is the critical success factor proejct success. The capabilities state what Done looks like in units of measure meaningful to the decision makers.
Performance-Based Management
integrates Principles, Practices, and Processes
– to assure actionable information is provided to the decision makers that can increase the Probability Of Program Success.
Successful projects deliver capabilities:
§ Not work efforts,
§ Not cost expenditures,
§ Not documentation, test results, or the processes.
§ These all needed, but they’re not the deliverables.
§ For success projects must deliver tangible beneficial outcomes, assessed in units of measure meaningful to the decision makers.
This slide deck is an extract from the Book of the same name https://www.amazon.com/Performance-Based-Project-Management-Increasing-Probability/dp/0814433308
Earned Value Management involves more that just cost and schedule. Six Business Systems, including EVM, are the basis of credible program performance management.
Here's a suggestion of how to "connect the dots."
Successful execution of Aerospace, Defense, and Federal
Government programs requires management discipline to
identify what “Done” looks like, provide measures of
progress toward “Done,” identifies risks and impediments to
reaching “Done,” and assures timely corrective action to maintain the planned progress toward “Done.”
Planning projects usually starts with tasks and milestones. The planner gathers this information from the participants – customers, engineers, subject matter experts. This information is usually arranged in the form of activities and milestones. PMBOK defines “project time management” in this manner. The activities are then sequenced according to the projects needs and mandatory dependencies.
Increasing the Probability of Project SuccessGlen Alleman
Risk Management is essential for development and production programs. Information about key cost, performance and schedule attributes are often uncertain or unknown until late in the program.
Risk issues that can be identified early in the program, which may potentially impact the program, termed Known Unknowns, can be alleviated with good risk management. -- Effective Risk Management 2nd Edition, Page 1, Edmund Conrow, American Institute of Aeronautics and Astronautics, 2003
Cost and schedule growth for complex projects is created when unrealistic technical performance expectations, unrealistic cost and schedule estimates, inadequate risk assessments, unanticipated technical issues, and poorly performed and ineffective risk management, contribute to project technical and programmatic shortfalls
From Principles to Strategies for Systems EngineeringGlen Alleman
From Principles to Strategies How to apply Principles, Practices, and Processes of Systems Engineering to solve complex technical, operational,
and organizational problems
Building a Credible Performance Measurement BaselineGlen Alleman
Establishing a credible Performance Measurement Baseline, with a risk adjusted Integrated Master Plan and Integrated Master Schedule, starts with the WBS and connects Technical Measures of progress to Earned Value
Capabilities‒Based Planning the capabilities needed to accomplish a mission or fulfill a business strategy
Only when capabilities are defined can we start with requirements elicitation
Starting with the development of a Rough Order of Magnitude (ROM) estimate of work and duration, creating the Product Roadmap and Release Plan, the Product and Sprint Backlogs, executing and statusing the Sprint, and informing the Earned Value Management Systems, using Physical Percent Complete of progress to plan.
Program Management Office Lean Software Development and Six SigmaGlen Alleman
Successfully combining a PMO, Agile, and Lean / 6 starts with understanding what benefit each paradigm brings to the table. Architecting a solution for the enterprise requires assembling a “Systems” with processes, people, and principles – all sharing the goal of business improvement.
This resource document describes the Program Governance Road map for product development, deployment, and sustainment of products and services in compliance with CMS guidance, ITIL IT management, CMMI best practices, and other guidance to assure high quality software is deployed for sustained operational success in mission critical domains.
Seven Habits of a Highly Effective agile project managerGlen Alleman
Recent neurological studies indicate that the role of emotion in human cognition is essential; emotions are not a luxury. Instead, emotions play a critical role in rational decision–making, in perception, in human interaction, and in human intelligence. Habits are the intersection of knowledge, skill, and desire.
Measures of Effectiveness, Measures of Performance, Technical Performance Measures
1. Cost
Schedule
Delivered
Capabili4es
Key
Performance
Parameters
Irreducible
and
Reducible
Uncertainty
Efficacy
of
Funds
Labor
Costs
Material
Costs
Overhead
and
Indirects
Technical
Performance
Measures
Measures
of
Performance
Measures
of
EffecBveness
Capacity
for
Work
Efficacy
of
Outcomes
Project
Success
starts
with
idenBfying
needed
capabiliBes
their
Measures
of
EffecBveness,
Measures
of
Performance,
and
Key
Performance
Parameters.
Using
these
measures,
risk
adjusted
esBmates
of
cost,
schedule,
and
probability
of
achieving
these
targets
is
the
basis
of
informaBon
needed
to
provide
acBonable
informaBon
used
to
make
decisions
to
Keep
the
Program
GREEN