| <?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.3/uma.ecore" epf:version="1.0.0" xmi:id="-DoLoZOTPa_LacQ3jUG_lsg" name="xp_sustainable_pace,3.133529870649493E-306" guid="-DoLoZOTPa_LacQ3jUG_lsg" changeDate="2006-11-09T15:07:23.389-0800" version="1.0.0"> |
| <mainDescription><a id="XE_xp__sustainable_pace" name="XE_xp__sustainable_pace"></a><a id="XE_sustainable_pace__practice_of" |
| name="XE_sustainable_pace__practice_of"></a><a id="XE_engineering_practices__sustainable_pace" |
| name="XE_engineering_practices__sustainable_pace"></a> |
| <h3> |
| Description |
| </h3> |
| <p> |
| The assumption in XP is that software development is not a sprint but a marathon. While a sprinter will easily beat a |
| marathon runner over a very short distance, the marathon runner will always win in the long run. Consistently working |
| overtime will destroy the team, the design, and eventually the product. It creates an environment that makes it |
| impossible to do high quality work. People make more mistakes because they are tired (not to mention their low morale), |
| causing bugs that require a lot of time to fix down the line. The end result is that it slows everything and everyone |
| down. |
| </p> |
| <p> |
| Continuous overtime can be a symptom of a deeper problem that is not being addressed. Perhaps the process is too broken |
| to be fixed by working more. The rule in XP is that, if the team has to do more than one consecutive week of overtime, |
| it should reassess the situation and start rethinking the plan. Overtime is OK if you need to get to the end of an |
| iteration or a release, but it should always be an exception rather than the rule. |
| </p> |
| <p> |
| Sustainable pace is about fostering a team that can produce a consistent amount of work over a long period of time. |
| </p> |
| <h3> |
| Benefits |
| </h3> |
| <ul> |
| <li> |
| <b>Improved predictability</b>: plans become more accurate. |
| </li> |
| <li> |
| <b>Improved product quality</b>: programmers have the time to do the right thing. |
| </li> |
| <li> |
| <b>Improved job satisfaction</b>: programmers can enjoy their work with as little stress as possible. |
| </li> |
| <li> |
| <b>Reduced time to market</b>: less time required to fix bad code and rotting design.<br /> |
| <br /> |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |