Effect of Batch Size on Work Flow
- 1. © 2016 Alex Kanaan
Agile Games Night
Effect of Batch Size on Work Flow
Jul 20, 2016
- 3. Connect With Me
More about Me http://www.alexkanaan.com
Read My Blog http://www.alexkanaan.com/#latestnews
Contact Me http://www.alexkanaan.com/#contact
Follow my Tweets @AlexKanDu
Connect on LinkedIn https://www.linkedin.com/in/arkanaan
- 4. © 2016 Alex Kanaan
Stay in Touch
alex@alexkanaan.com
http://www.alexkanaan.com
@AlexKanDu
https://www.linkedin.com/in/arkanaan
- 5. © 2016 Alex Kanaan
Introduction
• Waterfall teams are used to working on larger
sets of features for a longer period of time
• This means delivering those features are
usually delivered in larger, less frequent
releases
• A key feature of lean processes is quickly
flowing value to the consumer
• Adjusting sizes of objects within a process
enhances the flow
5
- 6. © 2016 Alex Kanaan
Learning Objectives
Study batch size impact on work flow
- 7. © 2016 Alex Kanaan
Game Overview
Two teams
Four Roles in Each Team
• Worker
• Manager
• Batch Timer
• System Timer
Game is Four Sprints; each is a different batch sizes
You will time and record performance for each sprint
- 8. © 2016 Alex Kanaan
Recording Sprint Results
Managers Record
Time Measured
Batch 1
1 x 20
Batch 2
2 x 10
Batch 3
4 x 5
Batch 4
20 x 1
Worker 1
Worker 2
Worker 3
Worker 4
FIRST BATCH
SYSTEM TOTAL
- 9. © 2016 Alex Kanaan
Role Tasks
Workers
• Select and use one hand
only
• Do work by flipping coins
one-by-one in the batch
• Pass batch to next person
• Always pass in same
direction
- 10. © 2016 Alex Kanaan
Role Tasks
Managers
• Stand behind your worker
• Ensure same hand is used
at all times
• Start timer when worker
receives batch of coins
• Stop timer when worker
hands-off batch of coins
• Record your workers time on
flip chart
- 11. © 2016 Alex Kanaan
Role Tasks
Batch Timer (first batch only)
• Start timer when first worker
in team turns over first coin
of the first batch of coins
• Stop timer when last worker
in team turns over last coin
in the FIRST batch of coins
• Record your teams first
batch time on flip chart
- 12. © 2016 Alex Kanaan
Role Tasks
System Timer (All Batches)
• Start timer when first worker
in team turns over first coin of
the first batch of coins
• Stop timer when last worker in
team turns over last coin in
the LAST batch of coins
• Record your teams system
time on flip chart
- 13. © 2016 Alex Kanaan
Let’s Get Ready
• Clear outer perimeter of table
• Managers stand behind your workers
• Everyone get your timers ready
- 18. © 2016 Alex Kanaan
Flipchart Huddle
What did We Learn?
Who had an Aha moment? When?
- 19. © 2016 Alex Kanaan
Flipchart Huddle
Individual Workers Performance?Total System Performance
- 20. © 2016 Alex Kanaan
Flipchart Huddle
So if no one’s individual time changed, how
come we cut overall time?
- 21. © 2016 Alex Kanaan
Flipchart Huddle
So if no one’s individual time changed, how
come we cut overall time?
ANSWER: Smaller batches allowed for better flow of
work through the team!
- 22. © 2016 Alex Kanaan
Flipchart Huddle
Compare to An Agile Team
- 23. © 2016 Alex Kanaan
Flipchart Huddle
STORY SIZE MATTERS!
- 24. © 2016 Alex Kanaan
Flipchart Huddle
First Batch Measurements
- 25. © 2016 Alex Kanaan
Flipchart Huddle
First Batch Measurements
=
First Value to Market
- 26. © 2016 Alex Kanaan
Flipchart Huddle
First Batch Measurements
=
First Value to Market
=
Used in LEAN AGILE
- 27. © 2016 Alex Kanaan
Flipchart Huddle
What about feedback within the sprint?
- 28. © 2016 Alex Kanaan
Flipchart Huddle
Reducing story size improves flow of stories
throughout the team and improves throughput.
- 30. © 2016 Alex Kanaan
Learning Exercises -1
What is the impact of working on large stories
that take up the sprint? (5 mins)
- 31. © 2016 Alex Kanaan
Learning Exercises-1
What does the Sprint Burnup chart look like?
- 32. © 2016 Alex Kanaan
Learning Exercises-1
What does the Sprint Burnup chart look like?
✗ ✓
- 33. © 2016 Alex Kanaan
Learning Exercises-1
Risk of missing sprint target is much higher
with large stories
- 34. © 2016 Alex Kanaan
Learning Exercises-2
What’s an ideal story size to aim for? (2 mins)
- 35. © 2016 Alex Kanaan
Learning Exercises-3
• What have you
learnt from the
penny game?
• What will you do
differently for your
team now that you
know this?
- 36. © 2016 Alex Kanaan
Your Take Home
• Processes with smaller batches provide faster
value to customer
• Reducing story size improves flow of stories
and throughput
• With faster feedback loops your defects are
caught and fixed sooner so quality is improved
• Risk of missing sprint targets is lower with
smaller stories
- 37. © 2016 Alex Kanaan
Do’s
• Break work into small manageable batches
• Break all stories – 1 to 3 days per story
• Limit size 5 stories and start with them
• Open one thing at a time & finish it!
• Stop Starting Start Finishing
• Introduce WIP limits to improve work flow
37
- 38. © 2016 Alex Kanaan
Understanding effect of Introducing WIP limits
When: WED AUG 17
Where: KAPLAN
Next Steps
- 39. © 2016 Alex Kanaan
Thank You
• Sheridan for venue and healthy snacks
• ALL of you
• Slides posted on my slideshare acount
• Stay in Touch!
Editor's Notes
- Happy Team Pictures
- Who here comes from a waterfall background?
How long does it take to get your requirements typically? They re pretty comprehensive and once you have them you usually deliver everything in one release, possibly two or three if you are using an incremental approach
Contrast that with Agile processes – we allow customer to set features as long as they get them in before sprints start and make changes to the backlog –
Now enter Lean – some the characteristics of lean are eliminating waste and increasing flow –
What does increase flow mean? Get the value to the customer faster
So how do we do that? How do we enhance the flow? If you look at the individual objects in a system, if you adjust the sizes within a process, you adjust the flow – we shall see how this is done
- -__-M. Q M. AA. q A/B you improved by factor of xxxx that’s AWESOME
- How was total system time for team 1, team 2? How did it change as batch size changed, awesome!
Lets look at individual workers performance – how did it change? Can we say it stayed same for the sake of argument?
OK so if it changed the same, how come you cut overall time?
- Point to last person – how did u feel in sprint 1? How did you feel in Sprint 4? Why?
So let me ask same question again – while no one’s time went DOWN, how did the team’s overall performance go UP??
- ANSWER you had better workflow because the batches were smaller
- Which team has a better flow of work
The one with larger stories, or the one with smaller stories?
That’s right
- What was your first batch like?? You went from xxx to YYY
Why do u think I asked you to measure the first batch time??
What is the significance of the measurement of the first batch?
- Improtant because its when we start delviering benefits that can translate to $$$$$
this means faster delivery of first value to customer
Where is this important? ? Hint I talked about it in the intro
NEXT SLIDE
- In Lean Agile!
In a lean process, not only is initial work delivered faster to a customer, the entire development processes is faster BECAUSE THE FLOW IS BETTER
- FASTER
if you have any defects u will FIND AND FIX them much sooner
QUALITY goes up
- Penny Game works because we reduce the batch size
- Penny Game works because we reduce the batch size
- People towards end of process have nothing to do until end of cycle
Pressure is on those towards end not to let down
Who are these people in an Agile team? Punish the testers!!
Burnup chart = POINTS delivered during a sprint =the rate at which work is being addressed
What does this tell us?
- What does this tell us ABOUT THE RISK OF MEETING YOUR SPRINT GOALS?
- How far do you break down the stories?
Steer away from as little as possible
- Break work into small manageable batches
Break all stories – 1 to 3 days per story, if a story is bigger then break it down using vertical slices
Open 1-2 things at a time so you can remain focused
Improve work flow to reduce or avoid the gridlock at the end
- Happy Team Pictures