Experience

Starting it from scratch – do you dare?

  • Reading time:6 mins read

(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 never do it as well as you did it the first time…

And yet, when initial frustration is gone, and you start doing it over again, from scratch, you are more likely to produce results of higher quality than the first time. Why? The reason for this is simply called—experience.

Continue ReadingStarting it from scratch – do you dare?

Introducing RoleTailored Experience

  • Reading time:5 mins read

In on of my earlier posts here on this blog, where I was merely testing out my theories, I said that user interface is one of the biggest drivers of return on investment: a familiar, easy to navigate, non-cluttered user interface that truly allows you to focus on your work, and not spend too much time meddling with hundreds of options, never being really sure which one to click (okay, I exaggerate, but don’t worry, that’s on purpose)—wouldn’t something like that cut down employee ramp-up time significantly and boost the productivity?

Well, now it’s here, and it’s called the RoleTailored user interface. Or experience, whichever you prefer.

Continue ReadingIntroducing RoleTailored Experience

Read My Lips: Why?

  • Reading time:6 mins read

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. Wiegers to devalue and dismiss Sure Step: firstly, the article has really nothing to do with implementation methodologies at all, and secondly, when I delivered Sure Step training at WinDays pre-conf earlier this year, I gave to each attendant a copy of Karl E. Wiegers’s latest book “Practical Project Initiation”—at the time it was the best book available that matched both the message of my training and the point of Sure Step as a methodology.

Continue ReadingRead My Lips: Why?

A case for Sure Step: how Sure Step brings project success

  • Reading time:8 mins read

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.

Continue ReadingA case for Sure Step: how Sure Step brings project success

NeverENDing story

  • Reading time:6 mins read

Hint: this is a post for developers, and mostly junior developers, those who are still learning how to code properly. I know, I promised not to blog about stuff like this, but I simply couldn’t help this time.

A friend of mine has asked me for help.

“There is this C/AL function I had to rewrite, now I end up with 106 BEGINs, and only 105 ENDs. Do you have any idea how to find where this missing END belongs?”

Continue ReadingNeverENDing story

Architectures: Good, Bad and Ugly

  • Reading time:6 mins read

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. Most of the stuff he talked about reminded me of some bad experiences about architectures on projects I’ve worked on. Most of stuff here is also not my original contribution to the universal pool of knowledge, and I reuse it with the permission of the author, so Miha, thanks! What I did, however, is that I applied general principles to specific Microsoft Dynamics NAV situations.

Continue ReadingArchitectures: Good, Bad and Ugly

Not-so-elementary costing: The Change

  • Reading time:5 mins read

They say the only constant is change. I’d say that the only other constant is error. We humans tend to err. Give a repeatable task to a human, and they’ll mess it up every once in a while. Some call it the human factor.

One of the many repeatable tasks in Microsoft Dynamics NAV is setting up items. If you remember my rant about mandatory fields, and how I said they were baaad, there might be an even more baaad kind of fields: the default value fields. Because the system simply inserts a value into these fields without asking for your say, and if anything is easy, it’s only so easy to overlook these. Yep, you have a chance to voice your oppinion on these, but having got to hurry for a cup of coffe with Mary from accounting, admit it, you’re gonna leave that default FIFO costing method for an item every once in a while, even though it should really have been Average. Then you’ll start posting. Then your phone rings and starts screaming at you about a moron who screwed up items again.

Continue ReadingNot-so-elementary costing: The Change