Is Your Project Out of Control?

Out of Control Checklist
This list is the same as the previous list, but presented in chronological order.
Specification Complete Milestone
Especially important when coding is about to begin are:

• Lack of a shared, crisp vision.
• Lack of a customer focus.
• Moving from technology to product.
• Biting off too much.
• Too many dependencies.
• Under-detailed specifications.
• Over-detailed specifications.
• Not managing product performance and size.
• Lack of shipping experience.
• Lack of technical skills.
• Inadequate staffing.
• The reality distortion field.
• Failing to use milestones and milestone reviews.
• Non-bottom-up scheduling.
• Magic dates.
• Schedule not detailed enough.
• Lots of items assigned to TBH or TBD.
• Failure to schedule busy work.

Coding or Code Complete Milestone
During coding, at coding milestones, or at code complete, watch for:

• Focus on extracurricular activities.
• The vision in the wind.
• Biting off too much.
• Too many dependencies.
• Not managing product performance and size.
• Lack of ownership.
• Hostages.
• Lack of communication among dependents.
• Inordinate emphasis on secrecy.
• Status reports that blame others.
• Failing to use milestones and milestone reviews.
• Lack of regular (daily) builds.
• Failing to eat your own dog food.
• Failing to track metrics.
• Handling process.
• Schedule churn.
• Lots of items assigned to TBH or TBD.
• Two sets of books.
• Buffer misuse.
• “We’ll make it up.”
• “Fix—if there is time.”

Beta or Release Candidate Milestone
In the final stages, be especially sensitive to:

• Lack of a customer focus.
• Focus on the wrong things.
• Not managing product performance and size.
• Hostages.
• Lack of communication among dependents.
• Failing to track metrics.
• Handling process.
• “Fix—if there is time.”

Refer : http://www2.slac.stanford.edu/comp/winnt/system-administration/outofcontrol.doc