Scrum, Kanban, and DevOps Sitting on a Tree... (Learn how to leverage Kanban & Scrum together and how to fit DevOps into the picture)Should we use Scrum? Should we use Kanban? Where does DevOps fit into the picture? The best agile teams already know they don’t need to choose. Scrum teams improve when they start to look at flow inside and outside their sprints. Kanban teams improve when they have a disciplined cadence, and effective Product Ownership and Scrum Mastership. DevOps really is mainly about doing Agile the right way. In this session, we will look at a core definition of Scrum, Kanban & DevOps, do some myth-busting as well as identify the quite significant common ground between Scrum, Kanban and DevOps. We will then look at practical ways like the Kanban-based Sprint Backlog, Flow-based Daily Scrum, Visualizing aging work, Flow-based Sprint Planning - which bring some Kanban flow into your Scrum. We will look at how to bring Scrum roles/events/artifacts into your Kanban. We will look at ways to wrap Scrum with a Kanban Flow system that looks upstream/downstream and at the higher level picture of a DevOps Culture/Process. You’ll leave with a better understanding of how Scrum, Kanban, and DevOps relate to each other and with some ideas for experiments to try when back at work.

1. Scrum, Kanban, and DevOps Sitting in aTree…
Learn how to leverage Scrum & Kanban together +
how to fit DevOps into the picture
YuvalYeret
AgileTrainer/Coach | Scrum.org PST | SAFe SPCT
AgileSparks
Yuval@AgileSparks.com
@YuvalYeret 11 May 2018

2. 2

3. 3
We’re privileged – We can mix colors!

4. 4
HelpingTeams Get More from Scrum
Scrum
Kanban
Professional
Scrum
Done
Right

5. Kanban reinforces
Waterfall
We do Kanban
because we can't
plan out for an
entire Sprint
Kanban is Linear
Kanban is all about
manufacturing,
software isn't
manufacturing
Where are the
PEOPLE in Kanban?
Our ScrumTeam
has evolved to
become a
Kanban team
Kanban doesn't
encourage creating
effective teams
Scrum is
revolutionary;
Kanban is
evolutionary
Scrum is for
complex work,
Kanban is for
simple work
Scrum is for
product teams;
Kanban is for
service teams
You can only
get so far with
evolutionary
change
5
Truth or Myth?

6. 6
Kanban in the Scrum Context
• Like the Scrum Guide; a simple set of rules to help
ScrumTeams get the maximum benefit from
Kanban practices.

7. 7
Defining and visualizing the “Workflow” -These Are PBI’s

8. 8 Defining and visualizing the “Workflow” - What Workflow Do the PBI’s
FlowThrough?
Sprint
Backlog
Design Development Testing
Done
Doing Ready Doing Ready Doing Ready
Is this Kanban?
Is ItWaterfall?

9. Sprint
Backlog
Design Development Testing
Done
Doing Ready Doing Ready Doing Ready
9
It’s not Kanban without Limiting work-in-progress (WIP)
4 7 4

10. Sprint
Backlog
Design Development Testing
Done
Doing Ready Doing Ready Doing Ready
10
It’s not Kanban without Limiting work-in-progress (WIP) + Pull
4 7 4

11. Next
Discovery Build
Ready
Building Deploy
Ready
Validate
Release
Ready
Stage Production
Doing Complete Doing Complete
WIP
11
Actively managing the items in progress – Using Some key flow metrics
5 4 3 4 2 2
CycleTime
Throughput
Work Item Aging

12. 1.Defining and visualizing the “Workflow”
2.Limiting work-in-progress (WIP)
3.Actively managing the items in progress
4.Inspecting and adapting your “Workflow”
12
Kanban in a Scrum Context – Core Practices
AND REDUCING!

13. Changes you can try in your Scrum teams
13

14. Use a Kanban Board as your Sprint Backlog
14

15. • Backlog item types
• Workflow
• Visualization policies
• WIP limits
• Pull/prioritization policies
• Service Level Expectations (SLE’s)
• Definition of “Done”
15
Go beyond “Definition of Done” to “Definition of Workflow”

