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.
Another one’s down, so let me give it a quick glance over my shoulder before I move on: March 2009.
This was the best month ever for this blog: it has seen most posts from me, most visits from you, most subscribers to the feed, and I’ve covered a wide range of topics which I am not yet sure if it has got me or lost me more visitors.
How do you eat an elephant? One bite at a time. Swallowing it all at once might be tempting as it has all the potential you need to get into the next edition of Guinness World Records. Likewise, trying it with an ERP implementation has all the potential you need to get into to the next edition of Chaos Report. One way or the other.
ERP software is huge. It contains thousands of features potentially touching every single tiniest aspect of your business. Implementing ERP is about introducing change into your company, and change can be evolutionary, or revolutionary. Your pick.
In my previous post I’ve (what, again?) shared some statistics about success and failure rates of software projects in general and ERP projects specifically. It seems that ERP projects fare somewhat worse than generic software projects, which I stated might have a lot to do with how requirements are handled.
Agile is an unpopular word in ERP world. We, the ERP people, love the glory and the thunder of The Waterfall. It has worked for us since forever, after all. Yes, we’ve all seen it fail every so often, but we’ve learned to learn from failure, and we know there is no better approach. Don’t we?