Promiscuous pairing

2005-10-05T21:39:00+00:00

Via the Agile Toolkit Podcast I discovered the article Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience by Arlo Belshee. It’s been a while since I’ve read such an interesting article!

Arlo describes how Silver Platter have experimented with different approaches to pair programming and task ownership/distribution. And most of their findings are not what you expect, and often they contradict commonly held truths. Some of them are:

assigning tasks to the least qualified worked better long term than assigning to the most qualified or randomly
team ownership of the tasks (team accountability) worked better than individual ownership (individual accountability)
task grabbing (pull) worked better than assignment (push)
swapping pairs each 90 minutes was most productive
for time between swaps of one hour to a day it was more productive if the one who had been with the task the longest switches task than if one stayed with a task until its completion

Go read the whole article now!

Oh, and that they use C++ makes it even more interesting!

Jason Fried on work process

2005-07-16T21:45:00+00:00

Jason Fried in an interview with Tom Peters:

We’re not much into planning or writing a lot of things down that are concrete. My personal opinion is that every decision you make should be temporary. So when you start writing things down, you start putting signatures to things, and you start being locked into your past actions. You’re letting your past determine the future. So I prefer to just start designing and see where things go. Then you can make adjustments and tweaks, realizing that every decision you make and everything you do can be changed if you come up with something better. I think that’s the best way to design things.

It also lets you make decisions when you have the right information to make them. The traditional design process might include a lot of documentation of functional specifications, or lots of charts and diagrams, and a bunch of stuff that you compile before you begin designing. In reality, you can plan all you want, but by the time you start actually designing something, and using it in the real world, you start seeing patterns and things you never could’ve guessed before. If you’re locked into a plan, then you can’t change those things.

andthennothing.net: Tag agile

Promiscuous pairing

Jason Fried on work process