A simple elevator-pitch explanation of Kanban for Scrum practitioners — what Kanban adds, what it changes, and why both approaches are complementary rather than competing.
Encouraging progress at the feature level rather than at task or sprint level: the management behaviors and visibility practices that shift teams from activity to outcome focus.
Using Minimally Marketable Features as the atomic unit for Scrum sprints in a Kanban-influenced delivery system — improving business value flow while keeping sprint structure.
Using statistical process control techniques with Kanban flow data to detect early warning signs of delivery problems before they become crises.
Slack is not wasted capacity — it is the prerequisite for improvement, learning, and sustainable delivery. Why teams and organizations need breathing room during agile/Kanban transitions.
The Ant vs Grasshopper fable applied to software development: why feature-first thinking creates a QA debt winter, and how agile and Kanban teams stay in sustainable ant mode throughout the release.