The Agile Wire: Talking Flow With Daniel Vacanti
Scrum vs. Kanban? How about Scrum and Kanban. Why would you want to use both? Scrum is based on Empiricism, Kanban is based on Flow, Flow enhances Empiricism and Empiricism enhances Flow. Take the best Scrum teams and the best Kanban teams and take an average person looking in on them they wouldn't be able to tell the difference.
Where can Scrum teams look to improve? Work on managing Flow within the Sprint. This is one of the foundational learning of the PSK course. Start with looking at your Work Item Age. How long has this thing been alive for? This will give you powerful information to help you start establishing Flow.
Empiricism, what does that even mean? Can you have it without a focus on good data?
https://www.dictionary.com/browse/empiricism?s=t
-
empirical method or practice
https://www.dictionary.com/browse/empirical
-
derived from or guided by experience or experiment.
-
depending upon experience or observation alone, without using scientific method or theory, especially as in medicine.
-
provable or verifiable by experience or experiment.
Story Points. Use rough sizing as a way to analyze the work and break it down. Cause really, the scores and made up and the points don't matter.
Delay begets delay. The longer something takes to finish the more chance that something is going (like COVID-19!) to happen that makes it take longer to get done.
2 fundamental myths in software development.
-
The more we work on the more we'll get done
-
The sooner we start something the sooner it will get done
The solution to both of these problems is to limit work in progress.
Flow Efficiency. Think about things that are flowing through your process as either 1. Actively being worked on or 2. Not Actively being worked on. So now we look at the Total Active Time divided by the Total Time it took moving through your system.
Actionable Agile Website