Most of you have heard the phrase that 90% of the manufacturing cost of a product is determined during product design. The same can be said about the program execution risk profile of IT-enabled transformations. The master statement of work (MSOW) established at the beginning of the program locks in 90% of the risk profile of the project. The system integrators have a full appreciation of the execution risks, while their clients tend to be newer to the game. Does it surprise anyone that system integrators are able to mitigate 90% of their own risk in the development of the SOW while their clients, more often than not, are unaware of the risks and issues they will encounter?
Read More from This Article: IDG Contributor Network: 5 mistakes to avoid when developing a SOW with Accenture, Deloitte, and IBM
Source: IT Strategy