During the implementation of a story, a scrum team notifies the scrum master of a technical challenge that is causing a delay. What should the scrum master advise the team to do?

Question

Options

• AImplement the story since the team is running behind schedule.
• BCreate a spike to finalize the story's technical approach.
• CTransfer the story to a scrum team experienced in solving similar problems.
• DAsk the product owner to reduce the story's priority and wait until more technical details are

• A
  7% (1)
• B
  71% (10)
• C
  7% (1)
• D
  14% (2)

Explanation

A spike is a time-boxed agile research task specifically designed to resolve technical uncertainty. When a story's technical approach is unclear or problematic, creating a spike allows the team to investigate, prototype, and determine the correct path before committing to full implementation. Option A (implement anyway) ignores the technical challenge and risks building the wrong solution. Option C (transfer to another team) is disruptive and not the standard response. Option D (reduce priority and wait) delays value delivery unnecessarily when a bounded investigation (spike) can resolve the uncertainty.

No community discussion yet for this question.