| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\xp\tasks\implement_spike.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: implement_spike.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,{85BE1C0E-F389-4246-BB22-9A52988018B7} CRC: 3859693007 -->Implement Spike<!-- END:presentationName,{85BE1C0E-F389-4246-BB22-9A52988018B7} --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-DbsgXRUjLhsnnpioGI2b3g CRC: 3266887289 --><a id="XE_implement_spike__activity_definition" name="XE_implement_spike__activity_definition"></a> |
| <ul> |
| <li> |
| Research a missing piece of information. |
| </li> |
| </ul><!-- END:purpose,-DbsgXRUjLhsnnpioGI2b3g --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_oCl4sGE-EdqnIZeW8YpHcA CRC: 2265408975 --> General <!-- END:name,_oCl4sGE-EdqnIZeW8YpHcA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_oCl4sGE-EdqnIZeW8YpHcA CRC: 319117512 --><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 /> |
| |
| </p><!-- END:sectionDescription,_oCl4sGE-EdqnIZeW8YpHcA --> |
| </body> |
| </html> |
