Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up
for free
Running Mob Programming - How we made our team x 4 faster!
Ikuo Suyama
August 07, 2019
Programming
0
1.5k
Running Mob Programming - How we made our team x 4 faster!
Agile2019 at D.C. Lightning Talk
Running Mob Programming, How we made our team x 4 faster!
Ikuo Suyama
August 07, 2019
Tweet
Share
More Decks by Ikuo Suyama
See All by Ikuo Suyama
martin_lover
15
5.2k
martin_lover
0
850
martin_lover
19
24k
martin_lover
1
1.6k
martin_lover
0
150
martin_lover
2
3.2k
martin_lover
1
600
martin_lover
0
270
martin_lover
0
110
Other Decks in Programming
See All in Programming
eller86
0
640
n1215
1
450
dhmegane
0
140
kulkarniankita09
0
260
bkuhlmann
5
690
bkuhlmann
2
320
yoshiken
1
220
mathetake
7
2.2k
hiro_y
1
450
syucream
4
1.4k
minodriven
34
25k
inoue2002
1
290
Featured
See All Featured
lara
172
9.7k
brettharned
93
3.1k
jakevdp
776
200k
holman
447
140k
geoffreycrofte
25
1k
3n
163
22k
iamctodd
22
2.2k
bryan
32
3.5k
lara
590
61k
bkeepers
PRO
54
4.3k
bryan
99
11k
jmmastey
10
700
Transcript
Running Mob Programming How we made our team x 4
faster
Ikuo Suyama @martin_lover_se ➔ From Tokyo, Japan ➔ ’LODEO’, CyberAgent
➔ Backend Engineer ➔ Apprentice Agile Coach
Mob Programming "Mob Programming A Whole Team Approach" Agile 2014,
Woody Zuill “On the same thing... At the same time... In the same place... On the same computer...
Our Mobbing Style
Our Mobbing Style ➔ Session ◆ 1 Session is 45
min ◆ Taking 5 - 10 min rest at each session ➔ Changing Driver frequently by timer ◆ Changing driver at 5 - 15 min ◆ All participants can be a driver at each session For keeping Concentration
Our Mobbing Style “for an idea to go from your
head into the computer, it MUST go through other's agreement. The driver can also join the discussion
Just following these rules, Our results x 2 faster than
ever!
X 2…?
X 4, wasn’t it…?
Yes, We SCALE our Mob.
Initial Approach: Scale-UP ➔ start from 3 people ➔ Increment
to 6 people...
Scale-UP: Problem Efficiency (1 / leadtime) Number of people Note:
This data is NOT accurate
Note: This data is NOT accurate ➔ It doesn’t scale
linearly ➔ Sweet spots is 3 - 4 people Scale-UP: Problem Low Resource Efficiency Resource Efficiency is getting worse
The Solution: Scale-OUT
Scale-OUT: Synced-Mob
Scale-OUT: Synced-Mob Keep the lines of communication open
2 mobs work together! Scale-OUT: Synced-Mob On the same thing...
At the same time... In the same place... But different tasks
Scale-OUT: Synced-Mob Reducing Sync point ➔ Mob Feature planning ◆
Independently Task Slicing ➔ Mob interface design & implementation ◆ Starting define interface with all
Scale-OUT: Synced-Mob X2 FASTER!! X2 FASTER!! Quite simple, but it
works well!!
If we got only 5 people…?
Like This…?
Oops! JOYFUL! EXHAUSTED…
Oops! JOYFUL! EXHAUSTED… Tend to Avoid…
Solution: Double-Linked Mob
Double-Linked Mob <This is HIGHLY EXPERIMENTAL!> Same effectivity as 3-3
synced mobs! ➔ Linking-Navigator ◆ 2 Mobs connect with navigator ◆ Rotate linking-navigator at each session ◆ Easy to found problems between each mobs
1/2 lead-time mob, X 2 parallel we got x 4
faster!
➔ Using Mob, we got x 2 faster ➔ To
achieve x 4 faster ◆ Scale-UP • Cause low-resource efficiency ◆ Scale-OUT • Synced-Mob • Double-Linked Mob <Experimental!> Conclusion
Twitter: @martin_lover_se Thank you for your kind attention!