Sign up to save your podcasts
Or
Share Episode 4 - Earned Value vs Agile Metrics, Can They Coexist?
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Episode 4 - Earned Value vs Agile Metrics, Can They Coexist?
Today we’re diving into a topic that often sparks debate in project management circles, especially in organisations that are transitioning from traditional delivery models to agile ways of working.
The episode is titled: “Earned Value vs Agile Metrics — Can They Coexist?”
If you’ve spent time in highly regulated industries—defence, aerospace, nuclear, major infrastructure—you’ve almost certainly encountered Earned Value Management, or EVM. It’s a structured, rigorous approach to understanding cost performance and schedule adherence. It gives executives confidence. It provides boards with clarity. It’s deeply embedded in contracts, governance frameworks, and assurance processes. And for many organisations, especially those dealing with safety-critical systems, it isn’t optional.
On the other hand, if you've worked with modern delivery teams—software engineers, agile coaches—then you’ll be familiar with agile metrics: velocity, cycle time, cumulative flow diagrams, throughput, lead time, team predictability, flow efficiency, and more. These metrics focus on value delivered, team behaviour, system flow, and adaptability. They’re less interested in “percent complete” and more interested in “how well are we learning, improving, and delivering in small increments?”
And here’s the tension:
Earned Value is rooted in the illusion of linearity. Agile is rooted in embracing change. Can these two worlds sit together without compromising one another?
This is a question that is becoming increasingly important as organisations adopt hybrid governance models. Many programmes today involve both hardware and software; both long-lead procurement and rapid-cycle development; both fixed obligations and iterative experimentation.
So, in today’s episode, we’ll unpack:
What EVM is really trying to measure versus what agile metrics actually reveal.
Why conflicts arise between them, both technically and culturally.
The misconceptions teams have when trying to mix the two.
And most importantly: one detailed, practical example of a organisation that successfully aligned EVM with agile delivery without losing the integrity of either approach.
By the end of this episode, you should have a clearer sense of when these methods clash, when they complement one another, and how to build governance that is robust enough for executives, yet flexible enough for delivery teams.
View all episodes
By Isaac AlcaideToday we’re diving into a topic that often sparks debate in project management circles, especially in organisations that are transitioning from traditional delivery models to agile ways of working.
The episode is titled: “Earned Value vs Agile Metrics — Can They Coexist?”
If you’ve spent time in highly regulated industries—defence, aerospace, nuclear, major infrastructure—you’ve almost certainly encountered Earned Value Management, or EVM. It’s a structured, rigorous approach to understanding cost performance and schedule adherence. It gives executives confidence. It provides boards with clarity. It’s deeply embedded in contracts, governance frameworks, and assurance processes. And for many organisations, especially those dealing with safety-critical systems, it isn’t optional.
On the other hand, if you've worked with modern delivery teams—software engineers, agile coaches—then you’ll be familiar with agile metrics: velocity, cycle time, cumulative flow diagrams, throughput, lead time, team predictability, flow efficiency, and more. These metrics focus on value delivered, team behaviour, system flow, and adaptability. They’re less interested in “percent complete” and more interested in “how well are we learning, improving, and delivering in small increments?”
And here’s the tension:
Earned Value is rooted in the illusion of linearity. Agile is rooted in embracing change. Can these two worlds sit together without compromising one another?
This is a question that is becoming increasingly important as organisations adopt hybrid governance models. Many programmes today involve both hardware and software; both long-lead procurement and rapid-cycle development; both fixed obligations and iterative experimentation.
So, in today’s episode, we’ll unpack:
What EVM is really trying to measure versus what agile metrics actually reveal.
Why conflicts arise between them, both technically and culturally.
The misconceptions teams have when trying to mix the two.
And most importantly: one detailed, practical example of a organisation that successfully aligned EVM with agile delivery without losing the integrity of either approach.
By the end of this episode, you should have a clearer sense of when these methods clash, when they complement one another, and how to build governance that is robust enough for executives, yet flexible enough for delivery teams.