Spike solutions are appropriate when:
A.
the business requirements are vague or inadequate for an iteration.
B.
a technology is understood well and has been used for a while, but needs a problem to be
debugged.
C.
there is insufficient time to refactor, but there is a need to resolve a specific problem.
D.
a specific technical
QUESTION needs to be answered, stopping work on the spike as soon
as it answers that question.
A spike solution, or spike, is a technical investigation. It’s a small experiment to research the answer to a problem. For example, a programmer might not know whether Java throws an exception on arithmetic overflow. A quick ten-minute spike will answer the question.
A spike solution is a very simple program to explore potential solutions. Build the spike to only addresses the problem under examination and ignore all other concerns. Most spikes are not good enough to keep, so expect to throw it away.
1
0