Kanban for large scale off-shored mobile.de. January Munich. Feedback to mandrezak@team.mobile.de

Size: px

Start display at page:

Download "Kanban for large scale off-shored maintenance @ mobile.de. January 26 2010 - Munich. Feedback to mandrezak@team.mobile.de"

Duane Maurice Fisher
8 years ago
Views:

1 Kanban for large scale off-shored mobile.de January Munich Feedback to mandrezak@team.mobile.de

2 feedback for all things Kanban at OOP 2010: #oopkanban

3 small bugs, small and medium features Photo by dolorix -

4 national vs. international: dedicated team Photo Nasa, visible earth

5 hard to manage, lots of WIP, hierarchical culture

6 cycle time = 28 days lead time = 52 days

7 you want half of these times? you have specialized teams? they are distributed?

8 Enter Kanban! (signal card)

9 Photo by john w -

10 10 Photo Sune Gynthersen, bestbrains.dk

11 value stream mapping

12 Input Development QA Production Ongoing Done Ongoing Done

13 design of Kanban cards

14 tasks / stories are represented as cards

15 map cards to value stream on the wall

16 Input Deelopment QA Production Ongoing Done Ongoing Done

17 definition of Work-In-Progress-limits (WIP-Limits) & Pull

18 Input Development Acceptance 5 5 Ongoing Done Ongoing Done Produktion Pull Fixed WIP-Limits in relevant phases

19 definition of input and output-cadence

20 e.g. weekly prioritization e.g. bi-weekly releases Input Development Acceptance 5 5 Ongoing Done Ongoing Done Production Pull Fixed WIP limits for relevant phases

21 definition of done per phase and / or rules on pulling

22 Kanban cards visualize overall process state and clearly indicate bottlenecks in the process ---> basis for applying TOC

23 Theory of Constraints (light) - Eliah Goldratt: identify bottleneck max. stress on bottleneck eliminate (or minimize) bottleneck Eliah Goldratt - The Goal

24 definition of WIP limits reduction of batch size reduction of lead time (Little s law)

25 Little s Law: lead time = WIP / throughput easy to change: discipline / Flow hard to change: mid term change process

26 estimations ---> calculation of cycle time and lead time

27 @

28 Maintenance - own track

29 why does Kanban match our requirements?

30 Chasin! low visibility my project Let s try! Photo by Balakov -

31 Things are slow I like it! Photo by Dunechaser -

32 estimations not required

33 frequent prioritization! -> weekly production incidents any time

34 Output Queue flexibly coupled to release cycle and hotfixes

35 how did we implement it?

36 Photo by Dunechaser - Semi-dictator style

37 I wanted desperately

38 first process draft

39 Input Analyse Development QA Published Deployed Ongoing Done Ongoing Done Ongoing Done

40 feature branches! Photo by danorbit. -

41 training via Photo by pt -

42 vacation :-( Photo by wili_hybrid -

43 QA doesn t join the flow Photo by fsudaft -

44 not enough integration systems Photo by bobthemtnbiker -

45 QA w/ limited availability -> buffer Photo by rev -

46 Entwicklung QA 5 5 Entwicklung ready f. QA QA Ongoing Done Ongoing Done

47 flow! Photo by ViaMoi -

48 sucess

49 Cycle Time ,0 22,5 15,0 august september 8 october 2 november 7,5 0 49

50 Lead Time (2-3 weekly releases) 52 60,0 45,0 august 28 september 22 october 30,0 15,0 0 50

51 but: once Chaos - now controlled

52 good mood in the team through flow experience

53 great communication tool

54 heavy discussion with uninvolved great buy-in with those involved

55 maintenance of whole platform from Jan 2010 w/ Kanban

56 1PO 1 Technical Lead 1 process guy 7 developers

57 Kanban adjustments required

58 introduction of classes of service for production incidents required / SLA

59 Thanks for your time and attention! contact: twitter.com/markusandrezak slideshare.com/mandrezak

60 more on Kanban Thu 14:30-15:30 Stefan Roock & Bernd Schiffer Was ist dran an Kaban Feedback: #oopkanban 02/ Feb 2010 articles by Stefan Roock & Markus Andrezak

Lean Metrics How to measure and improve the flow of work. Chris Hefley, CEO of LeanKit. November 5 th, 2014

Lean Metrics How to measure and improve the flow of work Chris Hefley, CEO of LeanKit November 5 th, 2014 Introduction to Lean Metrics What metrics should you measure? How to track them? What effect do