Kanban and DevOps

Kanban and DevOps
•  ¡
Limited WiP Society Meetup
August 2018

www.evogility.com.au @danploegdploeg@evogility.com.au
About me
Daniel Ploeg is an experienced leader in
Agile Software Delivery and Product
Development. Daniel helps organisations
unleash their own potential by facilitating
new and innovative ways of thinking and
working.
Accredited Kanban Trainer
Kanban Coaching Profesional

Origins of DevOps
Development Operations
Functional
•  New Features
Non-Functional
•  Uptime
•  Responsiveness

Origin of DevOps
Development Operations

Origins of DevOps

DevOps Today
3 Ways:
•  The Principles of Flow
•  The Principles of Feedback
•  The Principles of Continual
Learning & Experimentation
h"ps://www.amazon.com/DevOps-‐Handbook-‐World-‐Class-‐Reliability-‐OrganizaAons/dp/1942788002

Kanban – Evolutionary Change
•  Start with what you do now (respect current roles and
processes - initially)
•  Gain agreement to pursue improvement through
evolutionary change
•  Encourage acts of leadership at all levels

Kanban Practices
•  Visualise
•  Limit WiP
•  Manage Flow
•  Make Policies Explicit
•  Feedback Loops
•  Improve and Evolve

Kanban Practices
•  Visualise
•  Limit WiP
•  Manage Flow
•  Make Policies Explicit
•  Feedback Loops
•  Improve and Evolve
DevOps:
The

Principles
of
Flow

DevOps:
The

Principles
of

Feedback

DevOps:
The
Principles

ConAnual
Learning
&

ExperimentaAon

Getting Started
First understand – what’s the problem
Idea DoneDeployDevelopBacklogExploreApproved
Twice
a

year

6-‐9
months
3-‐6
months

3
months

6
weeks
Up
to
4

weeks

(Monthly

releases
)

Getting Started
Idea DoneDeployDevelopBacklogExploreApproved
Twice
a

year

6-‐9
months
3-‐6
months

3
months

6
weeks
Up
to
4

weeks

(Monthly

releases
)

Maybe DevOps isn’t appropriate yet
“See
the
Whole”

before
launching

into
a
DevOps

iniAaAve

Perhaps focus here first Fix this next
How
frequently

can

your
customers

“accept”
delivery?

Pipeline of work
Next Develop DoneTest2 2
Enablers

Pipeline
Automation
Arch Enabler
Projects

4
Show
the
whole

ﬂow

4
Deploy
4
Verify
8
Show
the
whole

ﬂow

Pipeline of work
Enablers

Pipeline
Automation
Arch Enabler
Projects

4
See
Diﬀerent

Work
Types

4
Allocate
capacity

to
the
types
via

WiP
Limits

Deploy
4
Verify
8
Allocate
capacity

to
the
types
via

WiP
Limits

Pipeline of work
Enablers

Pipeline
Automation
Arch Enabler
Projects

4
See
Diﬀerent

Work
Types

4
Non
funcAonal

acAviAes
are
ﬁrst

class
ciAzens

Deploy
4
Verify
8

Pipeline of work
Enablers

Pipeline
Automation
Arch Enabler
Projects

Deploy
4
Verify
8
AlternaAvely,

use
a
minimum

WiP
limit

3
8

Flow
•  Visualise your whole workflow – make it
visible to all
•  Make queues and bottlenecks visible –
focus improvements here
•  Limit WiP / batch size to improve flow
•  Use metrics to see problems and track
improvements

Flow
Next
Backlog
Develop Test Deploy Done4
5
3
3Ongoing Done DoneOngoing
Make
queues

and
bo"leneck

visible

LimiAng

WiP
enables

ﬂow

Blk
Make
queues

and

bo"lenecks
/

blockers
visible

Flow - Metrics
Problems
with
Flow

Improvements

showing
decrease

in
lead
Ame

Flow
•  How long would it take to deploy a
change to a single line of code?
•  How long to do it safely?
•  How much is that costing?

Feedback
•  Seeing problems – Kanban practice of
“Visualise”
•  “Stop the line” – build quality in
•  Many sources of feedback – eg Kanban
“Service Delivery Review”. Combine this
with other techniques such as A/B testing
to improve “fitness for purpose”

Feedback
Add telemetry alongside visual board
Respond
to

problems
as

they
occur

h"ps://www.ﬂickr.com/photos/xmodulo/24311604930

Feedback
“Stop the line” – pipeline failures should “block” work just like on the board
h"ps://docs.gocd.org/current/beta/comment_on_pipeline_run.html

Continual Learning &
Experimentation
•  Use data and the scientific method – “be
curious”
•  The Kanban “Operations Review” and
“Risk Review” can help larger,
organisation level learning

Risk Review
•  Try a Blocker clustering exercise – bring
data from visual board and telemetry
systems
Blk
Blk
Blk
Blk
BlkBlk
Blk
Blk
Blk
Blk
Blk
Blk
Blk
Blk
Build
broken
for
33
hours
last

month
due
to
ﬂakey
tests.

AcAon:
Stabilize
test

framework!

Operations Review
•  “System of Systems”
improvements
•  Bring data
•  Leaders take away
larger systemic
improvements

Kanban & DevOps
•  Kanban is the most natural fit for a
DevOps initiative!
•  DevOps improvements require many
incremental changes over a sustained
period of time – Kanban can help catalyze
and sustain the change
•  No silver bullets – you still have to do the
hard work!

Learning More
Kanban System Design
Private & Public Courses
www.evogility.com.au
Next Public Course: November
Register:
https://www.eventbrite.com.au/e/kanban-system-design-tickets-42805832397

Kanban and DevOps

More Related Content

What's hot (20)

Similar to Kanban and DevOps (20)

More from Daniel Ploeg (7)

Recently uploaded (20)

Kanban and DevOps