| Ron Ruble 2006-08-27, 6:58 pm |
| davout wrote:
> Are there any articles/web sites that can suggest best practices for how a
> business can provide continuity and investment protection on agile projects?
>
> I'm thinking here of situations like....
> * What happens if our two main developers are hit by a bus? How can we know
> what the code represents?
In addition to Philip's comment on tests, if you are pair
programming and rotate developers around, then the secondary
staff move on with it. Remember, the code is supposed to belong
to the team, not the individual developer who happened to work on
it first.
Just don't book -all- your developers on the same flight to a
conference. *
> * We are going to transfer most of the developers on this project to another
> assignment in 4 months time, and replace them with a completely new team.
> How can we manage the transition?
Have the new folks pair with the existing folks, at least part
time, before the existing folks roll off.
* I once worked with a company producing an app that modeled some
very complicated business rules. All the developers who had
worked with the business staff took a trip to Ireland together at
one point. I mentioned this as a risk, and pointed out that
planes do sometimes crash; the PM turned very white and scheduled
time for additional documentation and knowledge transition to
other staff before the trip.
|