1. Board of directors Henrik Kniberg Agile/Lean coach www.crisp.se The Thinking Tool called Agile Keynote, Lean-Agile-Scrum conference Zurich, Sep 7, 2010 henrik.kniberg@crisp.se +46 70 4925284 Copyright notice These slides are licensed under Creative Commons. Feel free to use these slides & pictures as you wish, as long as you leave my name and the Crisp logo somewhere. For licensing details see: http://creativecommons.org/licenses/by/3. 0/ http://creativecommons.org/licenses/by/3. 0/ All slides available at: http://www.crisp.se/henrik.kniberg/

2. 2 Purpose of this presentation To illustrate how Lean and Agile can fit together Henrik Kniberg 2

3. 3 3 Lean XP Scrum Agile TDD Kanban Continuous Integration What is all this stuff? Pair programming Refactoring Planning poker

4. 4 Tools Henrik Kniberg 4

5. 5 5 Pair programming Product Owner role Physical tools Process tools a.k.a. ”organizational patterns” Thinking tools a.k.a. ”mindsets” or ”philosophies” Lean Agile Toolkits a.k.a. ”frameworks” Scrum XP Visualize the workflow Kanban Systems Thinking Theory of Constraints RUP Tool ”anything used as a means of accomplishing a task or purpose.” - dictionary.com

6. 6 Lean & Agile process toolkits Henrik Kniberg 6 Kanban Scrum XP Values & Principles Lean, Agile, Theory of Constraints, Systems Thinking, etc Other lean tools (Value Stream Mapping, Root Cause Analysis, etc)

7. 7 Henrik Kniberg 7 Key point Compare for understanding, not judgement Tools can be combined

8. 8 What is ”un-agile”? Henrik Kniberg 8

9. 9 What is ”Agile”? Henrik Kniberg 9 www.agilemanifesto.org

10. 10 Waterfallitis Henrik Kniberg 10 Waterfallitis (n) (a.k.a. Waterfall obsession syndrome) The mistaken assumption that everything that isn’t Scrum is Waterfall. And that Waterfall always fails. Waterfallitis (n) (a.k.a. Waterfall obsession syndrome) The mistaken assumption that everything that isn’t Scrum is Waterfall. And that Waterfall always fails.

11. 11 Toyota Henrik Kniberg 11

12. 12 Waterfall @ Toyota Henrik Kniberg 12 Source: We visited Toyota in Japan during our ”Lean Study Tour”, April 2009. Requirements Module design Coding Integration test System test Acceptance test System design Architecture Unit test … but they are moving towards Lean & Agile SW dev

13. 13 What is ”waterfall” anyway? Henrik Kniberg 13 “I believe in this concept, but the implementation described above is risky and invites failure” The remainder of this discussion presents five additional features that must be added to the basic approach to eliminate most of the development risks ”Managing the development of large software projects” Dr Winston Royce, 1970 Step 5: Involve the customer – the involvement should be formal, in depth, and continuing

14. 14 Henrik Kniberg 14 Key point The borders between Lean, Agile, and Waterfall are fuzzy

15. 15 The illusion of ”good” and ”bad” tools Henrik Kniberg 15

16. 16 Henrik Kniberg 16 The illusion of a ”bad tool” The old tool was better! Don’t blame the tool!

17. 17 The illusion of a ”good tool” Henrik Kniberg 17 We succeeded thanks to Process X! Placebo effect The tendency of any medication or treatment, even an inert or ineffective one, to exhibit results simply because the recipient believes that it will work. Hawthorne effect A form of reactivity whereby subjects improve an aspect of their behavior being experimentally measured, simply in response to the fact that they are being studied, not in response to any particular experimental manipulation. Sources: http://en.wiktionary.org/wiki/placebo_effect http://en.wikipedia.org/wiki/Hawthorne_effect “It was suggested that the productivity gain was due to the motivational effect of the interest being shown in them” Really?

18. 18 Are there no universally Good or Bad tools? Probably not. But some are pretty close. Almost always a good idea: Visualize the workflow Limit work in progress Focus on quality Prioritize Short feedback loops Henrik Kniberg 18 Kanban Jim Johnson Chairman of Standish Group There is no silver bullet, but agile methods come very close

