Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Project management and PMO

Agile at scale: getting many teams to deliver together

Agile teams do not make an agile organisation. Our consultants help your teams sort out what happens between them: priorities, dependencies, integration and the way the work is funded.

Our principles

  • A framework chosen for your context, not by default
  • A cadence and priorities shared by the teams
  • Steering based on what is actually delivered
In brief

Agile at scale refers to the organisation that enables several agile teams to deliver the same product or the same transformation together, with common priorities and a shared cadence. Management Square helps you choose a framework suited to your context (SAFe or an alternative), synchronise the teams and steer by the value delivered rather than by reported progress.

Scope

How we contribute

  1. Assessment of your current agile set-up

    Observation of the teams, the dependencies and the decision path, from the business request to the production release. We locate what slows the flow before proposing a framework.

  2. Choosing and adapting the framework

    Comparison of the options (SAFe, LeSS, Nexus, product-based organisation) in the light of your size, your architecture and your constraints, then definition of what you retain from them.

  3. Structuring into value streams and teams

    Grouping teams around products or journeys, so as to reduce dependencies instead of administering them.

  4. Synchronisation and joint planning

    Shared cadence, collective planning by increment, demonstration of the integrated system and visible handling of dependencies between teams.

  5. Steering by value

    Increment objectives expressed as outcomes, prioritisation rules for the common backlog and a link with portfolio decisions.

  6. Support for key roles

    Support for product owners, synchronisation facilitators and managers, whose role changes more than that of the teams.

Page contents

Why agile at scale disappoints in both directions

Agile at scale runs up against two opposite failures, and it is common to move from one to the other.

The first is agility that has remained local. The teams work in sprints, hold their rituals, deliver software that works. But each one waits for the others to go into production. Integration happens late, priorities come from several sponsors who do not talk to each other, and the budget remains allocated to projects whose scope was fixed a year earlier. The organisation has agile teams and unchanged lead times.

The second is the framework applied from above. To get out of the first situation, the company adopts a complete framework: new roles, new governance bodies, new vocabulary. The old functions are renamed, the committees change their names, and joint planning becomes a ceremony where everyone presents a plan already settled. Nothing has changed in the way decisions are made or in the architecture that creates the dependencies.

In both cases, the subject has been approached through the teams or through the organisation chart. It is dealt with through the flow: what separates a request from its go-live, and everything that makes it wait.

SAFe and its alternatives: which framework for which situation

Several public frameworks offer an answer. None is superior in absolute terms: they correspond to different sizes, cultures and levels of prescription.

Framework Principle Suitable when Point of caution
SAFe (Scaled Agile Framework) Detailed multi-level framework that groups teams into delivery trains synchronised by joint increment planning The organisation is large, regulated, and needs explicit roles and reference points Can be applied as a procedure, without addressing the causes of dependencies
LeSS (Large-Scale Scrum) Scrum extended to several teams, with a single product owner and a single backlog Several teams develop the same product and the company agrees to simplify its structure Requires existing coordination roles to be called into question
Nexus Scrum supplemented by a team in charge of integration between teams A few Scrum teams share a product and struggle with integration Deals with neither the portfolio nor funding
Tribes and squads organisation Autonomous teams grouped by domain, with cross-cutting communities of practice The architecture genuinely allows team autonomy This model describes one company’s organisation at a given moment: it is not a framework accompanied by rules

Our glossary entry on the definition of SAFe details the concepts specific to this framework. In practice, many organisations take a framework as a starting point, then lighten or supplement it. What matters is less the name of the framework than the questions it forces you to settle.

The five questions every set-up must settle

Whatever the framework, a set-up at scale works if it answers five questions clearly.

  1. Who sets the priorities? A single place for decisions per value stream, and a common backlog whose order applies to all the teams concerned.
  2. At what rhythm? A shared cadence, which makes it possible to plan together, deliver together and correct course at regular intervals.
  3. How are dependencies handled? They are made visible during joint planning, assigned, then tracked between two planning sessions. The long-term objective is to reduce their number through the way teams and architecture are divided up.
  4. When is the system integrated? Continuously, with a regular demonstration of the assembled product and not of each team’s contribution. This requirement assumes an automated delivery pipeline, a subject we cover in our DevOps and platform engineering offering.
  5. How is the work funded? Through capacity allocated to a value stream, whose priorities are revised during the year. This point links the set-up to project portfolio management, which must evolve at the same time.

Our approach: start from a value stream, not from the organisation chart

We begin by following a real request, from its expression by the business to its go-live. This journey shows where the work waits: approval, dependency on another team, unavailable environment, pending decision. The assessment is based on these waiting times, not on a maturity questionnaire.

We then choose with you a first value stream, important enough for the result to matter and well enough delimited to be reorganised without touching the whole company. Our consultants help redefine the scope of the teams there, establish the cadence and prepare the first joint planning with the product owners.

The extension is carried out stream by stream, drawing lessons from the previous one. Managers are supported throughout the journey. Their role shifts from assigning work to removing obstacles, and this shift is the most difficult part of the transformation. It is a matter of change management as much as of method.

The pitfalls we help you avoid

  • Renaming without transforming. Changing job titles and committee names alters neither decision paths nor dependencies.
  • Administering dependencies instead of removing them. A dependency board that stays just as full from one increment to the next signals a team structure or an architecture that needs rethinking.
  • Planning in order to commit to a scope. Increment planning used as a delivery contract recreates a traditional cycle, with less visibility.
  • Leaving the portfolio aside. If the budget remains allocated to fixed projects, teams cannot change priorities, whatever the framework on display.
  • Measuring activity. Comparing teams on their velocity pushes them to inflate their estimates, without delivering anything more.

Measuring the value delivered, not the activity

The indicators of a set-up at scale describe the flow and its outcome. We track with you the time between a request and its go-live, the frequency of production releases, and predictability, that is, the share of increment objectives actually achieved. We add to these the number of dependencies discovered during the increment, which measures the quality of planning, and the share of capacity absorbed by defects.

These flow measurements do not say whether what is delivered is of any use. Each increment objective is therefore linked to an expected outcome for the user or for the business, checked after go-live. It is this check that underpins steering by value: a feature delivered on time that nobody uses is not a success.

Typical work

What our consultants contribute to

Assessment report

Map of the teams and their dependencies, flow blocking points and framework options with their consequences.

Target organisation model

Value streams, team scope, roles, governance bodies and cadence, with what changes compared with the current situation.

Joint planning kit

Running order for increment planning, objective format, dependency board and backlog refinement rules.

Flow dashboard

Lead time, delivery frequency and predictability indicators, fed by the tools the teams already use.

Insights

Further reading

All insights
Milestones, trains or hybrid: which IT programme management model should you choose?

An IT programme management model describes the way a programme plans, measures progress, allocates decisions and organises its teams. Management Square compares here three models in common use (milestones and work packages, trains or value streams, hybrid) on these four dimensions, and indicates the situations each one suits best.

Read the analysis
Product owner or product manager, two functions to distinguish before appointing anyone

In the Scrum Guide, the product owner is the person accountable for the value of a product and for its Product Backlog; product manager is a job title, absent from that guide, which in practice refers to the person in charge of a product's trajectory. Management Square compares product owner and product manager here (horizon, scope, counterparts, decisions) and describes the possible set-ups.

Read the analysis
From project PMO to agile PMO, a change of stance

Common usage calls an agile PMO a project office serving teams that deliver in iterations: it plans a cadence and a capacity, measures what is delivered and prepares priority arbitrations, without changing its mandate. Management Square compares here this stance with that of a project PMO in a predictive life cycle: what the office plans, measures, has arbitrated and stops doing, then what it keeps.

Read the analysis

Management Square in figures

300+
projects completed
43+
clients supported
Since2015
serving our clients
  • Allianz
  • Euler Hermes
  • Groupe BPCE
  • ODDO BHF
  • Candriam
  • Ledger
  • Saur
  • Veolia
  • Voltalia
  • emeis
  • Bonpoint
  • Legal Suite

FAQ

Frequently asked questions

Another question? Ask us

What is agile at scale?

Agile at scale is the set of practices that enable several agile teams to work on the same product or the same transformation without losing what makes agility worthwhile: frequent deliveries and the ability to change priorities. It deals with what a single team does not have to sort out: dependencies, integration, common priorities and funding.

Is SAFe the only agile at scale framework?

No. SAFe (Scaled Agile Framework) is a detailed framework designed for large organisations, but there are others, such as LeSS, Nexus, Scrum@Scale or Disciplined Agile. They differ in how prescriptive they are and in the size of organisation they target. Many companies build their own set-up from these sources.

From how many teams do you need an agile at scale framework?

The number of teams matters less than how dependent they are on one another. Two or three teams sharing the same product already need a common backlog and frequent integration. Conversely, many teams working on independent products do not need a heavy framework. The criterion is how often one team waits for another team in order to deliver.

Is agile at scale compatible with an annual budget?

Yes, provided the object of the budget changes. Instead of funding projects with a fixed scope, the organisation allocates capacity to value streams or products, then revises priorities within that envelope over the year. Budgetary control remains, but it applies to the envelope and to the value obtained.

Should all teams be trained before starting?

No. General training without immediate practice is quickly forgotten. It is more effective to start on a specific value stream, train the people concerned just before their first joint planning, then extend the set-up building on this first scope.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.