Linear vs. agile: project management in a roundabout way

Project management – just recently we here presented the various methods that a company could use to tackle an ERP project. However, if the approaches seem a little too complex, you can now look at two "simpler" or rather "more fundamental" approaches. You only need to ask yourself one question: do you prefer the linear or the agile approach? Which is better: linear vs. agile?

One by one

The more classic variant: step by step. The project is divided into phases. Standard here are usually the analysis of the processes, conception, implementation, integration test and finally the rollout. Once a phase is over, there isn't a lot of tweaking, improvement and modification afterwards. The structures can be advantageous if a high level of planning security is required. So full control. Many IT companies find that great at first.

However, the linear approach also has its risks. Because a ERP project is so complex that mistakes are often only noticed when you are really looking for them - or when it's just too late. An example would be that processes are incorrectly adjusted or simply forgotten in the analysis. There are often misunderstandings here, since most companies (at least in the medium-sized sector) work together with providers who are at the process analysis based on the statements of the company and the company in turn does not know all the possibilities/solutions of the provider. When the concept is in place - i.e. this phase is complete - then the lack or error of a process only becomes apparent during integration. But corrections here are one thing above all: expensive.
One might now think that there is no other way than to bear the additional costs at the end of an ERP project. But it does. Especially if there are indications in your company that the project will involve many changes to processes and workflows - i.e. it is complex and therefore confusing - the agile version of the process management be something for you.

Keep track of clutter

The "linear vs. agile" comparison is still used by few in the ERP business. With an agile method, in contrast to the linear method, you do not work through individual phases. Instead, short processing cycles are carried out in which individual functions are completely designed, implemented and tested. To make this possible, close co-operation between the provider and the company is essential, as the latter must improve the results during each cycle. This means that any changes can even be implemented during the implementation phase and errors are recognised at the latest during the immediately following test phase of individual functions. The agile method also has the advantage that the users (the company) become familiar with the "new" system straight away and also understand why which change is taking place.

On the other hand, it is difficult for providers if the management has to be convinced of the agile method. Because the apparent loss of control for lack of precisely calculated project plan is unfamiliar to most people. At the beginning of the project, it is therefore difficult to say when individual functions are actually functional. But as described above: planned does not mean finished.

Who will win the "linear vs. agile" game?

Two thirds of ERP projects are now processed linearly. However, there is a growing realization that agile methods may be the right answer to ever more complex project requirements.

SAP B1 blog