| Similar experience here at our dojo. Mob programming is great : we've had people working effectively in languages they don't know. And so we've had product guys sit with us and practically transformed them into programmers, able to fulfill their vision. Issues get identified much faster, and design decisions are quickly discussed and tried. Because we're able to get feedback on why we're developping, it's much easier to make the right choice for the right situation. Test code is much more relevant, and it's much more expressive, too. > - Biggest personality wins. I'd worry that whoever had the largest personality would drive everything, leading to people being disengaged. Honestly, we didn't run into this problem at all, maybe because it's a dojo setting. Since we're used to mobbing, people will usually be extra careful about it. When there are many people, setting up a fishbowl is a good exercise to teach people to leave more room to others.
I've had deadlocks happen during pair programming, but in a mob, it's much rarer. Also faster experiment time leads to much more tries. > - Constantly bringing people up to speed. Maybe this is actually a good thing? Definitely a good thing. People asking question is a good predictor of hard-to-maintain code. |