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? 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.
(A short rant about eye-contact-based specifications.)
In short, there is no such things as an eye-contact-based specification. And for a reason.
While kicking-off of a project, we had a discussion with the customer about the change management approach, and specification detail. (more…)
I’ve been blogging about Sure Step, talking about Sure Step, learning about Sure Step, teaching Sure Step, evangelizing Sure Step, here on this blog, in online columns, at conferences, presentations,…
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 deliverable of the Analysis phase and it both documented customer’s requirements and explained how they will be met with Microsoft Dynamics NAV solution.