Business analysis glossary
Spike
What it is
A spike is a timeboxed piece of research or experimentation used to answer a question or reduce uncertainty before the team commits to building something. Spikes can be technical, such as testing an API, or functional, such as exploring how users react to an idea. The output is knowledge, not production code.
Why it matters
When a story cannot be estimated because something important is unknown, guessing is risky. A spike buys the information cheaply and in a fixed time, so the team can then estimate and plan with confidence. Analysts often run functional spikes or support technical ones with business questions.
Example
Skylark Software wants to import tasks from spreadsheets but does not know how messy customer files are. The team runs a three day spike: the analyst collects twenty sample files and a developer tries to import them. The findings lead to clear rules for column mapping and error messages.