It’s probably not too far an exaggeration to say that it’s changes that kill projects. Whether it’s because requirements were incorrectly specified at the start, or the business environment has changed – moving the goalposts mid-way through the game can really screw things up.
So it’s no suprise that most methodologies have a lot to say on the subject of capturing and managing requests for change (RFCs). And a well-run project environment will have some kind of formal process for dealing with requests as they arise.
Some of the problems
But often a project environment won’t have a process – and what processes exist are actually irrelevant in day-to-day use. Do any of these situations sound familiar?
Read the rest of this entry »
