In this talk from the 2014 SQE Orlando Conference, Cory Foy details how a team can choose between Scrum and Kanban - by understanding that Kanban is a method for evolutionary change that sits inside of an existing process like Scrum or SAFe. He then details how we can use the properties of Kanban to improve our Scrum framework to resolve the pressures and forces of using it on a day to day basis. The talk was recorded by Cory and is available here: http://blog.coryfoy.com/2014/11/video-from-choosing-between-scrum-and-kanban-now-online/

1. Choosing Between
Scrum and Kanban
Cory Foy | @cory_foy |
foyc@coryfoy.com

2. Scrum
Kanban

3. Process
Method
Framework
Methodology
System

4. Process
Method
Framework
Methodology
System
A series of actions or
steps taken in order to
achieve a particular end

5. Process
Method
Framework
Methodology
System
A particular form of
procedure for
accomplishing or
approaching something

6. Process
Method
Framework
Methodology
System
A basic structure
underlying a system,
concept or text

7. Process
Method
Framework
Methodology
System
A system of methods used
in a particular area of
study or activity

8. Process
Method
Framework
Methodology
System
A set of principles or
procedures according to
which something is done

9. Refactoring
Test-Driven Development
Listening to Code
Framework
Inspect
and Adapt
Knowledge
Design
Patterns

10. Hedge Trimmer
Force Resolved By
Thick Bushes
Tall Bushes
Lots of Bushes
Sharp Blade
Long Reach Arm
Seat for Operator
Automated Blade

12. Framework
Inspect
and Adapt
Knowledge
Scrum

13. Scrum Forces
- Remote Team Members
- Coordinate Work Across Teams
- Dependencies with non-agile teams
- New work during sprint
- Stories overlapping sprints

15. “As long as the methodology is
being followed everyone feels safe,
because they are formally covered,
even in the absence of working
results. ”
–Gunther Verheyen
http://guntherverheyen.com/2013/03/21/scrum-framework-not-methodology/

16. Even In
The Absence
Of Working
Results

17. Scrum
is
People

18. Stand
Up
Roles Meetings
Scrum
Artifacts
Product
Owner
Scrum
Master
Team
Burn
Down
Product
Backlog
Sprint
Backlog
Sprint
Planning
Sprint
Demo

19. Rapid
Comms
Roles Meetings
Scrum
Artifacts
Product
Vision
Process
Vision
Delivery
Visual
of Delays
Key
Inventory
Goal
Focused
Plan
Inventory
Fast
Feedback

20. Process
Vision
Delivery
Product
Vision
Visual
of Delays
Key
Inventory
Goal
Inventory
Rapid
Comms
Fast
Feedback
Focused
Plan
Know What
We Need
Know How
We Work
Work In
Small
Chunks
Get
Frequent
Feedback

21. 4 Immutable Attributes of
Successful Projects
Know What
We Need
Know How
We Work
Work In
Small
Chunks
Get
Frequent
Feedback

22. Product
Owner
Scrum
Master
Product
Backlog
Burn
Down
Sprint
Backlog
Sprint
Demo
Sprint
Planning
Stand
Up
Know What
We Need
Know How
We Work
Work In
Small
Chunks
Get
Frequent
Feedback

23. Expect Well
Less
Well
Change
What we
wanted to
happen
What went
well
What didn’t
go so well
What we
want to
try

24. K A N B A N
A Method for Evolutionary Change
Management

25. 5 Core Properties of Kanban
Visualize
Workflow
Measure and
Manage Flow
Limit Work-in-
process
Make Process
Policies
Explicit
Use Models
for
Improvement

26. Visualize Workflow
Backlog WIP Done

27. Visualize Workflow
Story Points
“The Lemming”
Days in Sprint

28. Visualize Workflow
Backlog Analysis Dev Testing Done

29. Visualize Workflow
Backlog Analysis Dev Testing Done

30. Visualize Workflow
7 weeks of work
40 weeks to do the 7 weeks

31. Limit Work-In-Process
Little’s Law
L = λW
# In System =
Time * Throughput
Response Time =
Number In System / Throughput

32. Limit Work-In-Process

33. Limit Work-In-Process

34. Limit Work-In-Process
4
Backlog Analysis Dev Testing Done

35. Limit Work-In-Process
4
Backlog Analysis Dev Testing Done

36. Limit Work-In-Process
4
Ready
for
Test
BL Analysis Dev Testing Done

37. Limit Work-In-Process

38. Limit Work-In-Process
4
Ready
for
Test
BL Analysis Dev Testing Done

39. Measure and Manage Flow

40. Measure and Manage Flow

41. Measure and Manage Flow
4
Ready
for
Test
BL Analysis Dev Testing Done

42. Measure and Manage Flow
BL
Analysis
3
Ready
for
Test
Dev Testing Done
2
Write
Test

43. Expect Well
Less
Well
Change
What we
wanted to
happen
What went
well
What didn’t
go so well
What we
want to
try
Measure and Manage Flow

44. Make Process Policies Explicit

45. Make Process Policies Explicit
Standard
Scrum
Ascend
Standard Work
Standard Process
New Process
New Process
Inspect and Adapt
Inspect and Adapt
Acclimate

46. Use Models to Recognize Improvement
Theory of Constraints Deming
Complex Adaptive Systems

47. Framework
Inspect
and Adapt
Knowledge
Scrum
Visualize
Workflow
Measure and
Manage Flow
Limit Work-in-
process
Make Process
Policies
Explicit
Use Models
for
Improvement
Know What
We Need
Know How
We Work
Work In
Small
Chunks
Get
Frequent
Feedback
Kanban

48. Thanks!
@cory_foy | Cory Foy | foyc@coryfoy.com
http://www.coryfoy.com