My last two posts have been a detour from my regular themes, into something that might remind you of human resources. I’ve explained what Microsoft Dynamics consultant does, and how it looks through phases of Sure Step implementation, and I promised to conclude this journey with explaining what I believe to be the 5 most important qualities every great Microsoft Dynamics application consultant must posses. So, here you go.
I wonder what people do with Google (or any other search engine for that matter) results past page two, or three. Or ten.
The other day a visitor came to this blog by googling this question: What does a Microsoft Dynamics consultant do? Two things I don’t understand: first, how far in the search results did they have to go—my blog most certainly didn’t land on first ten pages; and second, did they find here on my blog what they were looking for?
I decided to improve both.
Methodology is a tough topic. There are good methodologies, there are bad methodologies, there are good methodologies gone bad. Methodology is not a silver bullet, it won’t just make any problems disappear, and is hardly ever the single source of success or failure. But a methodology can be a major contributor to success. I could put it this way: you stand much better chances of success if you apply a methodology, then if you don’t. With something as critical as an implementation of business software, methodology is a key success factor. According to Jim Johnson of Standish Group, it’s number nine on their ten identified most important success factors.