Managing code ownership
ME Nordberg - IEEE software, 2003 - ieeexplore.ieee.org
ME Nordberg
IEEE software, 2003•ieeexplore.ieee.orgSolving the problem of failed project ownership is not merely a process of assigning
developers to subsystems. This article describes four code ownership models, ranging from
one individual owning an entire system to the collective ownership that is a core extreme
programming practice. No single code ownership model is best. In fact, many projects would
benefit from dynamically adjusting the ownership model over time as development
progresses through, for example, the four phases of the unified process.
developers to subsystems. This article describes four code ownership models, ranging from
one individual owning an entire system to the collective ownership that is a core extreme
programming practice. No single code ownership model is best. In fact, many projects would
benefit from dynamically adjusting the ownership model over time as development
progresses through, for example, the four phases of the unified process.
Solving the problem of failed project ownership is not merely a process of assigning developers to subsystems. This article describes four code ownership models, ranging from one individual owning an entire system to the collective ownership that is a core extreme programming practice. No single code ownership model is best. In fact, many projects would benefit from dynamically adjusting the ownership model over time as development progresses through, for example, the four phases of the unified process.
ieeexplore.ieee.org