Kanban Applied to Scrum

I enjoyed this short and concise video on Kanban.

Kanban is a lean Agile methodology.

Kanban is a visual queue of work and helps with, as BTI360 states, the issues around unclear development steps, task switching, and partially done work.

  • Kanban helps with unclear development steps in that Kanban helps the team visualize flow of work and high level transparency to involved stakeholders.
  • Kanban helps with constant task switching in that Kanban helps by placing work-in-progress limits so that team members can focus on completion of work or value.
  • Kanban helps with partially done work in that Kanban helps by delivering fully complete work 100%.
Highly visible flow helps team address bottlenecks and on-demand improvement. Adjustments are made as they surface.

10 Responses to “Kanban Applied to Scrum”

  1. Gary
    October 26, 2011 at 9:41 am #

    This is why we switched to Pivotal Tracker. SCRUM with KANBAN is a Godsend

  2. Erwin Verweij
    October 27, 2011 at 11:06 am #

    This looks great, only one question. How does one determen the max number of items in each column. The 3,5 & 2 in this example. How do i find out the limit?

    • peter
      October 27, 2011 at 12:17 pm #

      Limit is determined by trial and error by the team, according to what they can do, capacity for work and where bottlenecks arise in the flow.

      • Erwin
        October 27, 2011 at 12:24 pm #

        Ok. I’m already doing Scrum. let’s say there are only two testers in the team. Does that mean that the testing column has the number 2. And i have 5 developers who can work on 4 user stories, so implementation is 4. Something like that. And then try to improve?

        it feels a little bit like waterfall or am i wrong.

        • peter
          October 27, 2011 at 12:33 pm #

          Yes. You can start there. When there are blockages through the system, other developers/team members can help swarm the story to help it get complete.

          It isn’t waterfall, but more manufacturing-esque.

          What we find is that through visually seeing progress through a kanban board, you can see where blockages are and understand WIP (work in progress) limits on teams better.

          Kanban is about continuous flow through the system, understanding how to improve flow of work. A great resource is:
          http://www.crisp.se/henrik.kniberg/Kanban-vs-Scrum.pdf

  3. Tommy Ball
    October 30, 2011 at 7:55 am #

    Good one Peter! Thanks!

  4. Jacob
    November 1, 2011 at 4:41 pm #

    I don’t think Scrum has the issues raised in this video; so long as you do Scrum and not ScrumBut (it’s Scrum, but…) – and of course, ScrumBut isn’t Scrum… Just saying ;-)

    Interesting video none the less. Thanks for sharing.

Trackbacks/Pingbacks

  1. Kanban Applied to Scrum | Agile Scout | Agile Software Development | Scoop.it - October 27, 2011

    [...] Kanban Applied to Scrum | Agile Scout [...]

  2. New PM Articles for the Week of October 24 – 30 « The Practicing IT Project Manager - October 31, 2011

    [...] Peter Saddington shares a video on Kanban, as practiced at your local Starbucks, and how it’s applied to Scrum.  Safe for work. [...]

Leave a Reply