Why is it that organizations using Agile methods such as Scrum and SAFe struggle with and suffer anxiety over dependency management, while it is largely a non-issue for organizations using the Kanban Method?
Reservation systems have been observed in Kanban implementations since 2008. They are used immediately upstream of a delivery kanban system, to indicate the desired start date of the request for work (a work item).
We don´t perform a specific activity to prioritize work for kanban systems. Instead we practice dynamic prioritization, selecting items of work on-the-spot, based on risk, or other desirable outcomes such as fairness, good customer service, or value.
Over the past 15 years, I have observed that managing dependencies has been a constant source of anxiety and a huge challenge for organizations adopting Agile methods. Meanwhile, dependency management has largely been a non-issue for organizations using the Kanban Method.
The Kanban Maturity Model release 1.2 is a new updated model incorporating organizational culture and managed evolution is far more extensive than its predecessors. The accompanying second edition book is 3 times the size of its predecessor based on the original beta release in April 2018.
I´ve been studying evolutionary theory recently, and how it applies to non-biological entities, such as buildings and businesses. This is the first of what will probably be a short series of blog posts providing new, or deeper insights into the application of evolutionary change in organizations.