In 30 seconds
- No single person owns a module.
- Anyone can fix or improve any code.
- Needs good tests, standards and shared knowledge.
What it means
An Extreme Programming practice: the team owns the code together. If someone sees a problem anywhere, they can fix it without waiting for the "owner".
Why it helps
- No bottleneck when one person is busy or away
- Knowledge spreads across the team
- Quality improves because more people see the code
What it requires
- Automated tests to make changes safe
- Shared coding standards
- Pairing or reviews to spread knowledge
- Continuous integration to catch conflicts early
Myth vs reality
Myth · Collective ownership means nobody is responsible.
Reality · Everyone is responsible, together.
Myth · Anyone can change anything without care.
Reality · Changes still follow tests and reviews.
Myth · Experts become unnecessary.
Reality · Experts still guide; they just aren't gatekeepers.
FAQ
Does this work in large codebases?
Yes, usually scoped to the team's own services.
What about very specialist code?
Pair with the specialist to spread knowledge.
How do we start?
Rotate who works on which area and pair across areas.