How are spikes typically treated in demos?

• A. They are demonstrable and included in the demo.
• B. They are shown only to management.
• C. They are excluded from the demo.
• D. They replace user stories in the backlog.

Answer: (A)

Spikes are time-boxed investigations to answer unknowns or reduce technical risk, and the value they deliver is a tangible artifact—like a prototype, a design option, or validated feasibility. In SAFe demos, any outcome from a spike that can be demonstrated to stakeholders counts as demonstrable progress, so spikes are included in the demo to show how uncertainty was addressed and what was learned. This keeps the demo focused on working, visible progress rather than hiding investigation work. The other options don’t fit because spikes aren’t kept out of view, aren’t used to replace user stories, and aren’t inherently reserved for management—when a spike yields something tangible, it belongs in the demo to illustrate learning and risk reduction.