# Spike: Name ## Spike Plan Written by: ### Context What is the reason we need this spike? How did we get to this point in time? Why are we making a decision now? ### Goal What question(s) does the spike intend to answer? What work is the Spike enabling us to complete? Are we trying to reduce estimate variability (functional spike), increase confidence in a solution (technical spike), or both? ### Acceptance Criteria What are the required deliverables, other than the spike report? This could be a prototype, proof-of-concept, architectural diagram, a technical design doc, a work breakdown structure or almost anything else. #### Timebox How much time has been agreed upon for the spike to be completed? When does the spike *need* to be completed by? ### (Optional) Method/Resources If you, as lead, were to answer this question - what resources or methods would you use? This section is to assist junior team members, or team members with limited experience in completing spikes, in order to give them a leg up. ## Spike Report Completed by: ### Deliverables Link, or otherwise describe how to get any deliverables as described in the Acceptance Criteria. ### Method 1. What steps did the developer use? 2. In order to create the required deliverables 3. And achieve the goal 4. So another developer could reproduce the result 5. Provide links or notes about any resources used ### Findings * What are the facts that have been uncovered? * Reference other deliverables here * What's the (short) answer to the question? * Can we now set out to complete the work that the Spike was to unblock? ### (Optional) Recommendations * Are there multiple possible solutions? If so, the developer can weigh in here to discuss what they think the best one is. * If the spike hasn't fully unblocked the work, list out what the next spike(s) are in order to be able to start work. Ideally, provide the Spike Plan for any further (required) work * Are there any other open questions or concerns? This could be any investigation idea, even if it might end up as a lower priority. ## Presentation Once the spike has been completed, it should be presented to the stakeholders who are relying upon the information. ### Attendees * Lead * Producer * 1-3 colleagues ### Feedback Note any feedback regarding the spike ### Decisions Note any decisions made, based upon the spike's findings