January 2009

Implementing a new Microsoft Dynamics solution doesn’t merely introduce a new piece of software into your environment. Yes, the software is an important part, you need to deploy it successfully, configure it as necessary, probably even customize it and change the business logic under the hood.

I’ll never forget my first NAV project. I was helping a customer migrate data from their old COBOL-based application, and was spending most of my time with a mid-aged lady who at first fascinated me with her mastery of their old application. That was until I found out she actually had no clue whatsoever about what she was really doing.

When I started blogging about Microsoft Dynamics NAV back in 2007 it was because there were not too many blogs on the topic at the time. There were a few notable ones, and that was it. If you wanted to track them all, it was a piece of a cake.

One of the major tasks I decided to undertake here on this blog in 2009 was to create a comprehensive Microsoft Dynamics NAV Functionality Catalog . When you are making a decision to implement any large scale business management or ERP system, it can take dozens of presentations to learn about the…

(A short, almost pointless rant about PMBOK vs. Sure Step nonsense) Once, while preparing an important RFP response, a partner told me they don’t use Sure Step because they use PMI methodology . This made my toenails curl up—when people tell me they are using PMI methodology , they in fact tell me they are using no methodology at all.

(Three compelling reasons to reshape your business processes, not your software) Has your computer ever crashed while you were doing something important, causing you to lose all your work? A natural first reaction to this situation is frustration: your work is gone, your effort went in vain, you’ll…

Every so often I get an inquiry about regulatory compliance of Microsoft Dynamics NAV. How well does it support IAS requirements? Does it conform to Sarbanes-Oxley (SOX) regulations? Is it aware of Basel II recommendations?

The degree of fit is an important indicator of your project’s alignment with the standard functionality. After you determine the degree of fit, and understand what it means for the project, do you just passively accept the findings, or do you do something to make them more favorable?

Many of you have asked me how to get my and Dave’s new book “Implementing Microsoft Dynamics NAV 2009”. I am glad to let you know that now you can get it on Amazon.com by following this link: Implementing Microsoft® Dynamics NAV 2009 . Also, there is a direct link to this book’s Amazon.com page in the sidebar, and you can also click there to get your copy.