This concept departs from traditional approaches where a piece of code is owned by an individual or a subset of the team. In a Scrum Team, the code is owned by the team collectively. This practice enables any team member to make changes in any part of code base, thus leads to faster bug fixes, code…This concept departs from traditional approaches where a piece of code is owned by an individual or a subset of the team. In a Scrum Team, the code is owned by the team collectively. This practice enables any team member to make changes in any part of code base, thus leads to faster bug fixes, code reviews and enables more fearless refactoring. At any given point of time, this approach ensures no one person alone becomes the bottleneck because they own part of the codebase absolutely.
Guide to Collective Code Ownership - PSM I
What is Collective Code Ownership? Collective Code Ownership is a principle in Agile and Scrum methodologies. It essentially means that code is not owned by an individual but by the entire team. Every team member has full access to the codebase and can make changes as required.
Why is it Important? Collective Code Ownership promotes shared knowledge of the code among the team, ensuring there are no knowledge silos based on individual ownership of code modules. Consequently, the application can evolve quickly and without ‘waiting time’ for a certain developer. This improves team productivity and project velocity.
How it Works? Any team member can modify any system part, although the developers are expected to communicate, collaborate and respect other team members' changes. This promotes shared understanding of the code and minimizes the risks associated with developer absence.
Exam Tips: Answering Questions on Collective Code Ownership 1. Understanding the Concept: Make sure you understand the basic principle of Collective Code Ownership; that code isn’t owned by an individual but by the whole team. 2. Implications: Understand the implications of Collective Code Ownership - how it dissolves knowledge silos, improves productivity and facilitates faster decision making. 3. Application: Be prepared to discuss how Collective Code Ownership is implemented, in terms of team interaction and respect for each other's work. 4. Avoid Pitfalls: Be aware of potential misconceptions; Collective Code Ownership is not a reason for avoiding individual responsibility or accountability. While the codebase is open to all team members, it is vital to maintain quality and not undermine the code structure or integrity.
PSM I - Collective Code Ownership Example Questions
Test your knowledge of Collective Code Ownership
Question 1
A new developer is struggling to grasp the project's overall structure and codebase, and is afraid to make changes. How can the Agile team handle this?
Question 2
A team member is unwilling to contribute to code review and pair programming activities. What should the team do?
Question 3
A team member completed a task from another team member and made some improvements to the code. The original developer wants to discuss these changes. What should the project lead do?
🎓 Unlock Premium Access
Professional Scrum Master I + ALL Certifications
🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
2149 Superior-grade Professional Scrum Master I practice questions
Unlimited practice tests across all certifications
Detailed explanations for every question
PSM I: 5 full exams plus all other certification exams
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!