Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kanban experiences at Volvo IT - Anders Jonsson, LTG-4


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Kanban experiences at Volvo IT - Anders Jonsson, LTG-4

  1. 1. Kanban@Volvo IT
  2. 2. Program X <ul><li>Global solution for all Volvo BA/BU’s </li></ul><ul><li>Program (Volvo IT part): </li></ul><ul><ul><li>Scaled from 25 to 50 persons and included a new site (Gothenburg, Wroclaw and Brazil) </li></ul></ul><ul><ul><li>Multiple releases (several releases / year) </li></ul></ul><ul><ul><li>Multiple functional patches (several / year) </li></ul></ul><ul><ul><li>Multiple stakeholders </li></ul></ul><ul><ul><li>Multiple projects (7) and Maintenance@once </li></ul></ul><ul><ul><li>.NET technology </li></ul></ul>
  3. 3. Background – why Kanban <ul><li>Volvo IT must meet the challenge to increase the delivery capacity from Volvo IT regarding future and increased workload at Volvo XX, dept. XYZ and also resolve how to handle multiple releases from multiple stakeholders. </li></ul><ul><li>We needed something that could scale beyond our current way of working (Scrum) </li></ul>
  4. 4. Approach <ul><li>We (Åsa Zetterlund, Petra Hallin and I) attended Kanban training given by David Anderson </li></ul><ul><li>Trained the entire team (~45-50 persons) onsite </li></ul><ul><ul><li>Walkthrough of Kanban concepts </li></ul></ul><ul><ul><li>Played the getKanban Board Game, </li></ul></ul><ul><li>Created the and redefined the board </li></ul><ul><li>Spent a lot of time defining the process </li></ul><ul><ul><li>Policies </li></ul></ul><ul><ul><li>Roles and feature teams </li></ul></ul><ul><li>Meetings structure </li></ul>
  5. 5. Visual board (initial version) Project ABC Project YYY Project XYZ Analysis FDCG queue Ready for IT WIP [xx] In prog Done Expediters IT Dev Analysis WIP [xx] Build Queue Development WIP [xx] In prog In prog Done Done Test WIP [xx] Package & deploy Live Maintenance
  6. 6. Kanban board
  7. 7. Lessons learned <ul><li>The team learned Kanban really fast </li></ul><ul><li>Knowledge sharing in the feature teams was good </li></ul><ul><ul><li>Distribution of knowledge </li></ul></ul><ul><li>Work progressed, in general, in a good way in the feature teams </li></ul><ul><li>Maintenance and Kanban worked really well together from day one (blends perfectly) </li></ul><ul><li>Kanban gave us a very good overview of the work across projects etc (easier to maintain several teams this way) </li></ul><ul><li>Productivity goals was reached in large </li></ul><ul><li>Scrum and Kanban works really well together (you need to use the good parts in both tool kits) </li></ul><ul><li>Capacity planning became really easy and visible </li></ul>
  8. 8. Lessons learned cont. <ul><li>Hard to get daily meetings to work properly </li></ul><ul><li>We focused a lot on the board content (dev process, policies etc) => didn’t have time or energy to improve our Kanban setup as soon as we would have liked </li></ul><ul><li>Don’t do Excel for 50 persons (it doesn’t scale though it’s a great tool)! </li></ul><ul><li>Traditional PM and Kanban doesn’t blend easily </li></ul><ul><li>You still need Scrum Masters (Kanban masters) and also a board owner when doing “program Kanban” (several projects etc) </li></ul><ul><li>You WILL NOT get it right the first time (this is a 100% guarantee) so GET GOING. But… it takes more time than anticipated to get the process in place and everyone to understand it so be prepared to spend some initial time and also to change it several times </li></ul><ul><li>Start with the existing process and make it visible </li></ul>
  9. 9. <ul><li>Kanban is like water </li></ul><ul><li>” It goes around the rock and g iven time it molds the rock” </li></ul><ul><li>Quote:David Anderson, Vienna 6 th of December 2011 </li></ul>