Today I’ve completed delivering the Microsoft Dynamics Sure Step course in Belgrade, Serbia, and I totally enjoyed it. The discussions were great, there was a lot of experience accumulated in that room, and all of the thirteen people attending the training were participating and contributing knowledge. If ever, this time during training I got zillions of ideas for blog posts, too bad I forgot most of them immediately thereafter :)

One of the discussions we led was about waterfall and its (in)effectiveness. Some of the people, those who primarily come from development background, expressed their belief that waterfall is a bad and an outdated approach which usually leads to failed projects. I shared some of my thoughts on the topic, but I still believe that I didn’t give a good explanation when the waterfall approach works better than an agile one.

Anyway, after a nice evening guided tour of Belgrade (thanks Marko!), and delicious cheese, yoghurt, ham and mushrooms pancakes, when I returned to my room I pondered a bit about the waterfall approach and how it could be put down simply: when to apply it, and when to just opt out.

Then I remembered I’ve once heard at a project management training (or read in a book, or a blog or somewhere) that the waterfall is a good approach when the duration of the project is shorter than the frequency of organizational change.

In other words, if the organizational change is frequent, and the project is long, then the project might fail, because the requirements might change as well.

I’ve tried to google it up quickly, but it yielded nothing, and this is definitely not my own brainpower at work here. I hate skipping giving credit to the author of this thought, but I have a plane to catch.

Bye-bye Belgrade, it was a great training, I hope you all pass the exam!

Read this post at its original location at, or visit the original blog at )