Why do so many companies fail at scaling Agile?

A battle-scarred Delivery Director, I’ve been in the Agile world for a while now, and still the debate rages on; why is Agile so hard to scale successfully? And what if anything, can we do about it?
Interview questions often focus on people’s experience using scaling frameworks such as SAFe and DAD. But not all experience has been positive and it helps both companies and workers to understand why. So, I wracked my brain thinking of the various organisations, projects and teams I’ve had the opportunity to work with, the growth strategy conversations I have been privy to, and the talks / conferences I’ve attended. And I realised that the trope is true, but it doesn’t have to be this way.
Yes, Agile doesn’t scale… but only in isolation.
The very nature of Agile and the key to its success, is often the key to its downfall. Agile advocates moving quickly; delivering as fast as possible, iterating wildly… but is the company or organisation structured to support it? An obvious question perhaps, but from experience, it’s often the missing puzzle piece. Scaling Agile is so often seen as a failure – but for the vast majority, the organisation is unable to support the growth of its Agile community.
I often find myself coming back to this article from the GDS team about Agile governance and agree that to avoid failing, the right questions need to be asked before you start:
Are the right people empowered at the right level in the organisation to make decisions?

  • Agility requires autonomy. The people closest to the problem are often the most qualified to resolve that problem, but they need to be empowered to do so. If you are constantly hearing the phrase ‘we will need to escalate this to be resolved’ – you probably don’t have the autonomy you need to move quickly. This is equally important in managing inter-team dependencies, the best people to resolve these dependencies are the teams themselves; but if every decision has to go through arbitration, you will be slowing down multiple teams. Finding a friction free way for teams to resolve such issues is key to delivering at pace at scale.

Do you have the right people to support the teams in the right way?

  • Much like the point above, having the right people supporting teams is crucial. If the leadership at team level is spending time resolving recruitment, budgetary and business operational issues – they are not focusing on delivery, and that will slow you down. Organisations tackle this in different ways, either by matrix structures, the infamous ‘Spotify model’ of clans and guilds or communities of practice – all essentially distributing the load so that the right people are involved at the right time. There is no ‘magic wand’ – each organisation needs to work out what works best in their context.

Does your organisation have a single, clear objective, that multiple Delivery teams can strive for?

  • One of the phrases I fall back on when talking to senior technical leaders is ‘humans scale horizontally, not vertically’. You reach a point where the people you have can only generate so much throughput, so the only option is to add more people. When you add more people to the pool, you need to make sure they have the same understanding of the objective. If they set off in a direction of their own, it is like adding a serve to your cluster with a different configuration and can do more damage than good. Making sure everyone is pushing in the same direction is critical to delivering at scale.

Who will take ownership of each part of the scaling process?

  • Scaling needs to be planned- not through charts and dates, but deliberate and structured. The goal is to find a pattern that suits your organisation so it can be replicated. In the same way that you manage the process as team level, you either empower the team or an individual to manage the process. In my experience this is most successful when managed by an individual whose sole focus is the scaling process; importantly also someone who knows how to navigate the organisation. This is an intensely contextual exercise and will require both tenderness and tenacity.

Every organisation is different, and as a result, all efforts to scale Agile will be different. Some may already have the organisational structure to support a scaling delivery team, but all too often it’s an afterthought and by then, too late.
If you haven’t prepared the business for Agile at scale, but want to push ahead anyway then heed this warning: a foolish person did build their house upon the sand.

Share on facebook
Share on twitter
Share on linkedin

One Response

  1. Mike,
    I am new in Agile and have just started learning its concept until I came across with your article. I fully agree with the notion that you have presented here especially the required questions and not just right questions to be asked to prevent failing on scaling Agile. However, as a new disciple of Agile and have just started building and accepting the Agile methodology, I was on the understanding that to be Agile you have to think Agile and act Agile.
    What is the point of scaling Agile if it’s working successfully? Even if you have the right people empowered to make a decision, the right people to support the team, a clear organizational objective, and have identified the team or individual to take ownership in managing and focusing on the process of scaling. Do you really need to scale Agile and what would be the consequences of not having the plan incorporated into the organization’s structure?
    Ed Manalansan

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

In The Zone with Marcin Zasepa

Welcome to the second in our new series, ‘in the zone’, a collection of conversations with CTO’s within the CTO Zone community. Each week we’ll be discussing the latest trends, insights gained from there experiences, and future predictions for their industry. This week we’d like to welcome Marcin Zasepa, CTO at Homegate AG in Switzerland. Every episode will be approximately 30 minutes

Read More »

In The Zone with Sasha Bilton

Welcome to the first in our new series, ‘in the zone’, a collection of conversations with CTO’s within the CTO Zone community. Each week we’ll be discussing the latest trends, insights gained from there experiences, and future predictions for their industry. This week we’d like to welcome Sasha Bilton. Every episode will be approximately 30 minutes long, and we aim

Read More »

Case Study: DAZN Data Engineering

Find out how 101 Ways helped DAZN improve their existing data warehouse as well as planning and setting the foundations of the new cloud-based data platform. Click here to download the full case study. Get in touch with a member of the 101 Ways team if you would like to discuss ways in which we can help you and your company

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?


101 Ways Limited
41 Corsham Street
N1 6DR
United Kingdom


101 Ways Limited
No.1 Spinningfields
Quay Street
M3 3JE
United Kingdom


101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.