| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="-DbsgXRUjLhsnnpioGI2b3g" |
| name="implement_spike,{85BE1C0E-F389-4246-BB22-9A52988018B7}" guid="-DbsgXRUjLhsnnpioGI2b3g" |
| version="1.0.0"> |
| <sections xmi:id="_oCl4sGE-EdqnIZeW8YpHcA" name=" General " guid="_oCl4sGE-EdqnIZeW8YpHcA"> |
| <sectionDescription><a id="Prep" name="Prep"></a> |
| <p> |
| A spike is an experiment. It helps the team find some bit of information it is missing in order to go forward. As such, |
| spikes are an important tool to minimize project risks. |
| </p> |
| <p> |
| Spikes are very often called for during the planning process when the team is unsure about how long particular stories |
| will take. In this case, the spike consists of trying out different ways of implementing the story. The team will do |
| the bare minimum to gain an understanding of how to do the story so that they can provide a reasonable estimate. Very |
| often, the code generated by spikes is literally thrown away. The value of the spike is in the information that was |
| missing, namely a good estimate in this case. |
| </p> |
| <p> |
| <br /> |
| &nbsp; |
| </p></sectionDescription> |
| </sections> |
| <purpose><a id="XE_implement_spike__activity_definition" name="XE_implement_spike__activity_definition"></a> 
 |
| <ul>
 |
| <li>
 |
| Research a missing piece of information.
 |
| </li>
 |
| </ul></purpose> |
| </org.eclipse.epf.uma:TaskDescription> |