scrum-ban: time-boxes and flow

21
SCRUM-ban: Time-boxes and flow Tang, Tze Chin Agile Manager

Upload: tzetang

Post on 05-Dec-2014

389 views

Category:

Business


0 download

DESCRIPTION

SCRUM has become the de-facto agile project management methodology for many software projects. I've been using SCRUM with my team for about two years, but we've hit a performance plateau. In this presentation, I share some techniques and experience in combining Kanban with SCRUM to manage flow of work and improve team productivity in identifying and managing bottlenecks.

TRANSCRIPT

Page 1: Scrum-ban: Time-boxes and flow

SCRUM-ban: Time-boxes and flow

Tang, Tze ChinAgile Manager

Page 2: Scrum-ban: Time-boxes and flow

What is SCRUM?

Page 3: Scrum-ban: Time-boxes and flow

What is Kanban?• Controlling Flow of Work

• Kanban is all around us

Inputs

Outputs

Constraint/Bottleneck

Page 4: Scrum-ban: Time-boxes and flow

Let’s do an exercise…

Page 5: Scrum-ban: Time-boxes and flow

Making Aeroplanes(Push)1. Stations can make and

complete their task as fast as they want and push to the next station

2. QA station at the end will verify if airplane build to specification and approve or reject

Page 6: Scrum-ban: Time-boxes and flow

Making Aeroplanes(Push)1. Stations can make and

complete their task as fast as they want and push to the next station

2. QA station at the end will verify if airplane build to specification and approve or reject

Page 7: Scrum-ban: Time-boxes and flow

Making Aeroplanes(Push)1. Stations can make and

complete their task as fast as they want and push to the next station

2. QA station at the end will verify if airplane build to specification and approve or reject

Page 8: Scrum-ban: Time-boxes and flow

Making Aeroplanes(Pull)WIP

limit:1

WIPlimit:1

WIPlimit:1

WIPlimit:1

1. A station can start work only if there is a unit work unit in the preceding kanban

2. A station can play a work unit only if the succeeding kanban is empty

3. QA will approve or reject accordingly

Page 9: Scrum-ban: Time-boxes and flow

Typical OutcomeTo manufacture 20 airplanes Push Run Pull Run

Total Time 8:40 9:15

Time per airplane 26.0s 27.8s

Rejected/Passed 7/13 2/18

Time per shippable airplane 40.0s 30.8s

Page 10: Scrum-ban: Time-boxes and flow

Push vs Pull – Flow

Page 11: Scrum-ban: Time-boxes and flow

Inventory is Waste

Page 12: Scrum-ban: Time-boxes and flow

Identify and Manage Constraints

Page 13: Scrum-ban: Time-boxes and flow

Measure value created, not effort expended

Page 14: Scrum-ban: Time-boxes and flow

Eliminate Waste

Page 15: Scrum-ban: Time-boxes and flow

How to Kanban• Set up a taskboard

• Define work steps

• Create kanbans before each step – Work in Progress

• Define WIP limits

Page 16: Scrum-ban: Time-boxes and flow

SCRUM + Kanban = Why?• You’re a SCRUM environment

• Agile adoption not yet mature

• Management ‘fear’ of change

• Below the radar…

Page 17: Scrum-ban: Time-boxes and flow

Kanban in a SCRUM Iteration• Still run a SCRUM, but with a bigger taskboard

Page 18: Scrum-ban: Time-boxes and flow

Revised Taskboard

Blocked Prioritized Backlog

Prepare for Dev(4)

Ready for Dev(4) In Dev (8)

Page 19: Scrum-ban: Time-boxes and flow

What have I learnt?• Work stages and WIP limits reflect team organization and

values• I focus less on burn-down and more on burn-up and

cumulative flow

• Team more focused on delivering value, not starting new work

Page 20: Scrum-ban: Time-boxes and flow

Further Reading

Page 21: Scrum-ban: Time-boxes and flow

• Email: [email protected]• LinkedIn: www.linkedin.com/in/tzetang• Twitter: @tzetang• Agile Malaysia: www.facebook.com/groups/agile.malaysia

• Team more focused on delivering value, not starting new work