During a backlog refinement meeting, a senior team member raises a concern about an epic sizing that requires the use of a new interface for a vendor product. The product owner acknowledges this as…

Question

Options

• ALog the risk in the risk register, and share the information with impacted stakeholders at the next
• BCreate a spike story to determine what needs to be done to use the new interface.
• CLower the epic's priority so that it can be deferred, and analyze it during backlog refinement
• DMove the work to the vendor, since they have better knowledge of interface implementation.

• A
  4% (1)
• B
  81% (22)
• C
  4% (1)
• D
  11% (3)

Explanation

A spike story is the agile mechanism specifically designed to address uncertainty and technical risk - it is a time-boxed investigation to gain the knowledge needed to estimate or implement a feature. Option B is correct because creating a spike allows the team to research the new vendor interface, reduce the unknown, and arrive at a more accurate estimate before committing to the full epic. Option A (logging the risk and sharing it later) is passive and delays action. Option C (lowering priority to defer) avoids the risk rather than addressing it. Option D (moving work to the vendor) is inappropriate - it transfers responsibility without ensuring the team understands the interface they will ultimately need to work with.

No community discussion yet for this question.