(Select 3) How do you demo a spike?

Question

Options

• ASpikes are strictly for internal learning of the team and do not need to be demoed.
• BShowing the functioning code in the production environment.
• CShowing the knowledge gained by the spike.
• DShowing a prototype produced for the spike.
• EShowing the quantitative data that will prove useful in developing future user stories.

• A
  6% (2)
• B
  16% (5)
• C
  77% (24)

Explanation

Demoing a spike is about sharing what was learned, not delivering a finished product. Options C, D, and E correctly capture the three valid outputs of a spike demo: the insights and knowledge the team gained (C), any prototype built to explore feasibility (D), and data gathered that will inform estimation or design of future stories (E). Together, these outputs justify the time invested in the spike and give the team the evidence they need to move forward confidently.

Why the distractors are wrong:

• A is incorrect because spikes are meant to be demoed - hiding the findings defeats their purpose of reducing uncertainty for the whole team.
• B is incorrect because spike work is exploratory and typically produces throwaway or prototype code, not production-ready software; deploying to production is the goal of regular stories, not spikes.

Memory tip: Think of a spike demo as a "show what you discovered" moment - Knowledge, Prototype, Data (C, D, E). If an answer describes shipping real production code or keeping things secret, it contradicts the transparency and learning purpose of a spike.

No community discussion yet for this question.