Question 1 of 21
During sprint planning, the team identifies that a critical API integration may not be available on time from a third-party vendor. What is the BEST way to handle this risk?
- A.Ignore the risk until the vendor confirms the delay — planning responses to unconfirmed third-party risks creates overhead without confirmed probability or impact data to justify the effort.
- B.Escalate to the product owner and halt sprint planning until the vendor confirms availability — committing to a sprint without resolving this dependency creates a commitment the team cannot reliably keep.
- C.Add the risk to the risk register, plan a mitigation strategy such as building a mock API, and add a contingency plan.
- D.Remove the integration story from the backlog until the vendor confirms availability — planning work with an unconfirmed external dependency creates a sprint commitment that cannot be reliably fulfilled.
Show answer and explanation
Correct answer: C
Proactive risk management requires documenting the risk, planning mitigation (e.g., mock API to continue development), and contingency if it materializes. Ignoring is passive acceptance with no plan. Stopping planning is an overreaction. Removing the story avoids the risk but delays value delivery unnecessarily.