Collective Ownership

Correct Answer: Encourage those members who understand to communicate and share their knowledge with the rest of the team. Everybody should learn and contribute to the tricky part.

The concept of Collective Ownership in Agile and Scrum promotes that the codebase or the product is owned by the team as a whole instead of individual team members. The suggested approach implies that if a tricky part arises, the team members who understand it should communicate and share their knowledge with the rest of the team. This ensures learnings are shared across, fosters a collaborative team environment, and avoids silos of knowledge. This also is aligned with the principles of Agile that emphasize knowledge sharing, team collaboration, and continuous learning. The other responses all suggest a more siloed approach whether it be allowing only the members who understand to work on the part, hiring out the resolution, or waiting for only the team members who understand to resolve it in their spare time. These are all against the principles of Collective Ownership which promotes the whole scrum team's ability to make changes anywhere in the product.

Correct Answer: The team member should correct the bugs and on next meeting, inform the others about it to prevent such mistakes in the future.

In Agile and Scrum practices, developers practice collective ownership of the code. This means that everyone is responsible for the overall development and quality of the complete product, not just the pieces they directly worked on. Thus, if a team member finds a problem in the code, even if it isn't their own, they fix it themselves. This is efficient and encourages learning. The concept of Collective Ownership eliminates the 'not my job' attitude and encourages developers to take broader responsibility. The team member should inform the others about it in the next meeting to prevent such mistakes in the future. This action promotes collective learning and improvement in the quality of work. The idea is not to call out individual mistakes, but to learn from them and improve as a team, this clears, why other options like leaving the bugs for the colleague to correct, immediately confronting the colleague or reporting to the scrum master are not adhering to the principles of Scrum and Collective Ownership.

Correct Answer: Encourage the team to understand and make necessary changes to the code without fear, ensuring that changes are validated with adequate testing.

The practice of Collective Ownership, which is highly recognized in Scrum and Agile methodologies, suggests that the team members collectively own the product, which includes the code base. This means that anyone in the team should be able to work on, modify and enhance any part of the code, regardless of who initially wrote it. So, the best approach would be to encourage the team to understand and make necessary changes to the code without fear, ensuring that changes are validated with adequate testing. Asking the team to avoid touching the code contradicts the principle of Collective Ownership. Hiring a new senior developer might not be feasible or necessary, and doesn't encourage Collective Ownership. Deleting the code and starting over would be extreme and may not be needed, as understanding and enhancing the existing code could be more productive and less risky.