Development

So I would guess that was it. I’m just returning to Kristiansand, my Norwegian base, after delivering the “Microsoft Dynamics NAV 2009 Development Best Practices” course to a partner, my first custom-developed training ever. My impression is—mission accomplished. I was not sure at first how this would turn out.

“Best practices” is one of those beloved and hated concepts. There are people who just embrace “best” practices for the sake of their bestness . And there are people who just shun them for the very same reason—those know-it-alls who have opinion on everything and know it better before even learning about it.

You can’t avoid customizations. Vanilla ERP is a great first step, and a valuable tool for establishing common language between the customer and the consultant. But in the long run? Probably not. Pristine uncustomized ERP won’t be sufficient, because of the gaps between your way and ERP’s way.

Yesterday, in my What does a Microsoft Dynamics consultant do? post I started explaining the job of an application consultant. As promised, today I’ll explain what duties an application consultant has in each of Sure Step phases.

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?

!!! Check out my book Implementing Microsoft Dynamics NAV 2009 !!! The long awaited Microsoft Dynamics NAV 2009 has been released for download earlier this week, and has just been publicly announced at Convergence 2008 Copenhagen. If you have PartnerSource access, you can download Microsoft Dynamics NAV 2009 here .

One of many improvements the latest version of Microsoft Dynamics Sure Step methodology has brought along is the revised purpose of the Functional Requirements Document (FRD) . This document has long served as cornerstone of every Analysis process of every implementation project: it was the main…

Recently, a reader, commenting on my last post about Sure Step , pointed me to an article by Karl E. Wiegers “Read My Lips: No New Models!” I initially responded to the comment, but I figure the comments aren’t read as often as posts, so I decided to blog it. It’s doubly funny that the reader is using Dr.

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.

[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.