Scaling Agile

A team is not enough!

If you already have experience with individual agile teams, the next step is often to roll out the processes and structures across multiple teams, to the next areas of the organization, or to bring the teams together. This is the agile scaling. If you do not have an agile methodology yet, please start with the "Agile Adoptions" section, as a successful scaling of Scrum or agile methods in understanding Scrum starts for individual teams.

A few key principles and practices for scaling are::

Add - don't tailor down: It's better to start with a simple and functional base instead of implementing everything first and then trying to figure out what's too much.

Systemic Thinking: It must be considered as a whole. A clipping can lead to local optimization, which can cause damage globally.

Simplicity: It's better to remember what the (hopefully few) really important things are, instead of preparing for every possible opportunity.

Our preferred tool for scaling is LeSS (Large-Scale Scrum). This is based on Scrum, which means that tried-and-tested methods and tools can be used ideally. 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 (intentionally) existing gaps in the framework with your personal requirements. It is especially important to bring the employees on board so that you feel as part of your reorganization.

Read our Merkur LeSS case study on the use of LeSS in Merkur Vorsicherung.

Benefit from our many years of experience in accompanying companies on their way to scaling!

More information and exchange on LeSS can be found at the LeSS Austria Community:

vortrag less video