Scrum & Kanban; Can they play nice together?

Tampa Bay Symposium © Copyright 2011 The Braintrust Consulting Group. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of The Braintrust Consulting Group. Images copyright of their respective artist, 2011, used under license from Shutterstock.com.

Scrum & Kanban Can they play nice together?

Where do you stand
Stand And Choose A Side:
Right side Scrum
Left side Kanban

Dot voting
Objectives

Brian M. Rabon, CST, PMP
Brian M. Rabon, CST, PMP
President, The Braintrust Consulting Group
BS CS from Auburn University
MS EE from UAB
CSM, CSD, CSP, CST, PMP
14 years of software development experience
Agile coach, trainer, and consultant

The agile umbrella
Agile
Scrum
Extreme Programming (XP)
Kanban/Lean
Crystal
Feature Driven Development (FDD)
Many, many, more
The Agile Umbrella

Scrum
Scrum 49% Scrum/XP Hybrid 22.3% Version One “The State of Agile Development” 3 rd Annual Survey: 2008 XP 8% Lean 1.9% 2008

Scrum
Scrum 50% Scrum/XP Hybrid 24% Version One “The State of Agile Development” 4 th Annual Survey: 2009 XP 6% Lean 3% 2009

Scrum
Scrum 58% Scrum/XP Hybrid 17% Version One “The State of Agile Development” 5 th Annual Survey: 2010 XP 4% Lean 2% 2010

2008-2010
Version One “The State of Agile Development” 3 rd - 5 th Annual Survey: 2008- 2010 2008 2009 2010 Scrum 49% 50% 58% Kanban 1.9% 3% 2%

As a PMI Tampa Bay Symposium attendee, I want to know what Scrum and Kanban are, so that I recognize them when I see them.

Pair share
Pair Share
Turn to your neighbor and share
What is a M/methodology?

Capital “M” Methodology – “A Methodology is a general systems theory of how a whole class of thought-intensive work ought to be conducted. It comes in the form of a fat book that specifies in detail exactly what steps to take at any time, regardless of who’s doing the work, regardless of where or when.” Peopleware: Productive Projects and Teams, 2 nd Edition, by Tom DeMarco and Timothy Lister, Dorset House Publishing, New York, United States

Lowercase “m” methodology – “A methodology is a basic approach one takes to getting a job done. It doesn’t reside in a fat book, but rather inside the heads of the people carrying out the work.” Peopleware: Productive Projects and Teams, 2 nd Edition, by Tom DeMarco and Timothy Lister, Dorset House Publishing, New York, United States

Scrum terms
Kanban concepts Work In Progress Limits – a constraint on the amount of work allowed in a particular workflow status Value Stream – what it takes to bring a product or service to a customer Kaizen – continuous improvement (PDCA) Work Item Card – a single work item Scrum concepts Backlog item – a single work item Sprint - a 30 day time period, at the end of which “potentially shippable” product is produced Backlog – a prioritized list of work items Roadblock – a risk or issue that is impeding the team’s progress

History
History Of Scrum Developed by Ken Schwaber & Jeff Sutherland Presented at OOPSLA in 1995 First documented in Agile Software Development with Scrum (2001) Based on… The New New Product Development Game By: Takeuchi and Nonaka Harvard Business Review, Jan-Feb 1986

Scrum core process

History
History Of Kanban Popularized by David Anderson & Allan Shalloway Based on… Toyota Production System (TPS) Lean Documented in Kanban and Scrum (3/1/2010) Documented in Kanban (4/7/2010)

Lean
Quality Just-in-time Short lead time Kaizen Minimizing waste Kanban Based On Lean Principles http://www.agilejournal.com/articles/17-articles/1737-what-is-best-scrum-or-kanban

Pillars
Visualize the workflow Limit work in progress (WIP) Measure the lead time

Flow Input Queue Prod Stage Release Ready Test Build Ready Development Analysis In Progress In Progress Development Ready Done Done Visualize The Workflow Kanban , 1 st Edition, by David J. Anderson, Blue Hole Press, Sequim, United States