19. 19 Henrik Kniberg 19 Distinguish between… Using the tool wrongUsing the wrong tool Neither of these problems are caused by the tool

20. 20 Henrik Kniberg 20 Key point Don’t blame the tool Tools don’t succeed or fail, people do. People choose where, when, how, and why to use which tool. Don’t blame the tool Tools don’t succeed or fail, people do. People choose where, when, how, and why to use which tool.

21. 21 Know your goal Henrik Kniberg 21

22. 22 The Goal is the goal! A Tool is just a tool Henrik Kniberg 22 How do we get Agile? What is your goal? We want to get Agile. Why?

23. 23 Sample goal - Toyota Henrik Kniberg 23 Are you staying in business so you can earn money? Or are you earning money so you can stay in business? (Toyota) Are you staying in business so you can earn money? Or are you earning money so you can stay in business? (Toyota) Source: ishii-san’s slides during our ”Lean Study Tour” to Toyota, April 2009.

24. 24 Henrik Kniberg 24 What is the goal?

25. 25 Identify the goal & alternative ways to reach it Henrik Kniberg 25 Chop down the tree Get firewood Heat Buy firewood Put on a sweater Cozy Virtual Fireplace DVD Electric heater Light fire Gather deadwood

26. 26 Henrik Kniberg 26 Focus on Why first, then How Focus on Why first, then How Key point

27. 27 Solve the right problem Henrik Kniberg 27

28. 28 Henrik Kniberg 28 Bail water Water in boat Hole in boat Fix hole Solve root causes, not symptoms

29. 29 Henrik Kniberg 29 Solve problems, not symptoms Solve problems, not symptoms Key point

30. 30 Example: Evolving Scrum Henrik Kniberg 30

31. 31 Scrum Sprint Henrik Kniberg 31 week 1week 2week 3week 4week 5week 6week 7week 8 Sprint 1 Plan & commit Review (release?) Sprint 2 Retrospective a timeboxed, fixed-commitment iteration

32. 32 Shu-Ha-Ri stages of learning Shu = follow the rules Ha = change the rules Ri = never mind the rules Henrik Kniberg 32 ScrumButophobia (n) See also: Scrumdamentalism Fear of doing Scrum wrong Symptom: Stuck in Shu ScrumButophobia (n) See also: Scrumdamentalism Fear of doing Scrum wrong Symptom: Stuck in Shu ScrumBag (n) A coach or consultant with a Scrumdamentalist streak Symptom: Spread of ScrumButophobia ScrumBag (n) A coach or consultant with a Scrumdamentalist streak Symptom: Spread of ScrumButophobia Scrumdamentalism (n) The mistaken belief that Pure Scrum always is the right solution.

33. 33 Example: Middle of sprint 1 Henrik Kniberg 33 To DoDoingDone A B C D PO I’d like to have E! Wait until next sprint! E

34. 34 Example: Sprint 1 retrospective Henrik Kniberg 34 PO New policies: Max 1 item in progress Allow To Do items to be swapped out

35. 35 Example: Middle of sprint 2 Henrik Kniberg 35 To DoDoingDone E F G H 1 PO I’d like to have J! or wait until next sprint! J OK, swap out G or H Policy Max 1 item in progress Allow To Do items to be swapped out Is this still Scrum?

36. 36 Example: Sprint 2 retrospective Henrik Kniberg 36 PO New policies: Max 1 item in progress Allow To Do items to be swapped out Max 2 items in To Do To Do items can be added at any time (as long as limit isn’t exceeded)

37. 37 Example: A few weeks later Henrik Kniberg 37 To DoDoingDone K L M N 1 PO I’d like to have P! or wait until there is space in To Do P OK, swap out M or N 2 Process changes: Max 1 item in progress Allow To Do items to be swapped out Max 2 items in To Do To Do items can be added at any time (as long as limit isn’t exceeded) Is this still Scrum?

38. 38 Alternatives to Sprints Sprints Henrik Kniberg week 1week 2week 3week 4week 5week 6week 7week 8 Sprint 1 Plan & commit Review (release?) Separate cadences week 1week 2week 3week 4week 5week 6week 7week 8 Planning cadence (2w) Sprint 2 Retrospective Release cadence (1w) Retrospectives (4w) Event-driven week 1week 2week 3week 4week 5week 6week 7week 8 Planning (on demand) Release (on demand) Retrospectives (4w)

