Webinar Recap: Project Performance Measurement – Part 1: Overview Of Project Performance Measurements

MPUG

Please find below a transcription of the audio portion of Fletcher Hearn’s session, Project Performance Measurement – Part 1: Overview Of Project Performance Measurements, being provided by MPUG for the convenience of our members. Fletcher Hearns: What can be measured?

Webinar Recap: Project Performance Measurement – Part 2: What to Measure and How to Report

MPUG

Please find below a transcription of the audio portion of Fletcher Hearn’s session, Project Performance Measurement – Part 2: What to Measure and How to Report, being provided by MPUG for the convenience of our members. This one covering, What to Measure and How to Report.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Project Management, Performance Measures, and Statistical Decision Making

Herding Cats

There is a current rash of suggestions on how to improve the performance of software projects. I work in the Software Intensive System of Systems domains in Aerospace, Defense, Enterprise IT (both commercial and government) applying Agile, Earned Value Management, Productive Statistical Estimating (both parametric and Monte Carlo), Risk Management, and Root Cause Analysis with a variety of capabilities. Figure 1 - Planned Estimates versus Actual Performance from [1].

How to Talk About Estimates

Herding Cats

What is an estimate? An estimate as a noun is an approximate calculation or judgment of the value, number, quantity, or extent of something. An estimate as a verb is to roughly calculate or judge the value, number, quantity, or extent of. But those estimates, nouns, and verbs themselves's have other attributes. Every month there is a Month End reports, both showing cumulative cost to date, cumulative schedule performance, and Physical Percent Complete.

4 Fallacious Reasons to Estimate and Why Those Are Fallacious

Herding Cats

There's a recent post titled Four Fallacious Reasons to Estimate. It lists the usual suspects for why those spending the money think they don't have to estimate how much they plan to spend when they'll be done producing the value they've been assigned to produce for that expenditure. And like many posts and tweets about estimating, it's made from this point of view, not the business point view, not from the point of view of those paying the developer.

A Compendium of Works to Increase the Probability of Project Success

Herding Cats

Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Software for Your Mind: Patterns and Anti-Patterns for Creating and Maintaining a Shared Vision. Nine Best Practices of Project Management , Software Program Managers Network (SPMN). Project Performance Management.

2008 45

What is an Estimate? What is Estimating?

Herding Cats

I work in a domain where estimates are made every single week. Estimate to Complete (ETC), Estimate at Completion (EAC), Estimated Completion Date (ECD) are the life blood of our software intensive system of systems programs. The management of SISoS is really no different than the management of any other enterprise class software system. In the #NoEstimates paradigm, the term estimate is redefined to be Forecast and relabeled as NOT Estimating.

Deconstructing the Hertz and Accenture Debacle

Herding Cats

A recent lawsuit by Hertz Rental Car against Accenture has turned into a rallying cry by Agilest and No Estimates advocates. Of course, No Root Cause analysis has been performed by these advocates, but it makes good click bait for their followers. This approach is guided by the processes for Root Cause Analysis on Software Intensive System of Systems project I've worked. Were they based on the established planning processes for complex Software Intensive System of Systems?

Project Versus Product in Agile Development

Herding Cats

This quote is typically the basis of proposing agile software development over traditional software development. But if the development work is a Project is a fixed period of performance, for a fixed (with margin) budget, and a fixed set of Capabilities, then the question is can agile be used to develop the software? FASB 86 is an example of how cost and revenue for internal software development are recorded on the balance sheet. .

2018 38

Biases in Project Management and How to Remove Them

Herding Cats

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What dos Done look like in units of measure meaningful to the decision makers? Software engineering economics is about making decisions related to software engineering in a business context.

Definition of Done

Herding Cats

The common definition of the Definition of Done in agile software development is (mostly from the Scrum Alliance and other official Scrum sites): A simple list of activities (coding, comments, unit testing, integration, release notes, design documents, etc.) These Measures have Little meaning to the Decision Makers. These are attributes to assure the system has the capability and capacity to perform. Do these Key Performance Parameters have a threshold or objective value?

2017 38

Cone of Uncertainty Bibliography

Herding Cats

I work in a domain where the CoU is baked into the Integrated Program Performance Management (IPPM) processes flowed down from the buyer, in this case, the Federal Government. The CoU paradigm defines the needed reduction in uncertainty is some performance metric. This can be the confidence in the estimate for any variable. It can be the needed performance of a measure - Effectiveness, Performance, Key Performance Parameter, or a Technical Performance Measures.

2017 32

Connecting "What" with "How" - and the Failure to Understand the Principles of Systems Engineering and Systems Management

Herding Cats

The original agile author's quote shows that systems engineering is missing from his development of software using Agile. In most of the software development, this notion is missing - hence the quote that What is divided from How. Progress and Value are measured with the same in Earned Value Management. In Earned Value Management paradigm, progress is always measured as physical percent complete. The Measures of effectiveness. Key Performance Parameters.

Cone of Uncertainty - Revisited

Herding Cats

