3 Years of Mob Programming
What it is and lessons learn't so far
Getting the best of everyone
into all the code
using Mob Programming
My first experience
About Me
Dev Lead @ MYOB
|
|
Outline
What is Mob Programming...
The roles and mechanics
Common questions
Things we have learnt
What is Mob Programming?
Roles in Mob Programming...
- Driver Typist
- Navigator Rest of mob
The typist
- Listen to what the mob is asking you to do
- Translate it to code (don't prematurely challenge)
- Work with an incomplete understanding for short periods of time
The rest of the mob
- Help discover the next logical step
- Talk at appropriate levels of abstraction
- Always try to increase levels of understanding in the mob
What to do when only one person knows
What to do when nobody knows
Default to collaboration
Is this cost effective?
How do you measure productivity?
|
|
What destroys productivity?
|
|
Multitasking
Before Mob Programming
When Mob Programming
Defects
Code Cruft
Technical debt
A question of quality
On our own we get the best and worst of us
As a mob we get the best of everyone into ALL the code
Isn't this just expensive pair programming?
Ideal size for problem solving is ±4 people
Increased flow
Waiting for information
If we are not able to answer our own questions, then we are missing someone in the mob
Physical setup matters
What's next?