blob: 3e8478eb83e5c2d93be847a9c9da8fdfd4fed883 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="" xmlns:org.eclipse.epf.uma="" epf:version="1.0.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>&lt;a id=&quot;Prep&quot; name=&quot;Prep&quot;&gt;&lt;/a&gt;
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.
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.
&lt;br /&gt;
<purpose>&lt;a id=&quot;XE_implement_spike__activity_definition&quot; name=&quot;XE_implement_spike__activity_definition&quot;&gt;&lt;/a&gt;
Research a missing piece of information.