Code Ownership

We do not practice code ownership. When the classes for some feature are first developed, only one team will typically work on them, during the one iteration it takes to develop them initially.

Thereafter, whenever any team has occasion to work with a class, whether to extend it or repair it, they do so freely. Because we release frequently, there are few conflicts. We have extended ENVY to warn us when we version a class that is not based on the released, and when it does, we integrate our changes into the released version if that isn’t the one we started with. (The team who released ahead of us will help us if we need it.)

On the contrary, lack of ownership might cause people to feel less responsible for their work.

On the contrary, the non-owner might not understand the class and break it.

1997, 1998, Ronald E Jeffries