ERP project metrics that are seldom met…

All the metrics used to determine project performance and the quality of the implementers’ work, none comes close in importance to staying on budget and schedule. These metrics are seldom met because very few (if any) of those perfectly met milestones corresponded in the slightest degree to any of the buyer’s critical business requirements and expectations for some system. A book could be written about this, a very long book, full of seemingly endless examples. Nobody would dispute a word of it, many people would quote it, but it wouldn’t change anything in the end.

All that’s required to change this whole mode of doing business is to offer a seller and/or implementer a statement of work (SOW) developed by the company themselves that describes the system the buyer actually wants. But this can’t happen unless these requirements for user satisfaction are known and stated at the point of initial contact and reinforced in the contract that guarantees payment. No implementer, anywhere, will ever agree to accept such conditions after contracts have been signed. Sellers and/or implementation firms are in business to sell hours, and if they’re allowed – let alone required – to quote the hours necessary for actually meeting a buyer’s critical business expectations documented in a statement of work that describes in extreme detail how its business operates and works, most will jump at the chance.

Download our free E-Book; The Symptoms, Reasons, and Causes for ERP project failures from our web site: