Wiki source code of Collective Ownership
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | Code is collectively owned. Any developer can change any module at any time. | ||
2 | |||
3 | ### Benefits | ||
4 | |||
5 | * **Improved Team Unity**: Eliminates factions and hierarchy. | ||
6 | * **Reduces Duplication**: Shared logic between different modules in the project through shared access. | ||
7 | * **Balancing Specialization & Generalization**: While specialization increases productivity in a specific area, generalization fosters growth in technical knowledge and team support. Aim for a balance between the two. For example, a backend specialist may be responsible for a story that requires changes in both the frontend and backend. Ideally, the general knowledge is broad enough to solve the task on his/her own, but if not, [[pairing up|doc:Software Engineering.Agile.Extreme Programming.Pair Programming.WebHome]] with a frontend specialist can be done to solve the problem and expand frontend knowledge. |