Blog

This was a part of Chapter 1 in the first draft of my book Implementing Microsoft Dynamics NAV 2009 . It was cut to keep page count down and preserve the environment, but I figure that a few electrons pushed through the optical labyrinths of The Internet won’t hurt anyone, so here you get it, in its original form: The History of Microsoft Dynamics NAV.

One of the biggest absurdities about ERP systems springs from the very word we use so often when describing ERP: integrated . ERP is an integrated system: it integrates all data and processes into a single application. Different modules look over different aspects of data and processes, but a change in one module automatically reflects in all others.

You can’t avoid customizations. Vanilla ERP is a great first step, and a valuable tool for establishing common language between the customer and the consultant. But in the long run? Probably not. Pristine uncustomized ERP won’t be sufficient, because of the gaps between your way and ERP’s way.

– “We need a report which groups our sales by product components.” – “And we need it broken down by cost centers.” – “And it must show comparison with last month, quarter and year, and with budget and forecast, with indexes and trends. In linear regression.” – “And it must let you choose if it is by posting date or by document date.

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 .

“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” That’s the very first principle of the Agile Manifesto . The problem with ERP is that the first deliveries are all but early: they typically occur only after about twenty months .

Many people have asked me about availability of a downloadable Microsoft Dynamics NAV 2009 demo. Unless you are an existing Microsoft Dynamics NAV customer on a support plan, or a Microsoft Dynamics partner, you can’t download a demo version from a public Microsoft web site.

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 has been gaining momentum among software development methodologies for past decade or so. Various researches and surveys consistently show that software developed under an agile approach is generally better than the software developed under waterfall approaches.

Prescriptive methodologies, such as Sure Step, are double-edged swords. They are aimed at increasing repeatability, consistency, traceability, manageability and more of your projects, yet they seemingly increase overhead and contribute to an inflated project price tag.