H T L E V E L • Only got a few hours? Working with an unfamiliar team? You may want to mob program a code kata. • Already working as a team? A non-obvious, challenging task that requires the whole team to participate will show the strengths of mob programming.
S • Mixed teams are a strength, not a problem. • Mob programming equalises differing skill levels swiftly. • Editor key shortcuts, domain knowledge, programming language constructs and concepts, and previously stumbled- upon pitfalls are all shared.
driver works at the keyboard. • The rest of the team act as navigators. • After a ﬁxed amount of time, e.g. 10-15 min, the driver is replaced. • Repeat until everyone has acted as a driver, then repeat from the top.
• Each cycle is an excellent opportunity to perform various micro-experiments. • Not used to test-driven development? Try it! • Avoid using the mouse. • Try the strong pairing style of not letting the driver write anything unless instructed to do so by a navigator.
• Found something that works really well given your context? Perhaps learnt something unexpected about you and your team? • Write about it on your development blog. • The Twitter hashtag is #MobProgramming. • Encourage others to experiment too!