Skip to main content

Command Palette

Search for a command to run...

Scaled Agile case studies

What are the most typical scaling problems, how to overcome them, and some case studies

Updated
2 min read
Scaled Agile case studies
R
I'm a Full-stack leader who loves learning and experimenting. Put me in any situation, I'll make order from chaos.

The world is not black and white but quiet colourful!

Let’s start by stating that none of the solutions is universally “good” or “bad”. The more you learn, the bigger toolset you will have to tailor your own environment.

We are all in a journey, nothing is ever perfect. Even the companies mentioned below have many areas to improve**.** But hey, it’s good news, because it means that there is always room for improvements!


Difficulties coming from scaling

The bigger the company gets, the more difficult it will be to deliver complex software.

Some of the most typical scaling problems

  • Growing legacy systems

  • Complexity, dependencies on other systems

  • Complexity of communication

  • Bureaucracy, change resistance

  • Losing sight of the big picture

How can we overcome them?

Lean, Agile, and engineering practices are all important; Having a good mindset helps you avoid endless bureaucracy and micromanagement. On the other hand, you need the right engineering practices to be able to focus on the important work instead of wasting your time on repeating manual work. See the 7 wastes of Lean for software development.

I find these especially important:

  • Clear vision constantly communicated by product, and connected to everyday development

  • High transparency in team structures (Who is working on what?)
    -> so, teams can self-organize their work with other teams

  • Continuous Integration for frequent code integration

  • Continuous Delivery for frequent customer feedback

  • Create a culture which attracts and keeps talent
    (Why Two-Thirds of the Fastest-Growing Companies Fail)


Case studies

Spotify

You can learn about scaled Agile, and engineering practices implemented in Spotify. Many of these values we also passionately share at Infinik!

https://www.youtube.com/watch?v=R2o-Xm3UVjs

PayPal

To make scaled changes you usually need an iterative approach, because big bang solutions carry a huge risk and can easily fail. Well... they can, but not always. You can see a counter example with PayPal:

https://www.youtube.com/watch?v=FtzJjbEATKk

Microsoft

You can learn about the technological, and process changes that helped Microsoft to reduce release time from 3 years to 3 months:

https://www.youtube.com/watch?v=nno6DwevspI

Do you have any good story or advice? Share with us!

More from this blog

I

Infinik's Awesome Blog 🦄

5 posts

Welcome to Infinik Insights! We build AI-powered organizational development tools for SMEs too.

This blog is where psychology, leadership, and startup reality meet. Expect actionable tips on team dynamics, agile company culture, and modern management to help you scale smarter. Every now and then, we’ll also peek under the hood to share our tech stack, AI experiments, and engineering lessons.

Whether you are scaling a team or curious about the tech behind it, you're in the right place! 💡