The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
The unified software development process
The unified software development process
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Software Engineering Project Management
Software Engineering Project Management
Proceedings of the 2nd International Workshop on Emerging Trends in Software Metrics
On the difficulty of computing the truck factor
PROFES'11 Proceedings of the 12th international conference on Product-focused software process improvement
Hybrid Offshoring: Composite Personae and Evolving Collaboration Technologies
Information Resources Management Journal
| Hi-index | 0.00 |
Code ownership is more than simply assigning subsystems to individuals or subteams. This article identifies and describes four different code ownership models, ranging from one individual owning an entire system to the collective ownership that is a core practice of XP. Each ownership model has certain advantages and disadvantages or limitations. After listing these, the article proposes that the best way to gain the advantages of each and to avoid the disadvantages is to intentionally vary the code ownership model over a typical development project's lifetime. The four models correlate in an overlapping way with the four phases of the Unified Process. Dynamically assigned ownership has the potential to help balance a project's needs for communication, productivity, and accountability against its needs for single-minded vision, maintainable product quality, and manageable complexity.