Embed Size (px)
DESCRIPTION
Kanban is a way to implement a Lean process, focused on flow, time to market, and waste removal. Understand the Lean principles behind Kanban, its relation to Agile/Scrum, and how the two can complement each other into Scrumban. Understand where Kanban should be considered.
Citation preview
Scrumban
Taking Scrum outside it’s comfort zone
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:– [email protected] – @yuvalyeret – http://www.linkedin.com/in/yuvalyeret
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?
Enterprise Project Development
Scrum’s Comfort Zone
Scrum
Event-driven
R&D
What is event-driven?• Helpdesk/Support activities
(driven by cases opened by customers, under SLA)
What is event-driven?• Hardening/Packaging phases
(driven by defects found in testing)
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?
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?
Kanban
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)
TO DO IN PROGRESS DONE
Scrum Task Board
Elad Inbar
Mushon Inbar
Elad
Mushon
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
TO DO IN PROGRESS DONE
Late-binding, Multi-tasking limits
http://moduscooperandi.com
Inbar
Elad
MushonInbar
Mushon
Elad
TO DO READY (2) IN PROGRESS (5) DONE
Voila! Kanban!
http://moduscooperandi.com http://moduscooperandi.com
Inbar
Elad
Mushon
Elad
TO DO READY (2) IN PROGRESS (5) DONE
Pull
http://moduscooperandi.com http://moduscooperandi.com
Inbar
Elad
Elad
MushonMushon
TO DO READY (2) SPECIFY (2) EXECUTE (3) DONE
Workflow
Inbar
Elad
Mushon
Inbar
Throughput
Work in Progress
Throughput
Teamwork
• Enhances Teamwork– Team focus on goals that add
value not individual tasks• Encourages Swarming
http://www.flickr.com/photos/markop/2523825358/
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!!!
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?
• Easier transition for Scrum teams/organizations– Step by step migration – see
http://leansoftwareengineering.com/ksse/scrum-ban/
Team Cadence/Heartbeat
Board reset
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?
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
When should I use Kanban?
• During hardening sprints• For the support/helpdesk teams/activities• For periods of heavy R&D
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
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?
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
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
Kanban Deep Dive
…
Coming Soon
…
References and Material
Scrumban - http://leansoftwareengineering.com/ksse/scrum-ban/
[email protected] http://availagility.wordpress.com .aaron@sanders name :// . . /http aaron sanders name
:// . . / / /http groups yahoo com group kanbandev
