Skip to content

SAFe Spikes

Source identity:

ddx:
  id: resource.safe-spikes

SAFe Spikes

Source

Summary

Scaled Agile describes spikes as small experiments used when a team faces a question, risk, or uncertainty before implementation. Spikes may use research, prototyping, feasibility checks, or technical evaluation. Their output is knowledge that helps teams choose an approach, split work, size work, or reduce risk.

Relevant Findings

  • Spikes should be used for real uncertainty, not routine delivery work.
  • A spike can be technical or functional, but it should answer a bounded question.
  • Spike output should be demonstrable and acceptable even when it is knowledge rather than shippable code.
  • A spike should gather only enough information to choose the next step or select a technical approach.
  • Frequent spikes can indicate unresolved uncertainty that should be made visible instead of hidden inside delivery plans.

HELIX Usage

This resource informs the Technical Spike artifact. HELIX uses it to keep spikes time-boxed, evidence-producing, and decision-oriented.

Authority Boundary

This resource explains spike practice in SAFe. It does not replace HELIX architecture, ADRs, proof-of-concept artifacts, or implementation plans.