FREE

BOOK*

*Subject to someone actually writing

the book in the first place**
**I wouldn’t hold my breath
About Me Dan Brown
Why am I here:
I’m passionate about helping organisations
transform, to improve service delivery to
customers, and improve the working lives of
people within the organisation.
I happen to be a coach, teacher and speaker,
focusing on Lean Kanban and Agile.
I’m sometimes called KanbanDan
I’m an Accredited Kanban Trainer, ICAgile Instructor
and Certified Professional in Agile Coaching and
Agile Facilitation. I am a Scrum.Org PSM(I&II), PSK
practitioner and lapsed Scrum Alliance CSM
and CSP.
About You..
•Have you taken your brave
pills today?
•If you know the answer,
buzz in
•If you don’t know the
answer buzz in and be a
chancer
• Your rejection target for
today
Lets break some
things first
Scrum is great for
cross functional team
delivery
But not so great for large
multi-team service delivery flows…
A group of great individuals
doesn’t magically make a
great team
Otherwise Manchester City would
win the league every year, right?
A group of great teams
doesn’t magically make
great value flow
Lets look at it: Single scrum team

Need

Customer Single Scrum Team

Deployable
Product Increment
Sequential Team “Value Flow”

Need

Scrum Team 1 Scrum Team 2 Non-Scrum Team

Non-Scrum Team Non-Scrum Team Scrum Team 1

Customer

Deployable
Product Increment
(Eventually)
(If we’re lucky)
Lets put it all back
together again
Get your buzzing hands ready…
What is Scrum for?
“Jeff Sutherland and I developed
the Scrum process for complex
product development.”
– Ken Schwaber www.controlchaos.com
The Scrum Guide says:
“Scrum is a
…framework for
developing, delivering, and
sustaining complex products”
What about Kanban?
“Kanban is something you
introduce to evolve an existing
process”
– David J Anderson on LinkedIn.com
The Kanban guide* says:
“Kanban is a method for defining,
managing, and improving services
that deliver knowledge work”
*Essential Kanban Condensed– Carmichael and Anderson
http://leankanban.com/guide/ - free ebook version
Scrum
is a delivery method

Kanban
is an improvement method
Scrum
• Tells you how to deliver products
• Says you should improve
Kanban
• Assumes you’re delivering already
• Tells you how to improve
Scrum
• Tells you 1 way to drive a car
Kanban
• Shows you how to improve your
driving
Scrum
• Tells you how to play the game
Kanban
• Tells you how to improve your
game
Kanban is not agile
• …but it is the alternative path to agility
• Using Kanban to improve your services will lead you to
become (more) agile
• Benefits include:
• High optionality of work selected
• Fast delivery of work items encouraged
• Focus on units of value delivery rather than units of work
• Customer focus as a principle, and customer engagement needed
• Inspect and adapt, but with more obvious things to inspect
• Validated learning
Kanban and Scrum?

• Kanban and Scrum aren't even of the same genus:

• Scrum is a Team framework
software to deliver
development lifecycleProduct
methodology;
• Kanban is a management
Service delivery improvement
method method
that prescribes the
structure to evolve existing workflow processes.

• You can apply Kanban to an instance of Scrum.

 First steps to a w i d e r world…
• Kanban allows decoupling of cadences, so you can deliver fortnightly,
Plan, Commit and Replenish weekly, or daily, or twice a week, or
whatever works best for you.
• Be as agile as you want to be.
• This is the first step I have seen most often in
“Using Kanban On Top Of Scrum” teams
• Wow that is a mouthful, perhaps we can merge the two words together
in a portmanteau, ‘Jedward’ style:
• Let’s say it together, 1, 2, 3…
KANBUM!
OK, maybe not
There is no Scrumban methodology
• Sorry, there just isn’t, despite the CVs I’ve seen it
on
• You cannot hybrid Scrum and Kanban in the
same way you cannot hybrid XP and Scrum in to
XScrumP
• Scrum is a framework to build in and around
• If you use C# in a Scrum team we don’t call it
Sc#rum do we?
Second steps to a wider world…
• Kanban usually spreads (infects) upstream and downstream… we
start looking at a wider picture beyond just their own team.
• Everyone involved starts looking right to left across the whole org.
• Soup to Nuts for service delivery
• We start to care about the things the customer cares about, instead of
the org chart…
• Just like those end to end single scrum team orgs do.
 Big organisation processes

Need

Scrum Team 1 Scrum Team 2 Non-Scrum Team

Non-Scrum Team Non-Scrum Team Scrum Team 1

Customer

Deployable
What if this is your team?
Product Increment
(Eventually)

Lets make it more visual

 StarbanDan’s Coffee Shop
Lets use an example we all know to
Customer
explain a real Kanban Board
Customer Selected 2 Order 2
Payment 10 Brew Coffee 4 Prep Milk 2 Lid 3
Cup Sleeve 3 Call Out 4 Done
Queue Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Name
 StarbanDan’s Coffee Shop
Lets use an example we all know to
Customer
explain a real Kanban Board WIP Limits
Customer Selected 2 Order 2
Payment 10 Brew Coffee 4 Prep Milk 2 Lid 3
Cup Sleeve 3 Call Out 4 Done
Queue Doing Done Doing Done Doing Done Doing Done Doing Done Doing Done Name

Buffer Lanes
Big organisation processes

Need

Scrum Team 1 Scrum Team 2 Non-Scrum Team

Non-Scrum Team Non-Scrum Team Scrum Team 1

Customer

Deployable
What if this is your team?
Product Increment
(Eventually)
 Big organisation processes
Scrum Team 1 Scrum Team 2 Non-Scrum Team Scrum Team 1 Non-Scrum Team Non-Scrum Team Improved
Live Service
Customer
Options ∞ Selected 4 Discovery 4 Build 4
Deployment 4 SIT Test 2
UAT 3
Pre-prod 3 Deployment4 Done
∞
Doing Done Doing Done Doing Done Doing Done Doing Done Testing
Doing Done
 Improved
Live Service
Customer
Options ∞ Selected 4 Discovery 4 Build 4
Deployment 4 SIT Test 2
UAT 3
Pre-prod 3 Deployment4 Done
∞
Doing Done Doing Done Doing Done Doing Done Doing Done Testing
Doing Done
Concluding thoughts Cohen brothers style
Concluding thoughts Group feedback style
• Visualising the whole system helps us see where it
needs to be improved
• Limiting WIP shifts us from focusing on working on our
bit to delivering he most value we can
• They bring the pain forward and improve our delivery
• PSK is a good step forward for us all to work together
• Kanban classes can help you learn how to improve
• Metrics make all this even better…