Ownership
Learn how different ownership models—collective, exclusive, and team—impact responsibility and trust in large Agile teams. Understand how these approaches facilitate collaboration, knowledge sharing, and effective artifact management, helping you make informed decisions on applying Agile ownership in complex projects.
We'll cover the following...
Trust and ownership
A typical agile team relies on trust in terms of ownership. This means that everybody on the team is responsible for all the artifacts, including code. There is no explicit ownership for any artifact, only trust in every team member taking his or her responsibility seriously. So, whenever an artifact needs to be changed for further improvement, everybody is able to do so.
This occasionally leads to arguments when introducing agile processes, even in small teams. With large teams, people usually claim that this is neither practical nor feasible.
Moreover, allowing everybody to change everything also helps to spread knowledge of the system, which helps ensure that everybody has the same understanding of it.
Different kinds of ownership
To further discuss the possibilities of ownership in a large team, let’s discuss the different kinds of ownership that can be established: