| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-n52TyFa7Reb3LOJV1JMpvg" |
| name="pair_programming,3.876855509996079E-307" guid="-n52TyFa7Reb3LOJV1JMpvg" |
| changeDate="2006-11-09T19:16:04.083-0500" version="1.0.0"> |
| <mainDescription><a id="XE_xp__pair_programming" name="XE_xp__pair_programming"></a><a id="XE_pair_programming__practice_of" name="XE_pair_programming__practice_of"></a><a id="XE_engineering_practices__pair_programming" name="XE_engineering_practices__pair_programming"></a> 
 |
| <h3>
 |
| Description
 |
| </h3>
 |
| <p>
 |
| All production software in XP is produced by two programmers, sitting side by side, at the same machine. This practice
 |
| ensures that all production code is reviewed by at least one other programmer and results in better design, better
 |
| testing, and better code.
 |
| </p>
 |
| <p>
 |
| Research into pair programming shows that pairing produces better code in about the same time as programmers working
 |
| singly.
 |
| </p>
 |
| <p>
 |
| Pairing also serves to communicate knowledge throughout the team. As pairs switch, everyone gets the benefits of
 |
| everyone's specialized knowledge. Programmers learn, their skills improve, and they become more valuable to the team
 |
| and to the company.
 |
| </p>
 |
| <h3>
 |
| Benefits
 |
| </h3>
 |
| <ul>
 |
| <li>
 |
| Better design, code and tests.
 |
| </li>
 |
| <li>
 |
| Application and skill knowledge sharing across team.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Related Information
 |
| </h3>
 |
| <p>
 |
| See the <a class="elementLinkWithUserText" href="./../../../xp/guidances/guidelines/pair_programming-2.html" guid="3.85153041801319E-307">Pair
 |
| Programming Guidelines</a>.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
