Jason's spot on on this one....and what works for one team doesn't often work for others. Hell, sometimes that's the case for individuals (some individuals are

Jason's spot on on this one....and what works for one team doesn't often work for others. Hell, sometimes that's the case for individuals (some individuals are not meant for pair programming where they might excel at code reviews instead). Also, OP mentioned something re: "minimize future modifications to already developed parts". Be aware of the technical debt you're incurring _as_ you develop it. We used to have regular sprints specifically to pay down the debt (one out of every 4 for example).