Skip to Content

Changes for page Collective Ownership

Last modified by chrisby on 2024/02/27 16:05
From version 1.10
edited by chrisby
on 2023/10/13 12:52
Change comment: There is no comment for this version
To version 1.11
edited by chrisby
on 2023/10/13 13:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,4 +4,8 @@
4 4  
5 5  * **Improved Team Unity**: Eliminates factions and hierarchy.
6 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.
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.
8 +
9 +### Example
10 +
11 +A backend specialist may be responsible for a story that requires both frontend and backend changes. Ideally, the backend specialist will have enough general knowledge to solve the task on his own, but if not, he should be paired with a frontend specialist to solve the problem and expand his front-end knowledge. If the task is still too complex or difficult, the next options might be to reassign the task to another developer or get help from the team, and this decision should be made transparently and collaboratively by the team.