One team is not enough!

If you already have experience with individual agile teams, the next step is often to extend the processes and structures to several teams or the next areas of organization, or to synchronize the individual teams. This extension is understood as agile scaling.

A few important principles and practices for agile scaling are:

Add – don’t tailor down: It is better to start with a simple and working foundation instead of implementing everything first and then attempting to figure out what is superfluous.

Systemic Thinking: The whole picture must be considered holistically. A mere cut-out can lead to local optimization, which, in turn, could cause global damage.

Simplicity: It is better to focus on what the (hopefully few) really important things are, instead of preparing for every conceivable possibility.


Our preferred tool for agile scaling is LeSS (Large-Scale Scrum). This is based on Scrum, which means that tried-and-tested agile methods and tools can be ideally utilized. When scaling, it is important for us to build on existing processes and structures – evolution instead of revolution!

Just as with the use of Scrum, it is essential to fill in the gaps in the framework (intentionally) with your personal requirements. It is particularly important to get the employees of your company on board so that they feel that they are taking part in your reorganization.

Read our Merkur LeSS case study on the use of LeSS frameworks for Merkur insurance.

Benefit from our many years of experience in supporting companies on their path to agile scaling!

You can find more knowledge and discourse on LeSS at the LeSS Austria Community:


You would like to join us on the path of agile team scaling? Then send in a non-binding request.

Scroll to Top