What do you think?
Rate this book
Actionable Agile Metrics #1
Actionable Agile Metrics For Predictability: An Introduction
“When will it be done?”
That is probably the first question your customers ask you once you start working on something for them. Think about how many times you have been asked that question. How many times have you ever actually been right?
We can debate all we want whether this is a fair question to ask given the tremendous amount of uncertainty in knowledge work, but the truth of the matter is that our customers are going to inquire about completion time whether we like it or not. Which means we need to come up with an accurate way to answer them. The problem is that the forecasting tools that we currently utilize have made us ill-equipped to provide accurate answers to reasonable customer questions.
Until now.
(You can also find out more at https://www.actionableagile.com)
That is probably the first question your customers ask you once you start working on something for them. Think about how many times you have been asked that question. How many times have you ever actually been right?
We can debate all we want whether this is a fair question to ask given the tremendous amount of uncertainty in knowledge work, but the truth of the matter is that our customers are going to inquire about completion time whether we like it or not. Which means we need to come up with an accurate way to answer them. The problem is that the forecasting tools that we currently utilize have made us ill-equipped to provide accurate answers to reasonable customer questions.
Until now.
(You can also find out more at https://www.actionableagile.com)
315 pages, Kindle Edition
First published March 4, 2015
101 people are currently reading
768 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 30 of 33 reviews
March 24, 2019
I think this book is likely a lot more accessible than Reinertsons "Principles of Product Development Flow" for many people. And it really hammers the effects of too much work in progress into your head. I also appreciate the less is more approach here, using just 3 basic metrics (Cycle-time, Throughput, WIP) and two diagram types (Cumulative Flow Diagram and the Cycle-time Scatterplot) for analysis and communication.
So why only four stars?
I've worked the last 1,5 years in a close enough setup using Kanban, reducing WIP where possible and using historic data percentile histograms to get a grip on forecasting. I had hoped that this book would deliver more on the latter topic, but unfortunately it was just a very brief chapter and a pointer to another book.
The quality of the diagrams in the print version of this book is also really lacking. Very often it was very hard to see visually what the author was talking about, since for example you couldn't make out the percentile lines in the diagram.
Last but not least, I already had a good enough understanding of flow before reading this book. The result being that the core insights in this book probably weren't so earth shattering for me. But that's hardly something that you can charge the book for. The general ideas are valid and I've seen real life results following this ideas. So if you haven't read anything on flow yet, this is the one you could start with.
So why only four stars?
I've worked the last 1,5 years in a close enough setup using Kanban, reducing WIP where possible and using historic data percentile histograms to get a grip on forecasting. I had hoped that this book would deliver more on the latter topic, but unfortunately it was just a very brief chapter and a pointer to another book.
The quality of the diagrams in the print version of this book is also really lacking. Very often it was very hard to see visually what the author was talking about, since for example you couldn't make out the percentile lines in the diagram.
Last but not least, I already had a good enough understanding of flow before reading this book. The result being that the core insights in this book probably weren't so earth shattering for me. But that's hardly something that you can charge the book for. The general ideas are valid and I've seen real life results following this ideas. So if you haven't read anything on flow yet, this is the one you could start with.
October 22, 2017
This is the best Kanban book in the last years. A must read for those who wants to have a clear understanding how to use effective metrics
December 6, 2015
This is THE best book about metrics I've read so far. Forget velocity and burn-downs: this book explains what you really need for predictability.
It goes through CFDs, cycle time, WIP, throughput - and explains in great details how to use them, all the traps to avoid, and all the value you can get from them!
The chapters on Little's Law are amazing: after hearing it mentioned so much in Kanban it's great to see its implications in action.
The author has a clear and direct style, even when he's going through advanced content he makes it very easy to understand.
I only wish he had gone into more details on forecasting and monte-carlo simulations, but I guess that might be coming in a future book.
It goes through CFDs, cycle time, WIP, throughput - and explains in great details how to use them, all the traps to avoid, and all the value you can get from them!
The chapters on Little's Law are amazing: after hearing it mentioned so much in Kanban it's great to see its implications in action.
The author has a clear and direct style, even when he's going through advanced content he makes it very easy to understand.
I only wish he had gone into more details on forecasting and monte-carlo simulations, but I guess that might be coming in a future book.
July 16, 2021
Excellent!
This book made me angry. Why the hell I have been doing story points estimation for 10 years? 10 years! Maybe it is not that bad - some people do it 20,30 years... The funny fact is that we all know that forecasts from story points estimations sucks because they are not about time but we still do this. Why? Because we don't know alternatives and stakeholders keep us asking; When it will be ready? So we have to give them the answer; We estimate, we add 20% extra (although according to the Parkinson law we will burn the 20% for sure). Stupid, isn't it? We estimate so hard, that we forget to look on the flow - what's eating the time? Where are the impediments? What is the root cause?
There was a time I was in love with Scrum. Recently the love is going away and this book just empowered this act. Scrum is not a solution. The "Simple but difficult to master" bullshit is just a justification for 15 page long (for some people even 15 pages is too much) scrum guide. You may say; do Scrum with kanban! ... I say: What about kanban without Scrum? Kanban with XP + Agile Development manifesto eagerly studied by Your team? Add DDD and You will see that Scrum is ... (placeholder for very bad word).
I really wish there could be more about Monte Carlo method. On the other hand maybe it is better that it is not in the book? In that form You have solid text which can help You with flow management, making it predictable. As Vacanti stated; when Your system is predictable, estimates based on CFD with data from scatter plots can work for a while. Once we are there, we can reach for Monte Carlo.
I forgive the ActionableAgile Analytics promo in the book - the stuff described in the book can be applied using spreadsheets what is also mentioned by the Author.
This is one of the best books I've read. 100% Recommendation!
This book made me angry. Why the hell I have been doing story points estimation for 10 years? 10 years! Maybe it is not that bad - some people do it 20,30 years... The funny fact is that we all know that forecasts from story points estimations sucks because they are not about time but we still do this. Why? Because we don't know alternatives and stakeholders keep us asking; When it will be ready? So we have to give them the answer; We estimate, we add 20% extra (although according to the Parkinson law we will burn the 20% for sure). Stupid, isn't it? We estimate so hard, that we forget to look on the flow - what's eating the time? Where are the impediments? What is the root cause?
There was a time I was in love with Scrum. Recently the love is going away and this book just empowered this act. Scrum is not a solution. The "Simple but difficult to master" bullshit is just a justification for 15 page long (for some people even 15 pages is too much) scrum guide. You may say; do Scrum with kanban! ... I say: What about kanban without Scrum? Kanban with XP + Agile Development manifesto eagerly studied by Your team? Add DDD and You will see that Scrum is ... (placeholder for very bad word).
I really wish there could be more about Monte Carlo method. On the other hand maybe it is better that it is not in the book? In that form You have solid text which can help You with flow management, making it predictable. As Vacanti stated; when Your system is predictable, estimates based on CFD with data from scatter plots can work for a while. Once we are there, we can reach for Monte Carlo.
I forgive the ActionableAgile Analytics promo in the book - the stuff described in the book can be applied using spreadsheets what is also mentioned by the Author.
This is one of the best books I've read. 100% Recommendation!
November 3, 2019
It might be worth five stars for beginners of Kanban, but for someone already familiar with Littles Law there is not much to get from the book besides a reminder on cumulative flow diagrams (CFDs) and scatter plot diagrams. The last should be well known by someone who is familiar with statistic process control (SPC). My personal view is that the book is highly overrated. Every time when it touches an interesting topic it stays pretty much on the surface. The example of Siemens Healthcare being no exception. There are claims that switching from Scrum to Kanban with SPC yielded high improvements and a lot of predictability but there is not much explanation on how this improvement came about.
There is nothing wrong with the content, except that it could be explained in less than 50 pages and that it stops where the interesting stuff begins (e. g. how to reduce variability in the process besides setting WIP limits). I found the book a big disappointment and rather shallow, others may have a different view.
By the way, SPC is quite the opposite of Agile - but this is a different story since nowadays Agile, Lean (Six Sigma) and Innovation all gets mixed up in the public media and discussion.
There is nothing wrong with the content, except that it could be explained in less than 50 pages and that it stops where the interesting stuff begins (e. g. how to reduce variability in the process besides setting WIP limits). I found the book a big disappointment and rather shallow, others may have a different view.
By the way, SPC is quite the opposite of Agile - but this is a different story since nowadays Agile, Lean (Six Sigma) and Innovation all gets mixed up in the public media and discussion.
January 18, 2020
A flow purist ranting on "scrum purists" 😁
I really like his approach. Yet, energy flows where attention goes. You can easily misuse this approach by running predictably fast into the wrong direction. But this book is not about delivering value or doing the right thing. It's about doing things right - and it's extremely good in delivery this.
I now how a new approach to try out and I'm looking forward to it.
One star removed, because it's very harshly "my way out the highway" and no focus on implementing this approach with other approaches like scrum and how they could benefit from it.
I really like his approach. Yet, energy flows where attention goes. You can easily misuse this approach by running predictably fast into the wrong direction. But this book is not about delivering value or doing the right thing. It's about doing things right - and it's extremely good in delivery this.
I now how a new approach to try out and I'm looking forward to it.
One star removed, because it's very harshly "my way out the highway" and no focus on implementing this approach with other approaches like scrum and how they could benefit from it.
April 8, 2020
Simple and an exhausting introduction. From time to time I had the feeling, why I'm reading this book, but then on some other times I had great insights why certain things are not working and how flow, WIP and Cycle Time can help to overcome those problems.
August 24, 2018
Great read. Currently trying it out with my team, plan to do it for the department and maybe even for my personal todo process (based on gtd).
I thought a new everything about CFD's but I didn't when it comes to modeling backlogs for example.
He also inspired me to try out scatterplots.
I thought a new everything about CFD's but I didn't when it comes to modeling backlogs for example.
He also inspired me to try out scatterplots.
December 1, 2023
One of the best books about Kanban method
May 7, 2017
Quick takeaway is this book is fairly well written but really really poorly illustrated. But if you get one book on "agile" metrics get this one.
Most of the figures appear to be low-resolution screen shots of tools Vacanti's company markets. Some are nearly unreadable.
That being said, I like the book's approach to understanding workflow through queuing theory (namely Little's Law) and visualizing workflow through cumulative flow diagrams (CFDs--note: I confused the aerodynamics team at work when I briefed my CFDs since they consider that the acronym for Computational Fluid Dynamics!).
This book made me think about our software development processes differently and combined with Kanban principles the tools presented are improving our ability visualize flow through our development, integration and test teams.
Most of the figures appear to be low-resolution screen shots of tools Vacanti's company markets. Some are nearly unreadable.
That being said, I like the book's approach to understanding workflow through queuing theory (namely Little's Law) and visualizing workflow through cumulative flow diagrams (CFDs--note: I confused the aerodynamics team at work when I briefed my CFDs since they consider that the acronym for Computational Fluid Dynamics!).
This book made me think about our software development processes differently and combined with Kanban principles the tools presented are improving our ability visualize flow through our development, integration and test teams.
February 27, 2017
Very good starting point about orienting metrics to promote predictable delivery and flow.
It helps me a lot to translate metrics and graphics into points for improving.
It helps me a lot to translate metrics and graphics into points for improving.
September 24, 2019
One of the few works that delivers on its promises. Actionable Agile Metrics is indeed Actionable.
Daniel Vacanti cuts thru the B$ and presents Kanban and its misconceptions quite clearly. It is also of importance how he debunks the many myths of Little's Law in knowledge work.
The message of the book is more or less:
1. Strive to stabilize your process so that Little's Law can be applied. By limiting WIP, matching departures with arrivals and ensuring conservation of Flow.
2. Gather Flow Metrics (WIP, Cycle Time and Throughput) to monitor and further fine tune your process. These are the levers that will help with continuous improvement.
And the corollary is with LESS variability you gain MORE predictability in your process. And the Flow Metrics are enablers for that.
I really enjoyed reading it, it is written with great sense of humor, straight forward language and quite accessible. It seemed more accessible than Reinertsen's works to me.
I read this booking after coming from Kanban in Action and I'm glad I did. Next step is The Principles of Product Development Flow
Daniel Vacanti cuts thru the B$ and presents Kanban and its misconceptions quite clearly. It is also of importance how he debunks the many myths of Little's Law in knowledge work.
The message of the book is more or less:
1. Strive to stabilize your process so that Little's Law can be applied. By limiting WIP, matching departures with arrivals and ensuring conservation of Flow.
2. Gather Flow Metrics (WIP, Cycle Time and Throughput) to monitor and further fine tune your process. These are the levers that will help with continuous improvement.
And the corollary is with LESS variability you gain MORE predictability in your process. And the Flow Metrics are enablers for that.
I really enjoyed reading it, it is written with great sense of humor, straight forward language and quite accessible. It seemed more accessible than Reinertsen's works to me.
I read this booking after coming from Kanban in Action and I'm glad I did. Next step is The Principles of Product Development Flow
July 11, 2019
Read this cover to cover inside 24 hours
A series of major eureka moments. (Stick with it, the author’s style warms up). I’ve read a lot about CFDs, but this clears up a lot of misconceptions, as well as introducing scatter plots and histogram views to better understand flow metrics of cycle time, wip and throughout. It also does a great job of explaining the assumptions underlying Little’s Law, and how setting your policies to comply with those will make your process more predictable. Key finding: you CAN answer “when will it be ready?” if you have such a process - but don’t use CFDs for forecasting - try Monte Carlo analysis. Great homework before taking the Scrum.org PSK certification
A series of major eureka moments. (Stick with it, the author’s style warms up). I’ve read a lot about CFDs, but this clears up a lot of misconceptions, as well as introducing scatter plots and histogram views to better understand flow metrics of cycle time, wip and throughout. It also does a great job of explaining the assumptions underlying Little’s Law, and how setting your policies to comply with those will make your process more predictable. Key finding: you CAN answer “when will it be ready?” if you have such a process - but don’t use CFDs for forecasting - try Monte Carlo analysis. Great homework before taking the Scrum.org PSK certification
December 23, 2019
The best i advance kanban a lean metric book
This is the best book that I have read about advanced topics into agile kanban and lean it systems.
It has a very interesting approach without using any estimate method, but using statistical method to predict lead time with good team autonomus practices, like avoid outliers late target into get finishing, resteting little's law and several other good practices.
This is the best book that I have read about advanced topics into agile kanban and lean it systems.
It has a very interesting approach without using any estimate method, but using statistical method to predict lead time with good team autonomus practices, like avoid outliers late target into get finishing, resteting little's law and several other good practices.
February 28, 2019
A good explanation about the core metrics of Kanban, and how they can be used to improve the predictability of software development.
Unfortunately I found the tone a little condescending at times, which is a shame because it has all of the information explained clearly for beginners to lean metrics.
Unfortunately I found the tone a little condescending at times, which is a shame because it has all of the information explained clearly for beginners to lean metrics.
February 15, 2021
This book explains the concepts of little’s law, CFD & cycle time charts very well. It is easy to understand and written well. It would be good book to start with to learn about CFD & cycle time charts. The book does not go deep into how the charts could be analyzed or how to introduce it to the team but has the introductory information.
March 9, 2021
Книга, относящаяся к категории книг-находок. Сфокусировано, но достаточно подробно описывает очень ограниченный набор метрик, полезный для построения предсказуемого процесса разработки. Да и не только разработки.
Я в восхищении от того, что автор не просто сухо рассказал о математическом аппарате, но и о том, какую дорогу нужно пройти, чтобы внедрить его у себя.
Я в восхищении от того, что автор не просто сухо рассказал о математическом аппарате, но и о том, какую дорогу нужно пройти, чтобы внедрить его у себя.
April 4, 2021
Great book, I cannot say enough good words on this book and the works of Daniel Vacanti.
going towards the world of flow and kanban, and the assumptions to respect for achieving stability in systems, this book is a cornerstone for anyone wishing to get to real actionable flow metrics, predictability, and the basis of real no bullshit reliable stable process forecasting.
going towards the world of flow and kanban, and the assumptions to respect for achieving stability in systems, this book is a cornerstone for anyone wishing to get to real actionable flow metrics, predictability, and the basis of real no bullshit reliable stable process forecasting.
February 1, 2025
Really intrigued by focusing on the concepts of flow to create more predictable product development processes. Learned a lot about how to capture and visualize this data, and interpret it to guide changes to systemic process.
Writing style is fairly pedantic, but if you can stomach that there’s a lot of value to extract here.
Writing style is fairly pedantic, but if you can stomach that there’s a lot of value to extract here.
May 19, 2018
If you manage any kind of complex process where predictability is expected, you should read this. Even if you are up to date with 21st century approaches like Agile and Lean-Agile. The book is a step-by-step gude to creating a predictable delivery and also a very pleasant read.
July 2, 2022
Excellent book. It explains the core principles to have a predictable system in an agile environment. I had to re-read some parts to understand them better. It is definitely a book i will reference at work when people ask me about any estimation.
Read
July 24, 2024Should be required reading for anyone working in software development
Outstanding book, cannot recommend highly enough.
Walks you through not only the right metrics to collect but why and what to look out for.
Outstanding book, cannot recommend highly enough.
Walks you through not only the right metrics to collect but why and what to look out for.
July 6, 2017
A must read book!
December 14, 2017
Really good and practical book.
February 23, 2018
Made me reconsider the efficacy of my Sprints. Some really practical stuff in here.
January 21, 2020
A must read for all agilists, and Lean practitioners.
Read
December 3, 2024Good
January 19, 2020
This is a very cool book! It´s actually the first time I start to understand why and especially how Little´s Law can be used in software development. I have read ca. 15 books about Kanban in the past and this is the first one to explain Littles Law in a way that somehow makes sense. Must read for everyone who wants to use Kanban metrics.
February 13, 2017
This book single handedly reinvigorated my enthusiasm for Agile. It does a very good job at visualising a basic set of metrics that can be used for all sorts of process improvements. Everything is very well argued and a lot of common mistakes made by other Agile books are debunked. I'm certainly planning to put some of these in practice.
One downside to the book is the way it glosses over the making predictions using the Monte Carlo method. While the book promised several times to go into more depth on this subject, the actual chapters dedicated to it are very shallow.
One downside to the book is the way it glosses over the making predictions using the Monte Carlo method. While the book promised several times to go into more depth on this subject, the actual chapters dedicated to it are very shallow.
July 8, 2025
This is a great starting point and reference if you want to learn about metrics that help you improve flow in your agile team.
Daniel starts at the beginning and introduces flow and its relation to predictability in a complex process that contains uncertainty. He introduces cumulative flow diagrams and cycle time scatter plots and how they can help us achieve said predictability.
This book picks you up where you are and does a very good job going into the details. The flow of the book is logical and it is easy to follow the content.
The case study at the end of the book adds clarity and real-world experience to the ideas and tools introduced in this book.
It is highly recommended to anyone working in a complex environment, especially to agile and Scrum teams wanting to improve their predictability of delivery.
Daniel starts at the beginning and introduces flow and its relation to predictability in a complex process that contains uncertainty. He introduces cumulative flow diagrams and cycle time scatter plots and how they can help us achieve said predictability.
This book picks you up where you are and does a very good job going into the details. The flow of the book is logical and it is easy to follow the content.
The case study at the end of the book adds clarity and real-world experience to the ideas and tools introduced in this book.
It is highly recommended to anyone working in a complex environment, especially to agile and Scrum teams wanting to improve their predictability of delivery.
Displaying 1 - 30 of 33 reviews