Agile Scaling and Descaling
Growing IT organisations often suffer from exponentially increasing complexity: too many coordination rounds, too little value creation. We structure teams to create value largely autonomously. The focus is on descaling: reducing unnecessary process bureaucracy in favour of clear responsibilities.
Focus Areas
Team Topologies Implementation We organise teams according to the principles of Stream-Aligned, Platform, and Enabling Teams. The goal is to minimise the cognitive load for each individual developer.
Inverse Conway Manoeuvre We align team structures so that they promote the desired software architecture (e.g., microservices) instead of hindering it through communication silos.
WIP Limitation and Focus Mechanisms reduce the number of parallel projects. Throughput (Lead Time) and quality increase.
Use Cases
- Growing Agencies: Scaling delivery capacity while maintaining consistent quality.
- Internal IT Departments: Transformation from purely execution-focused units to strategic product teams.
- Transformation Projects: Moving from waterfall to agile operating models.
Methods
The methods behind this are documented in the Neuland Handbook:
- Agile Scaling : Team Topologies in detail.
- Leadership Principles : Context instead of control.