2009

Can you believe it? I can’t. Almost. Two years ago I started this blog as a hobby, and I myself didn’t believe it would work out. It was months before the first reader appeared, but then it kind of just happened. Blogging was fun. It was tough.

I’ve seen a few projects where customers said they didn’t need contingency, because they decided to adjust the budget as changes happen. How does this sound to you? To me, this sounds pretty bad, because there is an important distinction between adjusting the budget based on change requests and consuming the contingency reserve.

Blogs are a great thing. They allow people to share their own knowledge, experience, thoughts, ideas. But communities are the real thing, they allow many people do the same at once, expanding the sharing into exchanging knowledge, experience, thoughts, ideas, advice, you name it.

April. There is definitely something upside down with this month. I’ve started it with a somewhat ambitious decision to blog a post a day. And it worked. Kind of. For the first eight days, anyway. And then it happened. Suddenly I’ve found myself blogging only occasionally, practically chasing my promise to deliver a blog post twice a week.

MSDynamicsWorld.com has just posted an excerpt from my friend Dave’s and my book Implementing Microsoft Dynamics NAV 2009, delivering some content from chapter 4, focusing on the implementation process. The Chapter 4 draws a lot of its content from Sure Step best practices, and the fact that…

If projects were completely predictable, there would be no need for risk management . Everything could be planned and executed according to plan. However, we know better. Unexpected things happen, disrupt the original plans and cause time and cost overruns. In IT projects, these overruns are far too common to be ignored.

WinDays9 is over, thank you all who attended my presentation “What’s new in Microsoft Dynamics NAV 2009”. I hope it was worth your time. For all you lucky ones, I hope you liked the book! I would prefer if I had enough of them to give you each a copy, but let’s just say I was logistically impaired.

Panorama Consulting Group , the authors of the ERP report , have just made available two interesting tools: ERP Quick Diagnostic, and ERP Readiness Assessment. According to their website, if you are “in the early stages of selecting a new ERP software or if you’ve already completed your project, our ERP Quick Diagnostic will help you benchmark with other ERP projects across the globe”.

Often you don’t even notice how quickly time goes by, except for a few milestones, which happen once a year and remind you that another one’s over. WinDays conference is one of such milestones, and I’ve barely published a handful of posts here since the last time it was the most discussed topic in Croatian IT community.

I’ve just got the news about Part III of Panorama’s ERP Report in my inbox. If you missed my analysis of the report , please read it first: part three builds on findings of the first two. I know that I am biased when writing about this, but how can I not be?