Two, Four, Six, Eight, How do We Communicate?

November 12, 2009 Will Read

When I joined the project, we went from one pair, to two. Today, we’re three pairs, six people strong. But the communication paths now are far more numerous than the one pair days.

It seems like a one pair project has it easy when it comes to knowledge transfer. Of course what it gains in simplicity, it also lacks in variety. That aside, it’s really easy; the client talks to the pair, and only two units need to be on the same page, one client unit, one pair unit.

The growing pain is easily identifiable when jumping to two pairs. Now the two pairs may agree, but the client may be picturing something else. Or maybe only one pair went on the phone call on Tuesday, so the Thursday phone call is different for everyone because they don’t all have the same context.

But it isn’t that hard to put four people on a phone call and have everyone ask enough questions to be heard and to understand. At six, now we’re talking about a lengthy discussion. Coming to a democratic consensus also becomes exponentially harder, let alone getting unanimous support. That’s OK, it is the disagreement that makes us pause just long enough to do the right thing, but it also means someone gets left out.

Going from two to four, then to six also means that you can get more work done, a lot more. How will you feed them this work? With one pair you can easily go day-by-day with just a few story lead time. When you get to three pairs, and each pair is blocked on one story, waiting for a batch job on a second story, and looking at the backlog for a third, you can’t go too long before you find yourself in a full on planning meeting on a very regular basis. Suddenly, keeping the backlog in order and stories teed up to be worked on goes from something you do at the end of the day to a full time job.

What one pair can often accomplish inline with a client, two pairs can do with some structure, but three pairs need to have a sit down and a real opportunity to have open conversations. That is not say, “Three is bad, never go above two pairs.” I’d argue for quite the opposite in fact. Three pairs have helped us flesh out how we really work, brought more areas of improvement to light, and of course, delivered more business value than ever before.

The real point is to say, “Be ready.” Our client knew this from experience, but it can be a hard lesson for a budding start up. You can try to be the head of sales and a project manager of a team of eight, but you’ll soon find yourself likened to “butter spread over too much toast”. As you grow your development team, you can also be prepared to grow your resources dedicated to keeping that team informed, fed with stories to work on, and reviewing the one’s they’ve completed.

About the Author

Biography

More Content by Will Read
Previous
The Failure of <insert development methodology here>
The Failure of <insert development methodology here>

Developers need to do stuff that you will never ask them to do, and if they asked you if it was ok to do it...

Next
absolute dates make tests brittle
absolute dates make tests brittle

Yesterday I modified an old app to turn off a feature for records that were more than a certain number of d...

Enter curious. Exit smarter.

Learn More