Spikes are investigative stories for learning, risk reduction, or decision-making. Although spikes may not always yield production code, they produce valuable artifacts or insights. Demoing a spike involves sharing:
Knowledge gained (C)
Prototypes produced (D)
Quantitative data gathered (E)
These outputs support transparency and future development. Spikes should always be demoed as part of the team’s continuous learning.
“Demoing a spike means presenting what was learned, prototypes built, and/or data collected. This demonstrates value to the team and stakeholders, even without production-ready code.”
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit