Achieving Enterprise-wide Agility: Beyond the Technology Stack

The technology is the easy part. The hard part is getting thousands of engineers across a dozen time zones to behave like one team. In this session, Naval draws on his experience leading enterprise-wide agility programmes at SLB to show what actually drives adoption — and what doesn't.

Why Pilot Teams Never Look Like the Problem

Every enterprise agile transformation nails the pilot. A hand-picked team, a supportive sponsor, a low-stakes product — of course it works. The failure shows up two years later, when the transformation is supposed to have spread past the first ten teams and hasn't. That's not a training problem. It's a sign that the organisation's structure, incentives, and culture are quietly contradicting the agile principles the pilot demonstrated.

The Three Layers That Must Align

The Technical Layer

Pipelines, platforms, and toolchains — the layer most transformations start with, and the one that's genuinely the easiest to fix. A shared platform and a consistent CI/CD toolchain remove friction, but they don't by themselves change how work gets prioritised or how teams are held accountable. Technology is necessary. It is nowhere near sufficient.

The Process Layer

Portfolio management, OKR alignment, and delivery governance. This is where most enterprise transformations quietly fail: teams run sprints, but funding and prioritisation still happen on an annual planning cycle designed for waterfall delivery. If the process layer above the team hasn't changed, the team-level agility is just theatre inside a system that's still fundamentally project-based.

The Cultural Layer

Ownership, trust, and incentive design. This is the layer leadership talks about least and that determines everything else. If a team's incentives still reward individual output over shared delivery, or if failure is punished rather than treated as signal, no amount of process redesign will produce genuine agility — people will comply with the ceremonies and protect themselves everywhere else.

Three Case Studies

The session walks through three real transformation efforts, each missing a different layer: a team with excellent tooling and process discipline that stalled because incentives still rewarded individual heroics over collective delivery; a business unit with strong cultural buy-in and executive sponsorship that couldn't scale because the annual portfolio funding cycle never changed underneath it; and a platform rollout that delivered a shared toolchain to five hundred engineers without ever addressing the process layer, producing consistent tooling and inconsistent outcomes. In each case, fixing the missing layer — not adding more of what was already working — is what unlocked the next stage of adoption.

Conclusion

Enterprise-wide agility doesn't fail because teams lack Scrum training. It fails because the layers above and around the team — funding, governance, incentives — were never asked to change. Get the technical layer right, and you've made agility possible. Get the process and cultural layers right too, and you've made it durable past the pilot.