You can thank us later

How come they all recommend an Agile implementation?

Agile implementation

Insanity Is Doing the Same Thing Over and Over Again and Expecting Different Results ~ Albert Einstein

Agile is the concept where you can continuously build, test, and implement the smaller components of the system and then proceed forward to the next system. You design, develop, test, and seek customers’ feedback from the beginning and maximize the progress.

Can this approach be applied to an ERP implementation? Sure!

That is why all corporate software providers indicate that Agile is the best/only way to implement their tools… (SAP, Oracle, SalesForce)


Did you know?


Can we do something about the above high rates of failure? Sure! 

Big bang implementations are risky! Do we want to do a better job of risk management? Sure! 


By applying some of the core principles of Agile:

  1. Short iterative cycles with early feedback from the business users.
  2. Breakdown of the functional scope into ‘small bites’ – smaller set of features that small teams can deliver in short sprints, thus, realizing business value quickly.
  3. Continuously deploy these sub-sets of features (MVP) –working system
  4. Repeat 1, 2, 3… and continuously deliver fully functional modules, even though they are not fully featured.

Realizing business value quickly can be achieved in a couple of ways:

  1. Deploy a minimal footprint (MVP) in one site vs. across multiple site. Benefit from a working system and early feedback from users.
  2. Deploy a small no. of fully functional modules vs. fully featured and/or across all sites. Benefit from a working system and early feedback from users.

It is not surprising that all of the large corporate software companies highly recommend deploying their software in an Agile manner: