Users

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…

Don’t you just love when users come up with new feature ideas at a microprocessor clock rate. Even before you finish developing one, five new requests pop up. This is a disease, and it’s called featuritis ! Featuritis doesn’t mean the features are just sporadically requested and developed ad hoc.

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

A few days back, while prototyping a new solution for a customer, one of the key users said: “But in our old software it didn’t work like that.” I was about to try to explain why the change, but then the user’s boss said: – We aren’t implementing a new solution so that everything can stay the way it was.

Four months ago I attended a conference, where I had a chance to listen to Miha Kralj, an architect at Microsoft, talk about architectures. It was one of the best presentations I ever attended, and ever since I had this topic in queue, but never really had chance to write about it.

The biggest jeopardies often lurk where we least expect them. When implementing an ERP system such as Microsoft Dynamics NAV, what should be one of our best allies, turns out to be our mortal enemy. It has a simple name: The Standard. Standard processes, standard functionality, standard documents, standard system.

I’m still in Vegas, and this city is crazy. But it’s funny, us people in IT have a thing or two to learn from these people in gambling business. We have all been hearing from our customers how they want their systems reliable, available, and so.