Spike: The Agile Team’s Secret Weapon for Uncertainty & Flow
When Agile teams face unknowns: technical challenges, architectural decisions, or research-heavy tasks, they use a Spike. But what exactly is a Spike, and why is it critical to Agile execution?
What is a Spike?
A Spike is a type of Enabler used to explore an unknown before committing to full implementation. As the name implies, Enablers enable future feature functionality. It allows teams to experiment, reduce risk, and gain insights needed to move forward confidently. “Spike” originated from Extreme Programming (XP) as a metaphor for driving a spike into a problem to explore and uncover unknowns. Spikes have since been adopted in Scrum and SAFe®.
Where Do Spikes Fit?
A Spike falls under Exploratory Enablers, one of the four types of Enablers:
1. Architectural Enablers: Support foundational architecture and technical decisions.
2. Exploratory Enablers (“Spikes”): Reduce uncertainty through research, prototyping, or technical validation.
3. Infrastructure Enablers: Set up or improve the system’s operational capabilities.
4. Compliance Enablers: Ensure regulatory, security, or legal requirements are met.
What Are Enablers Used For?
Enablers provide the technical foundation for Agile teams to:
• Break dependencies by addressing risks upfront.
• Improve technical execution by supporting infrastructure, architecture, or compliance needs.
• Reduce uncertainty by validating assumptions before implementation.
Where Do Enablers Reside?
Enablers exist at all levels of scales Agile execution:
• Portfolio Level: Large-scale architectural work or compliance requirements.
• Program Level: Solution-wide technical initiatives impacting multiple teams.
• Team Level: Research or technical work enabling feature development.
How Do Enablers Differ from User Stories?
Unlike User Stories, which deliver direct user value, Enablers support delivery by enabling future work. A User Story might say, “As a Propulsion Scientist, I want to upload files to AI-bot so that it provides context for extracting insights. A Spike might be, “Investigate the best file storage solution for compliance.” No “persona” is needed for an Enabler because it is not providing direct user value; however, both have Acceptance Criteria as conditions of satisfaction.
Are Enablers Story Pointed?
We won’t debate this point here, but since Enablers consume capacity, “Yes.” Like User Stories, Enablers are relative-size estimated and prioritized in the backlog. A Spike’s goal is to provide just enough knowledge to move forward with emergent development, so time-boxing within a Sprint is essential.
Who Writes Enablers?
Enablers can be written by:
• Architects: For system design, infrastructure, or security needs.
• Developers: When technical uncertainty needs research.
• Scrum Masters/Coaches: To address Agile process challenges.
• Anyone.
The Bottom Line
Spikes empower Agile teams to tackle the unknown, ensuring smoother execution and breaking dependencies before they become blockers that impede flow. They’re not just technical tasks; they’re strategic investments in faster, more effective delivery.