A Confession. While I'm a great fan of using SPC charts to explore specific cycle times and reduce variation / continuously improve a Kanban System (a great blog by benjamin mitchell), I'm only seeing preliminary results in the field with teams I'm coaching. The main reasons are lack of tooling, lack of incentive to manually manage …
(Note, this post is about slack the concept not Slack the collaboration platform. Though Slack the platform is great as well. We use it at AgileSparks and love it, although it eats up some of our slack time…) Actually, the title is wrong. I think slack is highly important during any change initiative where you …
I’m sure everyone is familiar with some version of the The Ant and the Grasshopper (or הצרצר_והנמלה) While talking to a Product Manager today, I was asked “How come we always end up without QA resources at the end of the version” and was reminded of this tale. Most projects behave like the Grasshopper. Focusing on …
A question in a recent kanban workshop was how to deal with the fact that some work has different workflow than others For example: Features need to go to testing after implementation Escalation cases without patches need to go to support for returning to the customer after implementation and that’s it Escalation cases with a …
In a previous post I started talking about the ratio between Dev and Test, and promised to revisit how it looks like in an Agile/Kanban environment. Whenever I talk to teams/managers about Kanban, whether as part of a workshop, or with a team actually practicing Kanban, the issue of testing as the bottleneck surfaces quite …
