One nice thing with mobbing is that it’s easy to have meetings. The team wanted a retrospective yesterday, so we all moved to a room and had a quick meeting. We used a Lean Coffee format last time. This time we tried a Sail-Anchor format (what blows us forwards, what drags us back). There were two main groups for each. What pushes us forwards: Behaviour in the mob. Good coding practices. Socialising more has increased morale. The mob in general seems more cohesive. Dropping in and out has become more normal. For coding practices, we’ve been focussing on small well-defined tasks, small simple functions, and writing good Scenarios. What drags us back: Behaviour in the mob. The codebase and tools. The unhelpful behaviour was a mix of not following good mob practices, criticising code written by others, and meandering off course down rabbit holes in the code. To help, we agreed that we’d check if a rabbit hole was worth following at the end of each turn d...
While mobbing can be great for progressing relentlessly through tasks, it can be quite intense. And we found that we weren’t taking breaks, or checking our email, or doing anything other than mobbing. So we made two changes. The first was to take tea-breaks. At first, we tried adding in a tea-break to our rotation timer, but it came round too quickly, so we ignored it... So I bought an hour-glass. When we start, we set it off. And when the sands run out, it’s time for tea :-) And the second idea was to stop early. Rather than keep going till lunch, we stop half an hour early, to give everyone a chance to catch up with anything that needs doing. It seems to be working so far!