Why Some Dynamics Projects Fail, and How the Problems Can Be Anticipated Early On

When a Microsoft Dynamics installation-whether a new one or an upgrade-- fails, some 60% of the time the problem can be attributed to implementation problems, according to Aditya Mohan, a Microsoft director of productivity management. 

There are ways to head off such costly failures early on, Mohan told a session at Convergence 2011. One recent addition to Microsoft's tools designed to increase the percentage of successes is the Microsoft Dynamics Project Readiness Assessment. It is an outgrowth of Microsoft's Sure Step methodology, intended to help guide Dynamics implementation projects.

According to Microsoft, the key to project success involves a number of steps taken very early in the process. These include:

• Gaining executive commitment for leadership and to reinforce to others the seriousness of the project;
• Serious budgeting in advance of the project;
• Establishing a strong project management team
• Learning to manage modifications so as to fit budgetary realities.

The Project Readiness Assessment includes a focus on requirements of partners as well. As Mohan of Microsoft explained it at the Convergence session, "You should have the partner's feet to the fire, but the partner should have control."

But the key is to have user representatives complete a set of 25 questions, which are then used to provide a rating as to the readiness of the company to begin a Dynamics project.