Kanban Kickstart Geeknight. Jesper Boeg, Agile/Lean Coach, VP Trifork Agile Excellence Twitter: J_Boeg

Size: px

Start display at page:

Download "Kanban Kickstart Geeknight. Jesper Boeg, Agile/Lean Coach, VP Trifork Agile Excellence Twitter: J_Boeg"

Oscar Lucas
5 years ago
Views:

1 Kanban Kickstart Geeknight Jesper Boeg, Agile/Lean Coach, VP Trifork Agile Excellence Twitter: J_Boeg

2 Agenda Introduction + Advertisement (15 min.) A Couple of War Stories The 5 Principles of Kanban Real Life Experiences Break: Sandwich and Networking More Real Life Experiences Discussion Topics 2

3 What I Won t Cover Kanban s Origins Kanban principles In-depth A Detailed Comparison of Scrum vs. Kanban 3

4 GOTO; Cph Conference Cool Products, Technical Tracks, Architechture Agile Mærsk Case Study, Agile Games, David Snowden Lean Benjamin Mitchell, Don Reinertsen, (Jesper Boeg) Agile UX Chris Nodder, Janne Jul Jensen (Winner of 2 Danish App Awards) DevOps/Continuous Delivery Patrick Debois 4

5 Trifork A/S Agile Coaching and Training Scrum, Kanban, Lean, XP. Software development: Public, Mobile, Security and Finance Technical Training Mobile, Java,.Net. Conferences GOTO and QCon 5

6 Popular Agile Training 1 day in-house Kanban Introduction Kanban Kickstart 1 day Kanban Introduction, kickstart + follow up 1 day Scrum introduction Agile Review CSM, CSPO New: Kanban 2 day Training March 8-9 Copenhagen April week16 6

7 In general Who are we? Let me know if you have questions Please help me remember the break You Will Get the Slides 7

8 8 A COUPLE OF WAR STORIES

9 1: THE CLASSICAL KANBAN EXAMPLE, OPERATIONS 9

10 2: ORGANIZATIONAL RESISTANCE 10

11 11 3: SUBOPTIMIZATION

12 12 4: A MATURE AGILE TEAM

13 13 KANBAN PRINCIPLES

14 1. PRINCIPLE VISUALIZE WORKFLOW 14

15 Visualize Workflow Inbox specification Breakdown Development Code review Test locally Test on Staging Release Planned In progress Done 15

16 2. PRINCIPLE LIMIT WORK IN PROGRESS 16

17 17 WHAT IS WIP IN SOFTWARE?

18 Limit Work in Progress Inbox Specification Breakdown Development Code review Test locally Test on Staging Release Planned In progress Done WIP Limit = 2 WIP Limit = 3 18

19 Capacity Constrained System You can never overload a Kanban pull system! 19

20 3. PRINCIPLES: MAKE POLICIES EXPLICIT 20

21 Make Explicit Policies Visual Ready for Code Inbox Specification Development Development Test locally review Planned In progress Done In progr. Done In progr. Done In progr. Done Test on Staging 2 In progr. Done Release Released: -Remove tickets -Write end date -Review deploy Write Start Date Accept Criteria! Plan pairing Refactor TDD Cover: Unittest Int.. Test Code Coverage Depl. issue Tester and Product Owner need 10 min. preparation Only Core Functionality - Update CFD, Defect rate and Cycle time 21

22 4. PRINCIPLE MEASURE AND MANAGE FLOW 22

23 23 Cumulative Flow Diagrams

24 24

25 5. PRINCIPLE IDENTIFY IMPROVEMENT OPPORTUNITIES 25

26 WHEN USED RIGHT POLICIES AND METRICS WILL DRIVE CHANGE 26

27 Identify Improvements Inbox Specification Breakdown Development Code review Test locally Test on Staging Release (Every Tuesday) Planned In progress Done Plan pairing Remember: Unittest Int.. test Coverage Depl. issue Tester and PO need 10 min. preparation Only Core functionality 27

28 KANBAN IS LIKE GETTING A SHRINK FOR YOUR PROCESS - JAN OLOFSSON 28

29 Kanban Principles Overview 1. Visualize Workflow 2. Limit Work-In-Progress 3. Make Policies Explicit 4. Measure and Manage Flow 5. Identify Improvement Opportunities 29

30 30 REAL LIFE EXPERIENCES

31 31 FOCUSSING ON FLOW HELPS!

32 32

33 YOU WILL BECOME MORE AGILE 33

34 34 A DRIVER HELPS

35 YOU NEED BOTH THE WHY AND THE HOW 35

36 CHANGE MANAGEMENT IS STILL HARD 36

37 UNCOACHED INITIATIVES FAIL! 37

38 QUALITY FOCUS HELPS. BUT YOU NEED PATIENCE 38

39 39

40 DON T WORRY ABOUT A LACK OF FOCUS! 40

41 GETTING PEOPLE TO THINK ABOUT THE ENTIRE VALUE STREAM IS HARD! 41

42 42 Blocked Items

43 43 Don t Forget the Vision!

44 DON T WORRY ABOUT PEOPLE USING KANBAN AS AN EXCUSE TO REVERT TO FORMER PRACTICES 44

45 PEOPLE WILL COPY WHATEVER YOU SHOW THEM! 45

46 PLUG-IN AGILE STILL DOES NOT WORK! 46

47 Most Failures - fall into one of the following categories No management commitment No crisis Management wants it but does not live it No autonomy People focus only on the mechanics 47

48 48 DISCUSSIONS

Kanban One-Day Workshop

Kanban One-Day Workshop Copyright Net Objectives, Inc. All Rights Reserved 2 Copyright Net Objectives, Inc. All Rights Reserved 3 Lean for Executives Product Portfolio Management Business Product Owner