Episode 156: Kanban with David Anderson

Essential Practices

Kanban's success in software development hinges on essential practices like configuration management and release processes. David Anderson emphasizes the need for a robust capability to release software, whether for internet applications or physical products. He notes that configuration management is crucial for tracking requirements and managing software versions, ensuring that only completed items are released 1. Anderson also highlights Kanban's adoption in IT departments of traditional industries, such as automotive manufacturing, where its lean principles optimize performance 2.

Configuration management is a core capability that is required to enable Kanban to work and it doesn't need to be super sophisticated.

--- David Anderson

This foundational capability is often already present in agile teams, facilitating the transition to Kanban.

   

Release Management

The importance of release capability and configuration management is underscored as key factors for Kanban's success. David Anderson shares insights from his experience with feature-driven development, noting that Kanban evolved from understanding flow problems and bottlenecks 3. He argues against the notion that Kanban is only for advanced teams, citing examples of teams achieving high maturity levels quickly through Kanban, even without prior Scrum experience 4.

The benefits have tended to go further and go further faster than we've seen with other agile methods.

--- David Anderson

This rapid maturity is attributed to the focus on configuration management, a fundamental capability for any team.