AL Object ID Ninja

Zero-configuration, dead-simple, lightning fast, no-collision object ID assignment for multi-user repositories

From the blog

Is agile ERP implementation possible?

image 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.

At the core of any agile approach is an assumption that whatever the requirements might be at the beginning of a project, they won’t be the same at the end of the project. The longer the project, the more truth there is in this assumption. To mitigate this situation, agile methodologies start with smaller sets of requirements, they start small and deliver functionality incrementally in a series of releases. No single release covers all requirements, but every release delivers more than the previous one.

With ERP implementations, we generally don’t subscribe to this idea. And at that, we might be wrong.

How you should learn from Sure Step

Sword & stone (Excalibur) by Midnight-digital (Not leaving ! Just very busy) (opens in a new window) 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.

As a result, companies sometimes offer excuses such as: it would be too expensive for the customer, or we would lose the project to the competitor, because our price would be too high.

In my opinion, this kind of reasoning is just wrong.