5 Lessons Learned from Complex Projects in the Agile Delivery Age

Christian Hansen, Partner, DA Network

Published: April 2026

Executive summary

Over the past 10–15 years, many organisations have moved from traditional waterfall delivery to agile ways of working.  We have seen the same across our clients, where agile delivery has become the standard approach. 

And for good reasons. Agile brings clear advantages:  Requirements can evolve,  Learning happens during delivery &  Value is delivered incrementally 

But when working on complex, time-critical transformations with multiple agile teams, our experience is that:  

1. Detailed Requirements Upfront Still Matter 

Even in agile environments, detailed requirements gathering in the beginning of the project plays a critical role when multiple teams are involved. It creates a shared understanding across teams of what needs to be delivered and why. 

Without this clarity Teams interpret scope differently,  Dependencies are missed &  Integration becomes difficult.

In complex transformations, requirements are not about locking scope, they are about creating alignment at scale. 

2. Planning Creates Alignment - Not Rigidity 

Following requirements, structured planning becomes essential. 

This is where Scope is aligned,  Priorities are clarified & Sequencing across teams is defined 

Strong planning helps identify Dependencies,  Integration points  &  Critical paths

At the same time, planning must remain adaptive. 

The most effective programmes combine Clear roadmaps,  Rolling wave planning & Flexibility for teams to iterate

This balance between structure and agility is what enables predictable delivery. 

3. Testing Must Be Prepared Early 

One of the most consistent lessons across complex transformations: 

Integration issues do not appear within teams; they appear between them. 

Early preparation ensures: Test environments are ready,  Data is available, End-to-end scenarios are defined & Roles and responsibilities are clear

Without this, testing becomes Fragmented,  Reactive &  High-risk

Early test readiness is critical to achieving stable and controlled delivery. 

4. Dependency Management Drives Delivery 

In multi-team environments, dependencies are not a detail they are the backbone of delivery. 

Effective dependency management ensures that: Work is sequenced correctly,  Teams are not blocked & Integration points are aligned 

Without it, delays in one team quickly cascade across the program. 

We consistently see that strong programmes Identify dependencies early  &  Actively track them 

This is key to maintaining momentum and avoiding late surprises. 

5. Progress Must Be Visible at System Level 

Tracking progress across multiple agile teams is essential — but it must go beyond individual team status. The real question is not:
“Are teams progressing?” 

It is:  “Are we moving toward a working end-to-end solution?” 

Effective progress tracking provides a consolidated view across teams,  highlights risks and misalignment early & supports better decision-making. Without it, teams may appear on track, while the overall delivery is drifting. 

The V-model in the agile context 

In our experience a good way to structure complex agile projects is by applying the classic waterfall V-model. This is still largely applied in regulated industries, for good reasons.  

Conclusion 

Agile has fundamentally improved how teams deliver, but in complex, multi-team transformations, success is not determined by individual team performance. It is determined by how well the full solution comes together. 

Our experience across industries shows that the difference lies in combining agile execution with structure, transparency, and end-to-end ownership. Detailed requirements, aligned planning, early test preparation, active dependency management, and system-level progress tracking are not in conflict with agile, they are what make agile work at scale. 

The V-model mindset reinforces this by ensuring that what is defined is consistently validated across the full solution, creating traceability and confidence throughout the delivery. 

In complex transformations, agile delivers the parts; structured delivery ensures they work together.