If we knew what we were doing, it wouldn’t be called research.
—Albert Einstein
Spikes
Note: This article is part of Extended SAFe Guidance and represents official SAFe content that cannot be accessed directly from the Big Picture.
Spikes are a type of SAFe Enabler Story. Defined initially in Extreme Programming (XP), spikes represent activities such as exploration, architecture, infrastructure, research, design, and prototyping. Their purpose is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate.
Like other stories, spikes are estimated, implemented and demonstrated. They also provide a mechanism and workflow that Agile Release Trains (ARTs) use to help determine the viability of Epics.
Details
Agile and Lean value facts over speculation. When faced with a question, risk, or uncertainty, Agile Teams conduct small experiments before moving to implementation rather than speculate about the outcome or jump to a Solution. Teams may use spikes in a variety of situations:
- Estimate new Features and Capabilities to analyze the implied behavior, providing insight into the approach for splitting them into smaller, quantifiable pieces
- Perform feasibility analysis and other activities that help determine the viability of Epics
- Conduct primary research to familiarize them with a new technology or domain
- Gain confidence in a technical or functional approach, reducing risk and uncertainty
Spikes may involve creating a small program, research activity, or test demonstrating new functionality.