Where can we use agile methods

Agile methods: advantages and principles

2. Responding to Change: More than following a plan

In the conventional "waterfall model", the project work takes place in successive phases. When one phase is completed, the next follows, incorporating the results of the previous phase. With this method, those responsible plan all the steps, milestones and project steps in advance - from start to launch. Every single aspect of the project is illuminated, analyzed and, as in a specification sheet, a fixed price is assigned. This procedure means that the start of the project is delayed because a complex plan is first processed in detail and then processed point by point.

But what happens if new findings or unexpected problems arise in the course of the project? At this point, the “waterfall model” makes it difficult to react to changes. Adapting a project plan once it has been designed costs time and money. Since the next phase can only start when the previous one has ended, the strict processing of the individual phase also takes up unnecessary time. In addition, there may be vacation and sick days. In the worst case, delays occur to such an extent that the product does not do justice to the competitive situation and decisive technical innovations can no longer be taken into account.

Agile vs. classic project management

Agile methods such as Scrum, Kanban, Design Thinking and Co. are an alternative to classic project management. Instead of planning that is too detailed, we use clear goals and guidelines in order to start faster and to react flexibly to changes as well as new findings in the development process. That is why we rely on short, manageable work packages ("sprints") and regular and brief exchange on project progress ("daily") for agile projects.