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. So, an incredibly short year later, here’s another one: WinDays9.
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? Microsoft Dynamics is the best choice ERP and the report (as a whole) clearly shows why exactly.
Project plan. A fancy term we all like to use. But believe it or not, most of us don’t even know what a project plan really is.
I don’t know why, how and when it came to be that in IT we started using the term project plan, but whatever the origin, the term we use is somewhat incorrect, and when attached to what we often attach it to, it’s downright wrong.
Take that project you are currently running, and imagine, just for a second, that it came with only 3% budget overrun. Most of people in software industry would call it wild success.
In motion picture industry, however, trampling measly 2% or 3% over initial budget would be considered a failure.
While movie industry and software industry are seemingly light years apart, there are many things these two have in common, and there are obviously many things we can learn from them.
Many project management authorities assert that from project management stance all projects are equal. I dare saying that some projects are more equal than others.
In my last post, I argued why I believe software (and ERP) projects are different. But something came to my mind today, and it’s really an important differentiator of ERP projects from other kinds of projects.