blob: d1d3c3984b816e50200997e5de17756ff76bc863 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
xmlns:xmi="" xmlns:org.eclipse.epf.uma=""
xmlns:epf="" epf:version="1.5.0" xmi:id="-ykYi7xrRdC5O9qFXhU3doA"
name=",_xYMPoCZnEdyUaK463Ozu5g" guid="-ykYi7xrRdC5O9qFXhU3doA" changeDate="2007-06-29T12:33:38.823-0700">
With collective code ownership, any member of the team can change any piece of code in the system at any time. There&#xD;
should not be a policy or norm that one person is responsible for one part of the code base so that others are not&#xD;
allowed to modify it.&#xD;
Fostering an environment where any developer might be expected to modify any piece of code to implement some&#xD;
functionality, fix a bug, or improve the solution leads to a more collaborative team experience. Developers will become&#xD;
familiar with more of the code and benefit from the experience of others. It drives a high-performance team and removes&#xD;
hurdles so that changes can be made by those who need them when they need them. No one person can become the gatekeeper&#xD;
or bottleneck for changes to some subsystem within the code base.&#xD;
Collective code ownership works best if there are coding standards in place so that there are not problems, where one&#xD;
developer's style is significantly different than another's (see &lt;a class=&quot;elementLinkWithType&quot;&#xD;
href=&quot;./../../../openup/guidances/concepts/coding_standard.html&quot; guid=&quot;_0lnRMMqOEduwrYVlQ9zp3w&quot;>Concept: Coding&#xD;
Standard&lt;/a>). It is also critical that there are developer tests in place to ensure that work on a unit of code does&#xD;
not break it.&#xD;