Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Running Mob Programming - How we made our team ...

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

More Decks by Ikuo Suyama

Other Decks in Programming

Transcript

  1. 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...
  2. 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
  3. 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
  4. 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
  5. 2 mobs work together! Scale-OUT: Synced-Mob On the same thing...

    At the same time... In the same place... But different tasks
  6. Scale-OUT: Synced-Mob Reducing Sync point ➔ Mob Feature planning ◆

    Independently Task Slicing ➔ Mob interface design & implementation ◆ Starting define interface with all
  7. 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
  8. ➔ 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