Skip to content

Mastertutorial · Part 9

Agile or waterfall: which project method fits?

With Christian Liebich16 minLeadership & teams

In short

Neither agile nor waterfall is the right method for every project: the method has to adapt to the project, not the other way round. Initialisation, architecture, interfaces and go-live call for sequential planning, while ongoing development benefits from involving stakeholders in an agile way. What decides the outcome is communication, empathy and a shared vision.

The video is spoken in German and has integrated English subtitles. The podcast episode and the blog article are in German. This page summarises the episode in English.

The video is loaded from YouTube only after you click. Data is then transferred to YouTube.

What you take away

  • Every project is unique. Applying Scrum, SAFe or HERMES dogmatically does not lead to the goal.
  • Agile does not mean “we do not plan”: without a rough concept and a cost ceiling there is no financial orientation.
  • Software development does not work like an assembly line, and specialists are not resources.
  • Reporting from the ivory tower hides the truth. Shortly before go-live the “panic zone” follows.

Topics of this episode

  1. Why dogma fails
  2. Communication vs. specification
  3. User stories vs. software architecture
  4. The unavoidable waterfall: initialisation and go-live
  5. Costs, budget and estimates
  6. Tools and reporting
  7. The “panic zone” before completion

Who it is for

For project leads, programme managers and decision-makers who are choosing a method or have reached its limits in a project.

This episode as

Related service

Team Coaching, Workshops & Keynotes

Teams that deliver again, and knowledge about AI and digitalisation that your people can apply right away.

Frequently asked questions

Is waterfall still up to date?

Yes. In initialisation, with strict regulatory requirements and when defining interfaces and architecture, sequential planning is often unavoidable.

Why do agile projects often fail on budget?

Because agility is misunderstood as “we do not plan”. Without a rough concept and a cost ceiling there is no financial orientation, and the scope grows unchecked.

What should I do if the team rejects the method?

Listen. The resistance is often based on practical experience. Adapt the method to the team, not the team to the method.

All Mastertutorials

Let us talk about your project

A first conversation takes 30 minutes and is free of charge. Afterwards you know which next steps make sense.