To Do (4) In Progress (3) Ready For Release (3) Done G A Limit Work In Progress (WIP) H I J E D C B F

Measure the lead time
Measure The Lead Time

Benefits
Benefits Kanban , 1 st Edition, by David J. Anderson, Blue Hole Press, Sequim, United States
Focus on quality
Reduce work-in-progress
Deliver often
Balance demand with throughput
Prioritize
Attack sources of variability to improve predictability

Emergent behavior
Emergent Behavior
Process uniquely tailored to each project/value stream
Decoupled cadences (or “Iterationless” development)
Work scheduled by (opportunity) cost of delay
Value optimized with classes of service
Risk managed with capacity allocation
Tolerance for process experimentation
Quantitative management
Viral spread (of Kanban) across the organization
Small teams merged for more liquid labor pools
Kanban , 1 st Edition, by David J. Anderson, Blue Hole Press, Sequim, United States

Scrum vs Kanban
Photo courtesy of Matt Cowell, Vice President of Software Engineering, Daxko VS.

Team Composition Team Product Owner Scrum Master Anyone Scrum Kanban

Cadence
Cadence
Scrum
Develop in Sprints
(generally 2 to 4 weeks)
Kanban
No timebox, continual flow

Scope
Scope
Scrum
Fixed scope within a sprint
Kanban
Work in progress limits

Sizing work
Scrum
Size the work to fit within the sprint
Kanban
Any size work can be accepted (with a preference to smaller size)
Sizing

Personal Kanban Personal Kanban

The sprint
Personal Kanban
Create your own Personal Kanban board
Brainstorm tasks
^ PLAY!

Beat the clock
Beat the clock! “ In 60 seconds write down 7 facts you have learned about Scrum and Kanban.”

As a PMI Tampa Bay Symposium attendee, I want to know the strengths and weaknesses of Scrum and Kanban, so that I better understand each approach.

Stand, stretch, and speak
Stand, Stretch, And Speak

Maybe have them help me do a SWOT analysis?
Positive Risk Negative Risk Strengths Weaknesses Opportunities Threats

Positive Risk Negative Risk Strengths Scrum | Kanban Weaknesses Opportunities Threats

Positive Risk Negative Risk Strengths Weaknesses Scrum | Kanban Opportunities Threats

Positive Risk Negative Risk Strengths Weaknesses Opportunities Scrum | Kanban Threats

Positive Risk Negative Risk Strengths Weaknesses Opportunities Threats Scrum | Kanban

As a PMI Tampa Bay Symposium attendee I want to know when to use Scrum and Kanban, so that I apply them appropriately at my workplace.

Shout out!
Shout Out! What types of projects are best suited for Agile?

Stacey Diagram
When to use Scrum
Strategic Management and Organisational Dynamics , 5 th Edition, by Ralph D. Stacey, Financial Times, Harlow, England Stacey diagram

Types Of Work
Types Of Work VS Defined process control - Simple Empirical process control - Complicated/complex

Cone of uncertainty

Chasm
http://en.wikipedia.org/wiki/File:Technology-Adoption-Lifecycle.png

Scrum vs Kanban
Photo courtesy of Matt Cowell, Vice President of Software Engineering, Daxko ?

Think and write
Takeaways Write down 1 or 2 actionable next steps from this workshop

Resources
Resources

Burning questions

Contact info
Questions And Resources
E-mail me:
- brian.rabon@your-pm-partner.com
Twitter
- @yourpmpartner
http://blog.your-pm-partner.com
http://resources.your-pm-partner.com

http://www.braintrustgroup.com	700
http://www.javiergarzas.com	211
http://www.your-pm-partner.com	170
http://pm.anchr.in	146
http://braintrust.dev	30
http://test.your-pm-partner.com	4
http://translate.googleusercontent.com	1
http://blog.yourpmpartner.com	1

Scrum & Kanban; Can they play nice together?

by The Braintrust Consulting Group

Accessibility

Categories

Upload Details

Usage Rights

8 Embeds 1,263

Statistics