Collective Code Ownership
A collaboration practice that speeds delivery by allowing any team member to change any project artifact or deliverable, reinforcing shared responsibility and accountability across the whole team.
Key Points
- Anyone on the team can modify any code, document, or work product when it benefits the project.
- Eliminates bottlenecks and single points of failure; work does not wait for the original author.
- Relies on standards, tests, peer review, and continuous integration to safeguard quality.
- Promotes shared ownership and collective accountability for outcomes.
Example
Mid-sprint, a developer finds a security issue in a service they did not write. They implement the fix, add unit and integration tests, run the CI pipeline, and merge the change after peer review, without needing to hand the task back to the original author.
PMP Example Question
During a sprint, a tester notices a minor bug in a component they did not build. To avoid delay, they implement the fix and add tests before merging. Which practice does this illustrate?
- Individual code ownership
- Collective code ownership
- Formal change control board approval
- Component stewardship
Correct Answer: B — Collective code ownership
Explanation: Collective code ownership authorizes any team member to change any work product, accelerating delivery while maintaining shared accountability.
