spike report template

Spike Number:

Spike Title:

name of author
date

Goals / Deliverables

eg UML diagram, code, software comparison report

Technologies, Tools and Resources Used

eg nodejs, visual studio, gcc

Tasks Undertaken

eg (good)

• Downloaded and installed visual studio
• Compile sample source code

eg (bad)

• read source code
• Got bored while compiling

What we found out:

Describe what you discovered relating to the outcomes of the spike. Use screenshots, graphs, code examples etc. For code examples avoid screenshots and use the code tags.

Open issues/risks [Optional – remove heading/section if not used!]:

List the issues that you weren't able to solve. Or any new issues discovered. Eg Couldn't get X to work. Or Y worked but performance was not acceptable

Recommendations [Optional – remove heading/section if not used!]:

Indicate whether new spikes are required based on your findings. Or recommendations to continue.