Each phase of Microsoft Dynamics Sure Step methodology is equally important in an implementation project. You could argue that analysis is the most important, or that design is the most important, or that operation is less important. I’ll paraphrase Scott Adams here and ask: how one phase can be more important if each of them is completely necessary? Well, except for Diagnostic phase.
Have you considered a career in Microsoft Dynamics? Yes, I know, many of you have are most likely already happily employed by a Microsoft partner company specializing in Microsoft Dynamics solutions. Good.
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.
[Updated]
I had to update this post a little bit, see below for the details, but the killer feature had to go 🙁
[/Updated]
Remeber that tool “Automated Version Management” that I published here and on Mibuso five months ago? It has just got an update: version 2.0.
I’ve just got a call for help from a partner, about their customer who has decided to move from basic inventory management to full-scale warehouse management system. The question was how to post the opening balances for existing inventory quantities in flat locations to warehouse-managed ones.
I thought this might deserve a quick blog post, you can never know when someone else would want to do the same thing.