16. Flow-based Sprint Planning
• You don’t need to plan out the entire Sprint
• You can begin unplanned work part way through the Sprint
(Leverage the Sprint Goal)
• Work can flow across Sprint boundaries
• Use throughput rather than story points/velocity
16

17. 17
Planning based onThroughput

18. • Work the board right to left
(Flow/Pull mode)
• What happened to me yesterday?
• What is going to happen to me
today?
• Is there any impediment to my flow?
18
Daily Scrum - Focus on the flow of work –Tell the story from the PBI’s
perspective
So yesterday…
And Today…
Right-to-Left Daily Scrum Flow

19. Work Item Age / Fighting Zombies
19

20. Work Item Aging Chart – Manage Service Level Expectations (SLEs)
https://www.actionableagile.com/analytics-demo/

21. Use Cycle time to figure out Service Level Expectations

22. Scrum Guide Relationship
E V E N T
Flow-Based Sprint Retrospective
22
• Adds a more quantifiable metrics aspect to the typical
qualitative Sprint Retrospective
» CycleTimes Scatterplot
» Cumulative Flow Diagram
» Blocked work and reasons
» Flow efficiency
» And many more…
• Review performance and compare to Service Level
Expectations (SLEs)
Sprint
Retrospective

23. Inspect & Adapt WIP/Flow using Cumulative Flow Diagrams (CFDs)
23

24. Inspect & Adapt Flow of specific items using CycleTime Scatterplot

25. Next
Discovery Build
Ready
Building Deploy
Ready
Validate
Release
Ready
Stage Production
Doing Complete Doing Complete
WIP
Using Flow Metrics in the Scrum Events
5 4 3 4 2 2
CycleTime
Throughput
Work Item Aging
Sprint Review
Sprint Planning
Daily Scrum
Sprint Retrospective

26. Scrum Guide Relationship
E V E N T
Sprint
26
• The Sprint is a planning, review, and retrospect
cadence
• Delivery can happen throughout the Sprint
The Sprint

27. Classic Approach to Potentially Releasable Increment
27
Product Backlog Develop &Test Release Activities Deployment
Production
Doing Ready Doing Ready Doing Ready Doing Ready
O
P
Q
R
S
T
U
V
…
K
L
M
N
C
D
B E
I
A
F
H
G
J
Sprint2
Sprint3
Sprint1
Continuous
Integration

28. Small Batch Continuous Flow Increments
28
To Do Planning Deveop &Test Delivery Deployment Production
/ Done
Doing Doing Complete Doing Complete Doing Complete
Auto
Automated
Agile
Continuous
Integration
Powered by strong automation
Frequent Feature Delivery
Predictable,
Repeatable,
Non-Event
S
T
U
V
Q
R
O
P
B
C
L
I G
J
H U
F

29. All together now - Scrum, DevOps and Kanban …
29
Learn more about Scrum & DevOps -
https://www.scrum.org/resources/convergence-scrum-and-
devops

30. Kanban – Not just for the Sprint…
0
Definition of Done:
• Asdcasdc
• Asdcasdca
• sdcasdca
• Asdca
sdc
• Asdca
sdca
• sdcas
dca
• Asdcasdc
• Asdcasdca
• sdcasdca
• Asdcasdc
• Asdcasdca
• sdcasdca

31. Scrum.org Blog
June 21, 2017
https://www.scrum.org/resources/blog/kan
ban-primer-scrum-teams
31
Suggested Reading
“A Kanban Primer for Scrum
Teams” (Porter,Yeret)
4 Key Flow Metrics
• ”Scrum and Kanban Stronger
Together” (Steve Porter)
Scrum.org Blog
June 21, 2017
https://www.scrum.org/resources/blog/scr
um-and-kanban-stronger-together
Scrum.org Blog
May 10, 2018
https://www.scrum.org/resources/blog/4-
key-flow-metrics-and-how-use-them-
scrums-events

32. Professional Scrum with Kanban –
HelpingTeams Get More from Scrum
Scrum
Kanban
Professional
Scrum
Done
Right
Find me at:
YuvalYeret, Scrum.org PST, PSK Steward
Yuval@AgileSparks.com
@YuvalYeret
https://www.agilesparks.com/psk