In a post titled IT project failures, Charlie Bess makes an insightful comment about a subject that should be obvious, but is often overlooked:
Since the only reason the project exists is to achieve business benefits. Project managers need to have the business needs as the project objective. If it appears the project will not be done on time and meet the objectives - speak up, early and often. Bad news does not get better with age. Part of developing that understanding will be having useful business metrics, and those may not be easy to find.
Technologists sometimes forget that when a business invests in software, it is making a business decision. Beware projects that take on a life of their own, with key staff ignoring objective metrics of succes or failure such as ROI. This caution applies equally to executive project sponsors and to the folks working in the trenches.
Thank you, Charlie Bess, for the reminder.