0
Continuously improving using Kanban

   CONVERTING A SCRUM TEAM
   TO KANBAN
2010-09-24

Mattias Skarin                   ...
2010-09-24

Mattias Skarin   2
Who am I?


Coach                   Entrepreneur            Engineer

  Help IT                   Extreme                9...
Look out for

   How we are learned the right process
 (and what problems to solve)




2010-09-24

Mattias Skarin        ...
Situation

    Sprint burndown




                 Why no reaction?

                                    ”Not sure scrum ...
Context – team setup

                                               AB        BV

                                       ...
What is the problem?
Product owner
   Deliver something with quality
   Team overstressed
   Estimates wrong, up to 5 time...
What to do first?                                                  Added visibility


                                    ...
After two weeks of kanban




2010-09-24

Mattias Skarin              10
Dude – get real..




                    Team 2




     Team 1




2010-09-24

Mattias Skarin               11
What’s next?
                                                                               Runnable
      Backlog    esti...
+ Better qa/dev ratio
  Inject TDD                                           + Much needed refactorings
                  ...
Next learning

                                                                              Runnable
      Backlog       ...
Mixing bad and good work
                               Trunk

                      Testing, Packaging



FR




        ...
Adding test design for refined flow

                                                                               Runnab...
Team taking charge of the process
                                                                                Runnable...
Small steps
                                  You know what? Customer now
                               trust me when I s...
Why it is important to
2010-09-24
                 understand the problem
Mattias Skarin                        19
”Team no longer
                                   work overtime”
                 Project manager




2010-09-24

Mattias...
Improvement tracking

      140,00

      120,00

      100,00
Days / percentage




             80,00
                  ...
Us - one
                 year later




2010-09-24

Mattias Skarin         23
What is different?
Before                                        After 1 year
    Sprints                                 ...
What is same?
    Still multiple projects (but better risk mix)
    External clients behaviour not changed

              ...
2010-09-24

Mattias Skarin   26
Meet the team




2010-09-24

Mattias Skarin   27
Thanks for listening!


                   Psst..
             Kanban Coach Camp
               November 9-10




   Expan...
Upcoming SlideShare
Loading in...5
×

Converting a scrum team to kanban - Mattias Skarin

1,481

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,481
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
32
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Converting a scrum team to kanban - Mattias Skarin"

  1. 1. Continuously improving using Kanban CONVERTING A SCRUM TEAM TO KANBAN 2010-09-24 Mattias Skarin 1
  2. 2. 2010-09-24 Mattias Skarin 2
  3. 3. Who am I? Coach Entrepreneur Engineer Help IT Extreme 9 years companies stay Solutions software dev competitive Bizplant Acting CTO mattias.skarin@crisp.se Blog: http://blog.crisp.se/mattiasskarin Book: ”Kanban and Scrum – making the most of both” 3
  4. 4. Look out for How we are learned the right process (and what problems to solve) 2010-09-24 Mattias Skarin 4
  5. 5. Situation Sprint burndown Why no reaction? ”Not sure scrum is helping” 2010-09-24 Mattias Skarin 5
  6. 6. Context – team setup AB BV EK Client user Client project specialist manager Client Side [uk] Q&A Meeting 1/w Our Side [fr] BS IK EK ST Product Owner/Project manager SH 2010-09-24 Mattias Skarin 6
  7. 7. What is the problem? Product owner Deliver something with quality Team overstressed Estimates wrong, up to 5 times Team off Switching too much between tasks Doing to much at the same time Client Descoped too far Project above team’s capacity 2010-09-24 Mattias Skarin 7
  8. 8. What to do first? Added visibility Runnable Backlog estimation @ Client In queue Estimated In queue Work Done Dev Merge Ci PO Test 2010-09-24 Mattias Skarin 9
  9. 9. After two weeks of kanban 2010-09-24 Mattias Skarin 10
  10. 10. Dude – get real.. Team 2 Team 1 2010-09-24 Mattias Skarin 11
  11. 11. What’s next? Runnable Backlog estimation @ Client In queue Estimated In queue Work Done Dev Merge Ci PO Test ..why is work stuck here? 8+ devs 2010-09-24 1.5 testers Mattias Skarin 12
  12. 12. + Better qa/dev ratio Inject TDD + Much needed refactorings + Self confidence Free some space! • Simplify estimates • Abolish sprints – regular release cadance 2010-09-24 Mattias Skarin 13
  13. 13. Next learning Runnable Backlog estimation @ Client In queue Estimated In queue Work Done Dev Merge Ci PO Test ..why are stories dropping out? 2010-09-24 Mattias Skarin 14
  14. 14. Mixing bad and good work Trunk Testing, Packaging FR UK Changing branch policies Trunk - releasable FR – unit tested EN – unit tested Mattias Skarin 15
  15. 15. Adding test design for refined flow Runnable Backlog estimation @ Client In queue Estimated In queue Work Done Test design Dev PO Test Build Package 2010-09-24 Mattias Skarin 16
  16. 16. Team taking charge of the process Runnable Backlog estimation @ Client In queue Estimated In queue Work Done Test Remember! design Dev Test Build Rel. Unit Func Gui Server Dude- Talk! Tag! Merge! 17
  17. 17. Small steps You know what? Customer now trust me when I say we are going to deliver something What is this shit in Project manager our code? Moving on Team - Train in root cause analysis - Train in problem solving 2010-09-24 Mattias Skarin 18
  18. 18. Why it is important to 2010-09-24 understand the problem Mattias Skarin 19
  19. 19. ”Team no longer work overtime” Project manager 2010-09-24 Mattias Skarin 20
  20. 20. Improvement tracking 140,00 120,00 100,00 Days / percentage 80,00 Velocity (pts) 60,00 Focus factor 40,00 20,00 0,00 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 Week 2010-09-24 Mattias Skarin 21
  21. 21. Us - one year later 2010-09-24 Mattias Skarin 23
  22. 22. What is different? Before After 1 year Sprints Release when ready (needed) Little teamwork, multiple Teamwork, despite multiple projects in sprint projects Planning & sp estimation T-shirt sizing Dispair over improvement Team focused, management supported improvements Key tech debts solved Nailing down the problem behind the improvement is getting harder - requires more effort and thinking.. 2010-09-24 Mattias Skarin 24
  23. 23. What is same? Still multiple projects (but better risk mix) External clients behaviour not changed Order Development Waiting Client QA In prod 18d 50d 43d Dev 17% Waiting 38% QA 38% Team project Backflow backlog Project #1 Not in prod .. but management are working on it Project #2 Not in prod and no longer considers this a team problem Project #3 In Work Mattias Skarin 25
  24. 24. 2010-09-24 Mattias Skarin 26
  25. 25. Meet the team 2010-09-24 Mattias Skarin 27
  26. 26. Thanks for listening! Psst.. Kanban Coach Camp November 9-10 Expand your improvement skills http://www.crisp.se/kanbancoachcamp 2010-09-24 Mattias Skarin 29
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×