Top Banner
Kanban Integrating Lean Into Software Project Delivery
20

Introduction to Kanban

Jun 15, 2015

Download

Software

Dev9Com

Are you trying to introduce change into your organization, and feel like you’ve hit a brick wall? Do you want to move forward with Lean initiatives, but are not sure how to apply them “in the trenches”? Have you adopted Agile principles and practice Scrum, but find it limiting when dealing with multiple teams and/or cross-functional organizations?

Kanban is an increasingly popular system for introducing incremental, evolutionary process into an organization. Based on Lean principles, it offers a way to move beyond basic Scrum and improve process in a consistent, manageable fashion. Dev9 has helped clients transition to Kanban, and we would like to share our engagement experiences.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Introduction to Kanban

Kanban

Integrating Lean Into Software Project Delivery

Page 2: Introduction to Kanban

Why should I care• Improve current process (in

increments)• Reduce task switching• Detect bottlenecks• Predict instead of react• Priorities change rapidly

Page 4: Introduction to Kanban

What is Kanban1. Visualize workflow2. Limit work in progress3. Manage flow4. Make Policies explicit5. Feedback loops6. Evaluate improvement with models

Page 6: Introduction to Kanban

Story 1 Story 2Story 3 Story 4

Story 5Story 6

Story 7

Story 8

Story 9

Workflow Visualization

Workflow

Backlog Develop QA Deploy Done

Priority

Page 7: Introduction to Kanban

WIP Limits• Limit work in progress for each

activity• Reduce context switching• Expose bottlenecks– Upstream tasks – Drives pulling

• Forces addressing blocked items

Page 8: Introduction to Kanban

WIP Workflow

Story 1 Story 2Story 3 Story 4

Story 5Story 6

Story 7

Story 8

Story 9

Backlog Develop QA Deploy Done6 3 3 2

Story 10

Story 11

Page 9: Introduction to Kanban

Flow Management (Measure)

• Every work item timed per state– Outliers may expose problems with work

breakdown

• Measure lead and cycle time• Keep a cumulative flow diagram– See cycle time over project’s life– Predict based on trends

Page 10: Introduction to Kanban

Cumulative Flow Diagram

Story 1 Story 2Story 3 Story 4

Story 5Story 6

Story 7

Story 8

Story 9

Backlog Develop QA Deploy Done

7/31

/14

8/1/

14

8/2/

14

8/3/

14

8/4/

14

8/5/

14

8/6/

14

8/7/

14

8/8/

14

8/9/

14

8/10

/14

8/11

/14

8/12

/14

8/13

/14

8/14

/14

8/15

/14

8/16

/14

8/17

/14

8/18

/14

8/19

/14

8/20

/14

0

5

10

15

20

25

30

BacklogDevelopment2QADeployDone

Lead Time Cycle Time

WIP

Remain

Page 11: Introduction to Kanban

Explicit Process Policies• Start with existing policies • Definition of done• Visible• Explicit policies are a handhold for

change.• Leverage your tools

Page 12: Introduction to Kanban

Process Improvement• Hold retrospectives• Listen to the team• Watch the data• Don’t hesitate to adjust• Revert changes that don’t work

Page 13: Introduction to Kanban

Sample Policies

Develop Feature

• Code is reviewed by another developer

• Unit test coverage at 80%

• Design impacts documented

Test Feature

• Integration tests reviewed by other QA developer

• Test cases documented in test case managament tool.

• Feature reviewed with BA to ensure completeness.

Page 14: Introduction to Kanban

Incremental Improvement• Periodically review the process • Follow the data– Set goal and measurement– Data should determine success or failure

• Retrospectives should influence process

Page 15: Introduction to Kanban

Real world examples

PhotoBy Super touristCC BY

Page 16: Introduction to Kanban

Scrum Development

Page 17: Introduction to Kanban

Cross-func matrix enterprise team

Page 18: Introduction to Kanban

Cross-func evolved

Page 19: Introduction to Kanban

IT Operations

Page 20: Introduction to Kanban

Q&A

“Sometimes the questions are complicated and the answers

are simple.” ― Dr. Seuss