We're writing two chapters in an upcoming Project Management Book, with a working title, The Gower Handbook of Project Performance for Agile, Waterfall and Everything in Between , edited by Mark Phillips. The Cone of Uncertainty,” Stephen Gryphon, Phillippe Kruchten, and Steve McConnell, Letters, IEEE Software , 23 (5) 2006, pp 8?10. Shrinking the Cone of Uncertainty with Continuous Assessment for Software Team Dynamics in Design and Development,” Pongtip Aroonvatanaporn,”Ph.D.

2012 28

INVEST, Scrum and Enterprise IT

Herding Cats

That would mine all the User Stories are standalone pieces of software. Besides the process, software, and User Experience modeling of the interdependent components, Risk Management and most critically Risk Propagation can be modeled with DSM. Actual software process flows contain loops. Enterprise Software process and data flows always contain loops. Cohesion is the measure of how well module fits together.

Decision Analysis - Ordinal and Cardinal Measures

Herding Cats

When we hear of the difficulties of making decisions in the presence of uncertainty, especially about software features and capabilities, there are straightforward ways to solve this problem. In our agile software development world, AHP is rarely found. AHP is based on the principle that all measurements are relative. Using this method, the performance, cost, time, and risks of alternatives can be articulated as ratios that can then be compared with one another.

2018 40

Misinterpretations of the Cone of Uncertainty

Herding Cats

The Cone of Uncertainty is a framing assumption used to model the needed reduction in some parameter of interest in domains ranging from software development to hurricane forecasting. The Cone of Uncertainty as a Technical Performance Measure. Active reduction requires we have a desired reduction goal, perform the work, and measure progress toward the rduction goal. Closed Loop Control, has a goal, an action, a measurement, and a corrective action.

2017 32

Principles, Processes, and Practices of Project Success

Herding Cats

What does Done look like in units of measure meaningful to the decision makers? What impediments will be encountered along the way to Done and what work must be performed to handle these impediments? What are the units of measures of progress to plan for each deliverable? Two Books in the Spectrum of Software Development. Estimating Processes in Support of Economic Analysis. Principles are timeless. Practices and Process are Fads.

2017 44

Biases in Project Management and How to Remove Them

Herding Cats

There is always lots of complaining about the biases introduced into managing projects and making the estimates needed to make project decisions. With these business principles of software development and projects in general, we can ask and answer five principles of project success. What dos Done look like in units of measure meaningful to the decision makers? Software engineering economics is about making decisions related to software engineering in a business context.

Five Immutable Principles of Project Success

Herding Cats

Without these measures, Done will usually mean . Without these measures, Done will usually mean we ran out of time and money. . The test of the hypothesis for projects are the Measures of Effectiveness, Measures of Performance, Key Performance Parameters, and techTechnicalformance Measures used to assess progress to plan for the project. Estimating how much is the starting point. Estimating is part of risk management. No Estimating?

2017 35

INVEST, Scrum and Enterprise IT

Herding Cats

That would mine all the User Stories are standalone pieces of software. Besides the process, software, and User Experience modeling of the interdependent components, Risk Management and most critically Risk Propagation can be modeled with DSM. Actual software process flows contain loops. Enterprise Software process and data flows always contain loops. Cohesion is the measure of how well module fits together.

Closed Loop Control and Granularity of the Estimating Process

Herding Cats

For software, this can be value produced (assuming we have a unit of measure for that value in the for of effectiveness, performance, key performance parameters, or technical performance measures ). For a software project, let’s start by answering a critical question – how long are you willing to wait before you find out you’re late ? For your Honeywell or Nest controller on the wall, that sample rate is measured in seconds.

Fallacy of the Day

Herding Cats

Project Controls are Management Actions, either preplanned to achieve the desired result, or taken as a corrective measure prompted by the monitoring process. Project controls are concerned with the metrics of the project – quantities, time, cost, and other resources and their measurable beneficial outcomes for the project. In the Project Controls paradigm, Value is a measurable attribute of the project controls process - a Closed Loop Control measure.

2017 34

Software Intensive System of Systems

Herding Cats

The domain I work in is categorized as Software Intensive System of Systems (SISoS). The development of the software and sometimes the development of the hardware is done in an agile manner, using one of several Agile development methods - SAFe, Scrum for example. The system can be a business system, a collection of hardware and software for defense or space, a weapons systems, a business management systems. Cost, Schedule, and these measures are tightly interconnected.

2001 30

Software Intensive System of Systems

Herding Cats

The domain I work in is categorized as Software Intensive System of Systems (SISoS). The development of the software and sometimes the development of the hardware is done in an agile manner, using one of several Agile development methods - SAFe, Scrum for example. The system can be a business system, a collection of hardware and software for defense or space, a weapons systems, a business management systems. Cost, Schedule, and these measures are tightly interconnected.

2001 28

What's Missing from the Agile Software Development Paradigm

Herding Cats

Agile software development is framed by a manifesto , a set of 12 principles, several methods. These are all focused on developing software, delivering that software to those paying the developers. The customer is accountable for knowing what Done Looks Like (in Unity of measure meaningful to their domain). Most customers have not been exposed to a paradigm that is the basis of everything we do in our Software Intensive System of Systems (SISoS) domain. [7].

