Shifting from Scrum to Kanban

Table of Contents

Format: Experience report
Duration: 60 minutes

Abstract

We in Huitale are developing a consumer portal that serves over 1000 registered users. After a year of developing the portal we had done 26 sprints but we felt that Scrum was not serving us in the best possible way. We decided to look around to improve our Scrum implementation and eventually we started shifting to Kanban in January 2009.

This sessions is a walk trough of our journey. We want to share our experiences and lessons learned so that your implementation of Kanban would be less painful.

Detailed description & timetable

0-10 Short introduction to Kanban

10-15 Starting point, our Scrum after 26 sprints

  • Why did we initiate the change

20-35 Step-by-step walk trough

  • We can release every day, why we should wait for iterations to end
  • Introduction of WIP limits and cycle time
  • From story points to T-shirt sizing and from stories to Minimum Marketable Features
  • Service levels and introduction of buffers

35-45 Where are we now

  • How do we plan and release
  • How do we do roadmaps
  • What do we measure and how

45-50 Lessons to take home

50-60 Q&A

Bio

Marko Taipale is Lean/Agile coach and CTO of Huitale, which conveniently allows him to field test agile in product development. He shares some of his experiences in his blog http://huitale.blogspot.com/
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Jul 23, 2009

    Vasco Duarte says:

    Your presentation probably considers these already, but will you tackle the "why...

    Your presentation probably considers these already, but will you tackle the "why" for each of the changes that you will be describing in your presentation?