One shared language for progress and dependencies: enabling alignment across agile and traditional delivery 

By Pim Veldhoven | Associate Partner | Consuting

The challenge 

As organisations scale agile ways of working while continuing to run large, milestone-driven programmes, a predictable tension emerges. 

Each delivery model speaks a different language of progress. 

Traditional programmes track predefined phases and formal milestones. Agile teams measure success through epics, features and user stories, delivered in short, iterative cycles. Each uses its own terminology, templates and reporting rhythms. Individually, both approaches can work well. The challenge appears when initiatives depend on one another. 

Two friction points quickly surface: 

  1. Integrated planning 
    Building a coherent, end-to-end plan becomes difficult when one part of the organisation works in quarterly increments, and another follows sequential stages with gated milestones. 
  1. Dependency management 
    Dependencies are identified too late, or not at all, because the signals used to express commitments, progress and risk are not compatible across methods. 

The result is familiar: misaligned expectations, missed hand-offs, unclear status reporting and delayed executive decisions. Not because teams are underperforming, but because they are speaking different operational languages. 

The solution 

Running a hybrid delivery organisation effectively requires a single, shared language for progress and dependencies. This does not mean forcing agile teams into waterfall processes, or reshaping traditional programmes to mimic agile ceremonies. Instead, it means introducing a minimal, common framework that connects the two worlds. In practice, this means: 

  • Translating agile outputs into portfolio-level milestones without diluting agility 
  • Aligning planning horizons so that both agile and waterfall teams provide inputs at predictable points 
  • Establishing a unified approach to dependency mapping, making cross-team and cross-method risks visible early 
  • Enabling transparent progress reporting that executives can rely on, regardless of delivery method 

When this shared language is in place, the portfolio begins to move as one system. Planning becomes coherent. Dependencies are surfaced earlier. Risks are addressed proactively. And importantly, agility is preserved rather than constrained. 

Want to know more?

If you’re navigating the complexities of hybrid delivery and want to create a seamless connection between agile and traditional approaches, we can help. Our experts at Valcon work with you to build tailored frameworks that foster shared understanding, improve visibility across teams, and accelerate decision-making, all while respecting each method’s unique strengths. Please reach out to Pim Veldhoven at [email protected].

Insights