| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-ykYi7xrRdC5O9qFXhU3doA" |
| name=",_xYMPoCZnEdyUaK463Ozu5g" guid="-ykYi7xrRdC5O9qFXhU3doA" changeDate="2008-08-06T15:25:38.875-0700" |
| version="7.2.0"> |
| <mainDescription><p>
 |
| With collective code ownership, any member of the team can change any piece of code in the system at any time. There
 |
| should not be a policy or norm that one person is responsible for one part of the code base so that others are not
 |
| allowed to modify it.
 |
| </p>
 |
| <p>
 |
| Fostering an environment where any developer might be expected to modify any piece of code to implement some
 |
| functionality, fix a bug, or improve the solution leads to a more collaborative team experience. Developers will become
 |
| familiar with more of the code and benefit from the experience of others. It drives a high-performance team and removes
 |
| hurdles so that changes can be made by those who need them when they need them. No one person can become the gatekeeper
 |
| or bottleneck for changes to some subsystem within the code base.
 |
| </p>
 |
| <p>
 |
| Collective code ownership works best if there are coding standards to prevent one developer's style from being
 |
| significantly different than another's (see <a class="elementLinkWithType" href="./../../../core.tech.common.extend_supp/guidances/concepts/coding_standard_1FF691E0.html" guid="_aGqAsJ01EdyQ3oTO93enUw">Concept: Coding Standard</a>). It is also critical that there are developer tests in
 |
| place to ensure that work on a unit of code does not break it.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
