Help

Software Organization Simulation

Understand technical debt. Master team and organisational complexity.

Describe the project

Four quarters of business as usual — then a classic Legacy System Modernization challenge hits: market, regulatory and personnel pressure all at once. You'll be able to postpone it by up to 2 quarters, but waiting only raises the stakes.

How complex is the legacy system you're taking on? Together, the six values below make up the Required Complexity Capacity — how much complexity your team needs to master so that technical debt doesn't keep piling up.

Base Complexity 0
low high
Transformation Scope 0
small large
Integrations 0
few many/complex
Data Complexity 0
simple complex/sensitive
Regulatory 0
light strict
Operational Criticality 0
low business-critical
0 Raw complexity

Build your team

There's no fixed maximum team size. What matters is whether your team brings enough Delivery, Complexity and Leadership Capacity for the project. You can adjust the team throughout the whole game.

Senior Delivery 5 · Complexity 5 · Leadership +3
0
Professional Delivery 4 · Complexity 3 · Leadership +1
0
Junior Delivery 2 · Complexity 1 · Leadership −2
0

Team Health Check (preview)