Kanban is all about flow, that’s why you can restrict the number of spaces in each swim-lane. Scrum, on the other-hand, has more of an implicit way of dealing with flow, the velocity that a team uses to determine how much work they can commit to is also restricting the amount of work in progress. […]

Happy New Year to all – when I started considering Golden Rules and how they applied to Kanban last year I was sure that the rules themselves would need to change, or at least be interpreted differently. Looking for where the “value” is certainly a case in point – in an earlier blog I’ve already […]

Regardless as to whether you’re using Scrum or Kanban this is very important. In Scrum poorly defined (or absent) acceptance criteria can lead to a story being carried over as it’s likely that during testing some aspect that wasn’t made clear fails the testing and requires re-work. In Kanban the story also potentially can be […]

A key part of Agile is to continually improve. We can always find ways to get better and there should always be the opportunity for the team to meet for retrospectives. With Scrum the iterations provide a regular cadence for retrospectives, with Kanban iterations aren’t mandatory but we should still allow retrospectives to happen at […]

This makes sense regardless of whether you’re using Scrum or Kanban – keep the tool that you’re using regularly up dated so it reflects reality. It’s frustrating when inspecting an agile board to ask questions only to find the answer is that in reality things have changed but the team have been too busy or […]

With Scrum, before a story gets on an iteration it is on the product backlog. The backlog is essentially a queue of work in a priority order and the nearer the story gets to the top of the backlog the more likely it will be included in the next sprint. With Kanban you don’t have to have the concept of […]

From my point of view this is really important for Scrum, that’s why it’s Rule Number 1! If you over commit then you end up carrying over stories on a regular basis, this means that the next iteration is already more difficult as there is a lot of unfinished work and this affects the team’s productivity […]