Microeconomics and Risk Management in Decision Making for Software Development

Herding Cats

Microeconomics is applicable to the development is software systems. If we look at the discipline of software engineering, we see that the microeconomics branch of economics deals more with the types of decisions we need to make as software engineers or managers. Throughout the software life cycle, there are many decision situations involving limited resources in which software engineering economics techniques provide useful assistance.

2007 32

Is Macroeconomics and Social Science the Same as Software Development?

Herding Cats

There a popular notions in the agile development world that authors like Hayek and Taleb speak to how software development works. Let's look at the thesis of Hayek in light of software development and the decisions that must be made when spending other people's money in the presence of uncertainty. He was not a program manager of engineered to order software intensive system of systems. Macroeconomics is the dismal science - treat it as such when developing software.

2016 36

Systems Engineering and Software Intensive System of Systems

Herding Cats

I come to this systems domain from the Software Intensive System of Systems paradigm. When I hear about complex software systems and how difficult they are, and how undesirable they are, and all the other urban legends about complexity, complex, complicated and chaos, I get a smile. The Art of Systems Architecting 2nd Edition , Mark Maier and Eberhardt Rechtin - is a seminal work including software systems. Technical Performance Measures. Estimating Guidance.

Risk Management is How Adults Manage Projects

Herding Cats

Research shows that for projects, especially software projects Aleatory uncertainty is the predominant source of risk. All making things smaller dos is show that you're late, over budget, and what you're building (Technical Performance Measures) doesn't work faster. So here are some books, handbooks, and guides that sit on my shelf that are used pretty much all the time on the Software Intensive System of Systems we work on. Software Risk Management , Barry W.

2003 38

Managing in Presence of Uncertainty

Herding Cats

This is an immutable principle that impacts planning, execution, performance measures, decision making, risk, budgeting, and overall business and technical management of the project and the business funding the project no matter the domain, context, technology or any methods. Do we have measures of Effectiveness, Performance, all the .ilities. Is each of these measures being met for the planned cost at the planned time? . Why did the estimates NOT get better?

Start with Principles, Not Personal Anecdotes

Herding Cats

I've seen estimates abused by bad managers, so let's NOT estimate and that will fix the behavior of Bad Managers." While the human behaviors are real and observable, conjecturing that decisions can be made in the presence of uncertainty without estimating the outcome of those decisions, there is no principle to support that conjecture. The first thing to do is NOT fall for the fallacy that NOT Estimating will fix the behavior of the bad manager.

2018 39

3 Questions That Must Be Asked at Every Project Management Meeting

Herding Cats

In the ConOps are measures of Effectiveness for the components of the project that implement the Capabilities . For software projects, Scrum can be used. The only answer to that is a measure of Physical Percent Complete (P%C). P%C starts with defining the Measures of Performance and Technical Performance Measures for each deliverable as a function of time. These measures are supported by Quantifiable Backup Data.

2018 35

Cone of Uncertainty - Part Cinq

Herding Cats

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates of cost, schedule, technical performance on the left side of the cone have a lower probability of being precise and accurate than estimates on the right side of the cone. Software Eng.,

2017 33

Agile Finance: How Do You Make a Business Case for Transformation?

Leading Agile

You will need to outline the estimated costs to be incurred as part of that transformation as well as the estimated annual benefits and savings expected to be realized from your transformation effort. .

Project Management Process: The Basics

Clarizen

Monitoring & Controlling : processes required to track, assess, and regulate project performance and progress, as well as identify and initiate changes as necessary. . Performance measurement baseline. Work performance data. Team performance assessments.

2021 101

Cone of Uncertainty - Part Cinq (Updated)

Herding Cats

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates of cost, schedule, technical performance on the left side of the cone have a lower probability of being precise and accurate than estimates on the right side of the cone. Software Eng.,

2017 30

Why Johnny Can't Do The Math

Herding Cats

In a previous post, Why Johnny Can't Estimate , mentioned some resources for estimating, the principles of business and technical management that demand estimates be made to make decisions, and background on the sources of uncertainty, that create risk, that require estimating to increase the probability of project success. One of the #Noestimates advocates has now discovered a phrase: Estimates are non-ergodic. Software projects are non-ergodic.

Cone of Uncertainty - Part Trois

Herding Cats

Barry Boehm's work in “Software Engineering Economics”. The Cone is a project management framework describing the uncertainty aspects of estimates (cost and schedule) and other project attributes (cost, schedule, and technical performance parameters). Estimates of cost, schedule, technical performance on the left side of the cone have a lower probability of being precise and accurate than estimates on the right side of the cone. Software Eng.,

2017 28

6 Tips for Better Schedule Management

ProjectManager.com

Related: Project Scheduling Software. Determining these right off the bat and including them in your project schedule will help minimize risk and ensure that each task can be performed effectively with minimal roadblocks and need for management down the road.

2019 322