Organic growth is the gradual evolution of a software system through accumulated changes rather than centrally planned restructuring. In a codebase, incremental delivery and agile methodology shape the system from the bottom up as developers add solutions over time. section 4.12
This evolution reflects many developers’ differing mental models, biases, and ideas about the future. As people join and leave, the codebase records hundreds or thousands of local decisions, often producing a system without a consistent overall direction. section 4.12
Organic growth creates recognizable tradeoffs:
- Preserves gradual delivery by allowing the system to respond to changing needs through incremental changes. section 4.12
- Accumulates ad hoc solutions that can leave the codebase inconsistent and difficult to guide. section 4.12
- Contrasts with controlled growth, where teams constrain what changes, decide where changes belong, and periodically review or rearrange the system. section 4.12
The public garden
Imagine a public garden where anyone can plant anything anywhere. It may become colorful, but it lacks harmony and guidance. A controlled garden limits what can be planted, places growth deliberately, and periodically reviews the arrangement. The contrast illustrates why organic growth can carry a negative connotation in software: accumulation alone does not provide direction. section 4.12
