Scrumban takes elements of Scrum and Kanban to manage product development workflows. Kanban uses visual boards and work-in-progress limits to maximize flow and control workflow bottlenecks. It was inspired by the Toyota Production System and aims to continuously improve processes. This presentation discusses using Kanban to manage activities outside of Scrum's core development cycles, like backlog management and testing. Kanban complements Scrum by providing visibility and control over the entire value stream. The speaker recommends Scrumban for long development cycles, heavy R&D, and support/helpdesk teams.
2. About Me
• Agile Coach, Certified Scrum Practitioner, Certified Scrum Product Owner
• 13 years experience leading R&D organizations (including VP R&D) focusing on
System-level software and products.
• Focusing on:
– Change Management and effective Agile Transitions
– Enterprise-scale Agility
– Lean, Kanban, and agility for special circumstances
– Using Retrospectives and Systems Thinking to identify and address deep issues with
how product development organizations execute
– Agile Management
• Find me on:
– yuval@agilesparks.com
– @yuvalyeret
– http://www.linkedin.com/in/yuvalyeret
3. TO DO IN PROGRESS DONE
Why do we
need to look
outside
Scrum?
What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
7. Backlog Pains
• How do we manage the flow around the backlog?
• How do we ensure we have enough analysis/stories
ready for development?
• How do we avoid preparing/analysing too many
stories for the development to work on (Waste)?
• We love the visibility Scrum provides us for the
development lifecycle. How do we extend it to the
backlog / story elaboration phases?
8. TO DO IN PROGRESS DONE
Why do we
need to look
outside
Scrum?What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
10. Toyota Production System
“The two pillars of the Toyota
production system are
just-in-time and
automation with a human
touch, or autonomation.
The tool used to operate
the system is kanban.”
Taiichi Ohno, Toyota Production
System (adopted 1962)
11. TO DO IN PROGRESS DONE
Scrum Task Board
Elad Inbar
Mushon Inbar
Elad
Mushon
12. TO DO IN PROGRESS DONE
What’s the problem?
http://moduscooperandi.com
Elad Inbar
Mushon
Inbar
Elad
Mushon
Mushon
Mushon
Inbar
Inbar
Mushon
Elad
Inbar Inbar
Inbar
13. TO DO IN PROGRESS DONE
Late-binding, Multi-tasking limits
http://moduscooperandi.com
Inbar
Elad
Mushon
Inbar
Mushon
Elad
14. TO DO READY (2) IN PROGRESS (5) DONE
Voila! Kanban!
http://moduscooperandi.comhttp://moduscooperandi.com
15. TO DO READY (2) IN PROGRESS (5) DONE
Pull
http://moduscooperandi.comhttp://moduscooperandi.com
Mushon
Mushon
16. TO DO READY (2) SPECIFY (2) EXECUTE (3) DONE
Workflow
18. Teamwork
• Enhances Teamwork
– Team focus on goals that add
value not individual tasks
• Encourages Swarming
http://www.flickr.com/photos/markop/2523825358/
19. When Blocked…
• Lower priority work…
– Spikes
– Analysis
• Production Capability
Improvement work…
– Tool Automation
– Refactoring
– Personal Development
– Innovation
• But NOT
– Anything which will create
work downstream
NOTE: This doesn’t mean you should ONLY “sharpen the knife” when Blocked!!!
21. TO DO IN PROGRESS
(1)
DONE
Why do we
need to look
outside
Scrum?
What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
22.
23. • Easier transition for Scrum teams/organizations
– Step by step migration – see
http://leansoftwareengineering.com/ksse/scrum-ban/
27. TO DO IN PROGRESS
(1)
DONE
Why do we
need to look
outside
Scrum?
What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
28. When should I use Kanban?
Extend Scrum to the whole
value stream
– Upstream - Manage the
Backlog process - All the steps
preceding the actual
development sprints
– Downstream –
Manage system testing,
packaging,
deployment
29. When should I use Kanban?
• During hardening sprints
• For the support/helpdesk teams/activities
• For periods of heavy R&D
30. When should I use Kanban?
• Another angle to start your transition from
– Add visibility and WIP controls to current
workflow
– Inspect the constraints/bottelenecks
– Adapt the workflow, resources, processes – Scrum
It if it makes sense!
– Drive for maximum throughput and fastest time to
delivery
– Repeat
31. TO DO IN PROGRESS
(1)
DONE
Why do we
need to look
outside
Scrum?
What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
32. TO DO IN PROGRESS
(1)
DONE
Why do we
need to look
outside
Scrum?
What is
this
Kanban/
Scrumban
?
How does it
complement
Scrum?
When
would we
want to use
it?
Detailed
comparison
between
Scrum and
Kanban
How to
manage
in Kanban
using TOC
Kanban
Release
Planning
Kanban and
Commitment/
Velocity
Flow of
business
value using
Kanban
Scrumban
implementation
Details
Advanced
Kanban
Concepts
33. TO DO IN PROGRESS
(1)
DONE
Detailed
comparison
between
Scrum and
Kanban
How to
manage
in Kanban
using TOC
Kanban
Release
Planning
Kanban and
Commitment/
Velocity
Flow of
business
value using
Kanban
Scrumban
implementation
Details
Advanced
Kanban
Concepts