kanban

Encouraging Feature-level progress tracking in Kanban

One of the key questions project managers and senior management in general ask themselves and their teams on an ongoing basis is – "Are we on track to deliver the scope we committed to, on time". In some environments "on budget" is added to the question. If you are talking about a Release Scope, the answers are …

Read more

MMF driven sprints in a Kanban world

The more experience I get with Kanban, and the more I talk about it with people, I see that one of the main challenges is maintaining some form of goal-driven cadence that energizes the team. If every one of your Kanban Cards/Stories is an independent goal (e.g. a support environment) its easy to connect to …

Read more

Kanban early warning using a predictive variant of SPC

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 …

Read more

Why I think slack is highly important during an Agile/Kanban transition

(Note, this post is about slack the concept not Slack the collaboration platform. Though Slack the platform is great as well) Actually, the title is wrong. I think slack is highly important during any change initiative where you expect continuous improvement of the process and practices. The importance of slack is not new. Not in …

Read more

The Ant and the Grasshopper – Application for product development

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 …

Read more

Can lanes be skipped in a kanban board?

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 …

Read more

Finding the right Dev to Test Ratio when working in Kanban

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 …

Read more

So what is the right ratio between developers and testers?

One of the questions I’m asked quite frequently is what is the right ratio between developers and testers. A variant on that question is what I typically see in other organizations as the ratio. Well lets answer the second variant and then try to deal with the first. Typically what we see in agilesparks customers …

Read more

Using Kanban to drive Continuous Improvement and Management Teams

It seems like new uses for Kanban are cropping up every day. One of those ideas is to use Kanban in order to drive Continuous Improvement efforts.

The cost of iterations applied to Kanban as well…

My latest blog post was about the costs and challenges of iterations, as well as what to do to overcome them. One of the other things I’m working on is Kanban. I believe Kanban is a great fit to many teams and situations. Specifically doing Scrumban is a great way to get the benefits of …

Read more