To keep projects running smoothly, experienced project leaders/manager think ahead, and employ "preventative action" patterns to reduce or eliminate risk.
A well-executed preventative action reduces or eliminates the need for a Corrective Action. A poorly executed preventative action can backfire. Anti Patterns include instances of poorly thought-out or executed preventative actions.
A surprise project review is a good example of a risk to project stability that needs to be managed. First-time project leaders may react by "stopping the show" to prepare for the review; more experienced project leaders think ahead to how the review may destabilize the project, and may employ a number of preventative actions, including negotiating to contain the scope of the review.
Examples of preventative actions include
-- Dave Smith 11/1/95
How about the Double The Estimate pattern to deal with incurable programmer optimism. -- Blake Coverett
From my experiences, Double The Estimate can be a little dangerous. Recently, we had a �500 piece of work charged at �2000 due to two people applying this pattern! The client was appalled, and it was basically unfair. I think a better pattern would be Question The Estimate, where the PM asks the developer if they have included design time, talk time, testing time and meeting time in their estimate. Even better, educate the eager developer in software estimation techniques?! -- Tobin Harris (20-May-2001)
Preventative? What's wrong with Preventive? -- Sitaram Chamarty (10-Jan-2002) (sitaram@dimensional.com)
See original on c2.com 