Kanban is a Tool, NOT a Solution

About Jimi Fosdick

With more than 14 years of experience in product development, Jimi Fosdick has worked in a wide range of industries, including publishing, software, advertising, and the public sector. As one of CollabNet’s Certified Scrum Trainers, he conducts dozens of public courses around the world each year, helping organizations to surface dysfunction and improve processes through Scrum.

  1 comment for “Kanban is a Tool, NOT a Solution

  1. September 26, 2012 at 11:11 pm

    Great piece, Jimi. In my observations, “Scrumban” is unfortunately here to stay, and not just on support teams. It’s simply easier than Scrum to deploy and does not expose harsh realities. I am seeing more teams go to kanban from Scrum (or whatever machination of the two) but have yet to see it be an advantageous move for the business. The biggest pitfall is the lack of incremental deliverables. In my experience, the business notices this too late, when “scrumban” has become the norm and teams don’t want to change. It’s just lazy agile, wrapped inside a fancy sounding name. Sure, Scrum can be too much ceremony in certain circumstances, but agile teams need to assess their needs with a clear view. Is Scrum really too much ceremony, or is it just too hard?

Leave a Reply

Your email address will not be published. Required fields are marked *

*

CAPTCHA Image

*