About airfocus

Try for free

Spike in Agile


What is a spike in Agile?


Agile Spike Definition

Agile spikes are used during product development as a means to explore solutions for a user story for which the team cannot yet estimate a timeline.

When a team needs more information to develop a feature, a spike allows them to develop the means and methodology first, before committing to a defined user story. How product teams use the time provided by the spike is up to them, but most product managers will explore either technical solutions (the nuts and bolts of developing a feature) or functional solutions (how the feature will impact the final product or align to the product vision). 

Why use spikes in Agile?

Generally speaking, a product development team will use spikes in Agile as a tool to crystallize requirements going forward. The common rationale for the use of a spike is that there are competing solutions for a particular feature. For the team to choose the right path in developing this feature, a spike is deployed as a user story in the roadmap and the time used for developing, testing, and finalizing solutions.

How long is an Agile spike?

There’s no right or wrong amount of time for an Agile spike to take — it all depends on the project. That said, “timeboxing” is one of the key concepts behind the use of spikes in Agile.

Because Agile spikes are designed to break a problem down into smaller stories using research and testing, it can be tempting for a team to dive a little too deep into a solution, which may take time away from the rest of the roadmap. 

Timeboxing Agile spikes helps product teams stay focused on the end goal and not spend too much time over-engineering solutions for a singular user story — no matter how important the feature may be.


Agile: Best Practices and Methodologies

Read now
CTA eBook image background
airfocus eBook Agile: Best Practices and Methodologies

Spike Agile

General FAQ

What are spikes in Agile?
An Agile spike is a time-boxed story used to identify the ideal approach to developing a particular feature, as opposed to actively developing the feature. Spikes are used when multiple methods might be relevant to solve the same story.
Can I use multiple Agile spikes for one story?
As many spikes as necessary can be used to identify the ideal approach to developing a particular feature. Each spike can be tailored to different fact-finding activities, such as isolating possible solutions, testing them, and finalizing the chosen methodology.
How often should we be doing spikes?
There are no hard and fast rules about how often product teams should deploy Agile spikes. But if they find themselves disagreeing on a particular feature or solution, spikes can be a time-saving answer — getting straight to possible solutions faster.
airfocus eBook Agile: Best Practices and Methodologies
Agile: Best Practices and Methodologies
Read now

Experience the new
way of doing product

Try for free

Book a demo

airfocus modular platform
Top rated
on major review platforms
g2 badge users love us
g2 badge leader fall
GetApp badge category leader
software advice badge
capterra shortlist badge
proddy badge roadmapping
crozdesk badge
All rights reserved.