2. Goal
âWalk away with some ideas of how
to use the principles and practices
from the various Agile approaches to
help you develop valuable products
in the best way possible for you.â
3. Reaching that goalâŠ
Level set on the term âagileâ
Flavors of âagileâ
Effective combinations
Points of friction
11. What does âagileâ mean to you?
You keep using that word. I
do not think it means what
you think it means.
12. What does âagileâ mean to your
company?
You heard
weâre going
Agile, right?
Great! More done
with less people in
half the time!
Iâll start shopping
for my second
private jet now!
13. Concept to Cash Deliver value to our
customers quickly
Maximize learning
and incorporate
feedback
14. Agile is not the thing.
Agile is a thing that helps
you get to the thing.
15. Scrum doesnât do anythingâŠ
âIn the end it doesnât matter what
names you use for your processesâŠ
âŠscrum offers individuals and
organizations the opportunity to
continuously improve the way they
work.â
- Tobias Mayer
Image used without permission.
Shhh! Donât tell Tobias!
16. Agile doesnât do anythingâŠ
âAgile wonât fix your problems.
It will tell you how screwed you are
a lot earlier.â
- Me
24. Extreme Programming (XP)
Similar process to Scrum
Focus on engineering practices
Time-boxed iterations for delivery
Encourages direct involvement of user
40. Core Principles of Kanban
Visualize the workflow
Make process policies explicit
Measure and manage flow
Limit work in progress
Continuous improvement
41. Visualize the workflow
Sprint Items To Do In Progress Done
Task Task
Task
Task Task Task TaskTask
Task Task
Task Task
User
Story
User
Story
User
Story
Unit of EffortUnit of Value
43. Visualize the workflow
Sprint Items To Do In Progress Done
UAT
QA
Test
Write
Code
UAT
Write
Code
QA
Test
User
Story
User
Story
User
Story
Parts of our process are
represented by the tasks
themselves.
Some parts of the process
are assumed and not
represented at all.
UAT
QA
Test
Write
Code
50. Measure and manage flow
Cycle Time10
days
2 days
6 days
2 days
âWhy is this taking
so much longer?â
51. Making idle work visible
2 days
4 days
2 days
.5 day .5 day 1 day
âWhy is completed dev
working sitting here idle?â
52. Measure and manage flow
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
53. Limit work in progress
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
User
Story
Flow
54. Flow inside the Sprint
Sprint
User Story A
Code Test Deploy
User Story B
Code Test Deploy
User Story C
Code Test Deploy
55. Flow inside the Sprint
Sprint
User Story A
Code Test Deploy
User Story B
Code Test Deploy
User Story C
Code Test Deploy
59. Scrum & Kanban
More granular visualization
More focus on managing flow
Limiting work in progress
Better metrics around flow
Data driven continuous improvement
81. Continuous flow process
âThe Kanban Method does not ask
you to change your process. It is
based on the concept that you
evolve your current process.â
- David Anderson
83. Evolving to continuous flow
Scrum
Get good at
managing
work in
small,
focused
batches.
XP
Get good at
delivering
high quality
code
quickly.
Kanban
Get good at
measuring
and
managing
flow of
work.
Lean
Get good at
optimizing
your entire
system and
your
people.
84. What do we lose?
Sprint
User Story A
Code Test Deploy
User Story B
Code Test Deploy
User Story C
Code Test Deploy
5 5 5
Velocity = 15
Cycle Time
85. What do we lose?
Sprint
Sprint
Planning
Review
Retro
Grooming
Grooming
Flow
Jidoka â stop the line
Heijunka â leveling, meet demand by reducing waste
Kaizen â continuous improvement
Takt time - the rate at which a finished product needs to be completed in order to meet customer demand.
Any see what is wrong with my list? It is not in the normal order (for a reason!)
Typical scrum board
Does not really map to the underlying process, it is hidden in the task cards partially
Focuses more on the flow of units of work than units of value (the top of the lean house)
Typical scrum board
Does not really map to the underlying process, it is hidden in the task cards partially
Focuses more on the flow of units of work than units of value (the top of the lean house)
Like definition of done in scrum, but specific for each step of the process
Limiting WIP does not require any new process/people/software/etc. You simply just have to agree to start it.