(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
  5% (2)
• B
  12% (5)
• C
  5% (2)
• D
  79% (33)

Explanation

Note: The question asks to "Select 3," but the provided correct answer only lists two options (D, E). The third correct answer is almost certainly C - making the full correct answer C, D, and E.

Demoing a spike means demonstrating what the team learned, not shipping production code. A spike is a time-boxed investigation, so its output is knowledge - shown through the prototype built (D), quantitative data gathered (E), and the knowledge gained overall (C). These three forms of evidence answer the core question a spike addresses: "Is this approach feasible, and what will it cost?"

Why the distractors are wrong:

• A is incorrect because spikes do get demoed at the Sprint/Iteration Review - the team owes stakeholders transparency on what was learned, not just silence.
• B is incorrect because spikes are research activities, not production features; working code in production is the output of a story, not a spike.

Memory tip: Think of a spike demo as a science fair presentation - you show your experiment (prototype), your findings (data), and your conclusion (knowledge gained). You wouldn't ship a science fair project to production.

No community discussion yet for this question.