Linear vs. agile: project management in a roundabout way

Project management - just the other day 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 have 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. The standard phases here are usually analysing the processes, conception, implementation, integration test and finally the rollout. Once a phase has been completed, there is no need to tweak, improve or change it afterwards. The structures can be advantageous if a high degree of planning security is required. In other words, full control. Many IT companies in particular find this great at first.

However, the linear approach also has its risks. Because a ERP project is so complex that errors often only become apparent when you are really looking for them - or when it is too late. One example would be that processes are incorrectly adapted or simply forgotten in the analysis. This often leads to misunderstandings, as most companies (at least in the SME sector) work with providers who do not specialise in the analysis. process analysis The company must rely on the company's statements and the company in turn does not know all the options/solutions offered by the provider. Once the concept has been finalised - i.e. this phase has been completed - the absence or error of a process only becomes apparent during integration. Corrections here are one thing above all: expensive.
You might think that there is no other option than to bear the additional costs at the end of an ERP project. But there is. Particularly if your company is anticipating that the project will involve many changes to processes and workflows - i.e. it is complex and therefore confusing - the agile variant of the process management be something for you.

Keeping an overview with confusion

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. This is because the apparent loss of control due to a 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 will actually be 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