39. 39 Henrik Kniberg 39 Focus on process improvement rather than process compliance Key point

40. 40 Example: Kanban Henrik Kniberg 40

41. 41 ”One day in Kanban land” Henrik Kniberg 41 http://blog.crisp.se/henrikkniberg/tags/kanban/

42. 42 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 1 – one piece flow Henrik Kniberg 42 B C A D E F G H I J L K M

43. 43 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 1 – one piece flow Henrik Kniberg 43 B C A D E F G H I J L K M

44. 44 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 1 – one piece flow Henrik Kniberg 44 B C A D E F G H I J L K M

45. 45 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 1 – one piece flow Henrik Kniberg 45 B CA D E F G H I J L K M

46. 46 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 1 – one piece flow. Henrik Kniberg 46 B CA D E F G H I J L K M

47. 47 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 47 B C A D E F G H I J L K M PO

48. 48 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 48 B C A D E F G H I J L K M PO

49. 49 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 49 B CA D E F G H I J L K M PO

50. 50 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 50 B CA D E F G H I J L K M PO

51. 51 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 51 B CA D F G H I J L K M !? E PO

52. 52 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 52 B C A D E F G H I J L K M !? PO

53. 53 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 53 B C A D E F G H I J L K M PO

54. 54 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 54 B A D E F G H I J L K M C PO

55. 55 Next Dev Done Backlog 3 2 In production :o) Ongoing Scenario 2 – Deployment problem Henrik Kniberg 55 B AD E F G H I J L K M C PO

56. 56 Example: Portfolio mgmt Henrik Kniberg 56

57. 57 Portfolio-level kanban board Henrik Kniberg Next Develop Bingo 1 FLOW Avg lead time: weeks 12 Releas e Done 2 Conce pt Playabl e Feature s Polish 3 Zork Pac man Pong Donkey Kong Mine sweeper Dugout Duck hunt Game Team 1 Game Team 2 Game Team 3 Solitaire

58. 58 Game teams Henrik Kniberg 58 Game team 1 Current game: Pac Man Game team 2 Current game: Pong Game team 2 Current game: Donkey Kong

59. 59 Example: Connecting Scrum & Kanban Henrik Kniberg 59

60. 60 Operations / support team Connecting Scrum & Kanban Henrik Kniberg 60 Feature team 1 Feature team 2 Feature team 2 Feature team 1 Feature team 2 Feature team 2 Scrum Operations / support team Feature team 1 Feature team 2 Feature team 2 Scrum Kanban Step 1Step 2Step 3

61. 61 Wrapup Henrik Kniberg 61

62. 62 Agile is ”simple” Henrik Kniberg A few books on Agile...... and Scrum...... and XP... and maybe some on DSDM and Crystal and Lean while you’re at it.

63. 63 Agile is Simple but Hard Henrik Kniberg 63... like chess... and piano playing

64. 64 Agile & Lean fit well together Customer value Visual management Build quality in Continuous improvement Empirical approach Empowerment Henrik Kniberg 64

65. 65 Essential skills needed regardless of process Henrik Kniberg 65 Software craftsmanship Splitting the system into useful pieces Retrospectives As a buyer I want to save my shopping cart so that I can continue shopping later

66. 66 Don’t be dogmatic Henrik Kniberg 66 Go away! Don’t talk to us! We’re in a sprint. Come back in 3 weeks. Though Shalt Limit WIP

67. 67 Know your Goal Focus on Why Agile/Lean are tools, not goals Tools don’t fail or succeed. People do. There is no such thing as a good or bad tool. Only good or bad decisions about when, where, how, and why to use which tool. Don’t limit yourself to one tool Mix & match Compare for understanding, not judgement. Experiment & enjoy the ride Don’t worry about getting it right from start. You won’t. The important thing isn’t your process. The important thing is your process for improving your process. Henrik Kniberg 67 Take-away points

68. 68 Perfection is a direction, not a place Henrik Kniberg