scrum-ban: time-boxes and flow
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
SCRUM-ban: Time-boxes and flow
Tang, Tze ChinAgile Manager
What is SCRUM?
What is Kanban?• Controlling Flow of Work
• Kanban is all around us
Inputs
Outputs
Constraint/Bottleneck
Let’s do an exercise…
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
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
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
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
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
Push vs Pull – Flow
Inventory is Waste
Identify and Manage Constraints
Measure value created, not effort expended
Eliminate Waste
How to Kanban• Set up a taskboard
• Define work steps
• Create kanbans before each step – Work in Progress
• Define WIP limits
SCRUM + Kanban = Why?• You’re a SCRUM environment
• Agile adoption not yet mature
• Management ‘fear’ of change
• Below the radar…
Kanban in a SCRUM Iteration• Still run a SCRUM, but with a bigger taskboard
Revised Taskboard
Blocked Prioritized Backlog
Prepare for Dev(4)
Ready for Dev(4) In Dev (8)
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
Further Reading
• 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