What is Your Approach for Implementing Microsoft Dynamics?
Every Microsoft Dynamics prospect that I meet these days asks the question “What is your methodology for implementations?” Gone are the days when companies would simply license software based upon the feature set of the software and not a
sk about the methodology and plan to get the system live. Companies are moving in the right direction when they ask the “Methodology” question, but are they really asking the right question when they meet their partner for the first time?
A methodology tells you what you need to do in order to manage a project from start to finish, describing and defining every project management task used in the project. If all companies and projects were created equal then a one size fits all approach might make sense. However any method is only as good as its application and that is where the role of the project manager becomes so important. Companies should insist on more than a textbook answer to the methodology question since a good project manager will know better than to take a cookie cutter approach to an implementation and will craft the appropriate method from the available project management tools to deliver the best outcome with minimum risk.
Instead of using a one size fits all methodology to implement Dynamics, a project manager should approach the project with the idea of crafting a unique methodology that delivers the Dynamics solution based upon the project’s unique goals and objectives. The project manager, with assistance from the business analyst and project team, should review the project’s demands along with the project’s goals and objectives to determine the project management tasks and techniques that can best help deliver true business value to the project’s stakeholders.
Perhaps the prospect should really be asking the partner “What is your approach to creating a methodology for my implementation?”