Effect of Batch Size on Work Flow

© 2016 Alex Kanaan

Agile Games Night

Effect of Batch Size on Work Flow

Jul 20, 2016

About Me

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

© 2016 Alex Kanaan

Stay in Touch

[email protected]

http://www.alexkanaan.com

@AlexKanDu

https://www.linkedin.com/in/arkanaan

© 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

© 2016 Alex Kanaan

Learning ObjectivesStudy batch size impact on work flow

© 2016 Alex Kanaan

Game OverviewTwo 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

© 2016 Alex Kanaan

Recording Sprint Results

Managers Record

Time MeasuredBatch 11 x 20

Batch 22 x 10

Batch 34 x 5

Batch 420 x 1

Worker 1

Worker 2

Worker 3

Worker 4

FIRST BATCH

SYSTEM TOTAL

© 2016 Alex Kanaan

Role TasksWorkers • 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

© 2016 Alex Kanaan

Role TasksManagers • 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

© 2016 Alex Kanaan

Role TasksBatch 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

© 2016 Alex Kanaan

Role TasksSystem 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

© 2016 Alex Kanaan

Let’s Get Ready• Clear outer perimeter of table • Managers stand behind your workers • Everyone get your timers ready

© 2016 Alex Kanaan

Sprint 1

1 x 20

© 2016 Alex Kanaan

Sprint 2

2 x 10

© 2016 Alex Kanaan

Sprint 3

4 x 5

© 2016 Alex Kanaan

Sprint 4

20 x 1

© 2016 Alex Kanaan

Flipchart HuddleWhat did We Learn?

Who had an Aha moment? When?

© 2016 Alex Kanaan

Flipchart Huddle

Individual Workers Performance?Total System Performance

© 2016 Alex Kanaan

Flipchart HuddleSo if no one’s individual time changed, how come we cut overall time?

© 2016 Alex Kanaan

Flipchart HuddleSo 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!

© 2016 Alex Kanaan

Flipchart HuddleCompare to An Agile Team

© 2016 Alex Kanaan

Flipchart HuddleSTORY SIZE MATTERS!

© 2016 Alex Kanaan

Flipchart HuddleFirst Batch Measurements

© 2016 Alex Kanaan

Flipchart HuddleFirst Batch Measurements = First Value to Market

© 2016 Alex Kanaan

Flipchart HuddleFirst Batch Measurements = First Value to Market = Used in LEAN AGILE

© 2016 Alex Kanaan

Flipchart HuddleWhat about feedback within the sprint?

© 2016 Alex Kanaan

Flipchart HuddleReducing story size improves flow of stories throughout the team and improves throughput.

© 2016 Alex Kanaan

BACK TO SEATS

© 2016 Alex Kanaan

Learning Exercises -1What is the impact of working on large stories that take up the sprint? (5 mins)

© 2016 Alex Kanaan

Learning Exercises-1What does the Sprint Burnup chart look like?

© 2016 Alex Kanaan

Learning Exercises-1What does the Sprint Burnup chart look like?

✗ ✓

© 2016 Alex Kanaan

Learning Exercises-1Risk of missing sprint target is much higher with large stories

© 2016 Alex Kanaan

Learning Exercises-2What’s an ideal story size to aim for? (2 mins)

© 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?

© 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

© 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

© 2016 Alex Kanaan

Understanding effect of Introducing WIP limits

When: WED AUG 17 Where: KAPLAN

Next Steps

© 2016 Alex Kanaan

Thank You• Sheridan for venue and healthy snacks • ALL of you • Slides posted on my slideshare acount • Stay in Touch!

© 2016 Alex Kanaan

THANK YOU!

40

Questions?