Scenarios

Each scenario isolates a different facet of software team dynamics. Pick one and start experimenting.

adding people helps — until it doesn’t

Mythical Man Month

Why is it that adding more people to a late project makes it later?

  • Project size and chunk size shape how much work can happen in parallel
  • Coordination, onboarding, drag, and interruptions eat into team capacity
  • The staffing curve often bottoms out before the largest possible team
Run simulation
LOWHIGHDEFECT RISK
grows with deploy size · shrinks with tests

Deployment Reliability

How does defect rate change as you deploy more code at once? Explore the relationship between commit size, test coverage, and the probability that something breaks in production.

  • Larger deploys compound defect probability — subroutine interactions multiply
  • Test coverage catches defects before they reach production
  • Developer care (haste) directly shapes how many defects are introduced per commit
Run simulation
place, wire, and observe emergent dynamics

Studio

Design an organization from scratch on a canvas. Place teams, environments, and customer bases, wire them together, and run the simulation to observe emergent dynamics.

  • Configure any combination of components without touching code
  • Wire customer bases to environments and watch satisfaction respond to code quality
  • Pre-seed environments with healthy or defective code to explore different starting conditions
Open Studio