Introduction to Software Kanban

Transcription

1 Introduction to Software Kanban Darian Rashid Agile Trainer & Coach 1

2 Topics Push vs. Pull Systems Introduction to Lean/Kanban Traditional Wastes in Lean Standard Development Taskboard Deriving a Kanban Board Scaling the Value Stream Daily Planning Information Radiators Kanban Must-Haves 2

3 Push vs. Pull Systems Product is pushed through the system by a schedule usually generated from an MRP system Ready or not here it comes P u s h Product is pulled through the system by a signal at the rate of customer demand P u l l Triggers and signals 3

4 Push vs. Pull Systems No restriction on releases to the line Controlled by upstream information Inherently make-to-order Make all we can just in case Resource gathering Approximation: Forecasts or schedules Demand dictated internally Large batches High inventories Waste Management by firefighting Restrictions Controlled by downstream information Inherently make-to-stock. Make what the customer orders Resource demand Usage: Actual consumption Demand dictated externally Small batches Low inventories Waste reduction Management by sight 4

5 Lean/Kanban Kanban ( 看 板 ): literally meaning "signboard" or "billboard More than just a sign, it represents the soul and the honor of a business -- like a family crest in the European tradition Build ONLY to today s demand and then STOP. DO NOT make more. Find something else to do until more parts were needed When more parts are needed because the current # of parts were below quota (due to sales, etc.), THEN build more Bottom line: don t produce anything until the customer asks for it (pull) and you have space to put the finished goods (WIP Cap) 5

6 Kanban Is About Being Lean 1. Respect people 2. See the whole 3. Build integrity in 4. Eliminate waste 5. Amplify learning 6. Decide as late as possible 7. Deliver as fast as possible 8. Empower the team - Lean Software Development: An Agile Toolkit Tom and Mary Poppendieck 6

7 Traditional Lean Wastes A Inventory Extra Motion Defects Waiting Waste Time Time Time Time Time B 7

8 Kanban in Product Development is A continuous flow development method that limits WIP and focuses on Just-in-time production 8

9 Development Taskboard STORY TODO DEVELOPMENT VERIFICATION DONE Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y xxxxxx Y Y Y Y Y 9

10 Development Taskboard 10

11 Development Taskboard 11

12 Development Taskboard Create Pull STORIES / MILESTONES TASKS TODO DEVELOPMENT VERIFICATION DONE Y Y Y IN PROG. COMPLETE IN PROG. COMPLETE Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y xxxxxx Y Y Y Y Y 12

13 Little's Law In Out Total Time WIP Exit Rate 1 6 / min 6 min. In Out Total Time WIP Exit Rate 1 14 / min 14 min. Fixed capacity + increased WIP = longer total times POed customers! 13

14 WIP Cap Establish a WIP cap to control lead time Cap is maintained by Exits which trigger Starts into the process Key to lead time reduction 14

15 WIP Cap Keep WIP caps to 1 task per person Keep Blocked WIP to 1 per person or less Keep tasks to less than 1 day (preferably 2 3 hours) Keep Optimum Total Time = 1 day Keep the Exit Rate to 1 / minimum If Exit rate is 2/day, what is the WIP Cap? 15

16 Development Taskboard Limit WIP STORIES / MILESTONES TASKS TODO DEVELOPMENT WIP CAP: 3 VERIFICATION WIP CAP: 2 DONE Y Y Y IN PROG. COMPLETE IN PROG. COMPLETE Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y xxxxxx Y Y Y Y Y 16

17 Whaddaya Do Now? STORIES / MILESTONES TASKS TODO DEVELOPMENT WIP CAP: 3 VERIFICATION WIP CAP: 2 DONE Y Y Y IN PROG. COMPLETE IN PROG. COMPLETE Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y xxxxxx Y Y Y Y Y 17

18 Scaling the Value Stream STORIES / MILESTONES TASKS TODO DEFINING WIP CAP: 3 DEPLOYMENT WIP CAP: 2 DONE IN PROG. COMPLETE IN PROG. COMPLETE Scale columns to accommodate all VA steps in the value stream 18

19 Scaling Parallel Tracks STORIES / MILESTONES TASKS TODO Y Y Y DEVELOPMENT WIP CAP: 3 IN PROG. Y COMPLETE Y Y Scale rows to accommodate all parallel tracks including People Teams Y Y Y Y Y Y Y Y Y xxxxxx Y Y Y Y Y 19

20 Scaling Flow and Flexibility STORIES / MILESTONES TASKS TODO DEVELOPMENT WIP CAP: 3 Y Y Y IN PROG. COMPLETE Y Y Y Y Y Y Y Y Cap Feature WIP over time Y Y Y Y 20

21 21

22 Kanban Boards 22

23 Daily Planning a.k.a. stand-up meetings NOT A STATUS MEETING Time for the meeting, everybody! THIS IS A PLANNING MEETING Time-boxed for 15 minutes All pigs must attend Only pigs may speak Should be at the same time and location everyday Set by the team Meetings are NOT for the ProcessMaster but for the team 23

24 Daily Planning Answer 3 questions: Are we on track? If so, how do we know? If not, why not? Fully transparent Any chicken who wants to know the status is welcome Chickens sit around the periphery Chickens may not cluck 24

25 Cumulative Flow Diagram Total Items Lead Time WIP Time 25

26 Cumulative Flow Diagram 26

27 More Information From a CFD 27

28 Burndown Charts Shows the amount of work remaining over time Y-axis shows the remaining number of work to be burned-down Hours for Sprint burndown charts Story points for release burndown charts X-axis shows time Days for Sprint Burndown charts Iterations for release burndown charts The plotted point represents the sum of work that isn t finished yet 28

29 Kanban Must-Haves 1. Pull rule is in-effect 2. Very few items in WIP. Use WIP Cap with this 3. Slice thinly 4. Very short total times (in order of 1-3 days) 5. Reduce or eliminate setup and changeover 6. Radiate information constantly 7. Continuous balancing. Use cross-training to help 8. Continuous improvement 29

30 Questions? 30