Using Kanban to Drive Management Team Improvement
How management teams use Kanban to focus and execute improvement work — prioritizing the improvement backlog, using WIP limits, and leading by example.
How management teams use Kanban to focus and execute improvement work — prioritizing the improvement backlog, using WIP limits, and leading by example.
The case for small batches: why large work items slow everything down, and how cutting batch size improves flow, quality, and predictability.
Why the Product Owner is often the most underinvested role in Scrum, and why getting stories to READY-READY is a business investment, not a process step.
The overhead of iterations doesn't disappear with Kanban — it shifts from fixed-cadence overhead to on-demand transaction cost you can optimize differently.
Severity vs. priority in bug tracking — why these two axes matter, why teams conflate them, and how keeping them separate improves triage and flow.
Patterns for tracking issues across multiple concurrent releases — managing parallel streams without losing visibility or creating conflicts.