PMP Practice: Iteratively assess and prioritize risks

In agile environments, risks are assessed iteratively and just-in-time rather than through comprehensive upfront analysis. The spike story is the most appropriate agile practice here because it enables rapid learning and informed decision-making without disrupting the current sprint commitment. A spike is a time-boxed research activity that helps the team understand technical uncertainty before committing to implementation work. Since the API change happens in six weeks and integration is planned for Sprint 9 (approximately four weeks away), the team has a brief window to investigate options, assess feasibility, and adapt the backlog accordingly. This approach balances the urgency of understanding the risk with agile principles of empirical learning and just-in-time planning. The spike findings will inform conversations with the product owner about roadmap adjustments during backlog refinement, allowing the team to make evidence-based decisions rather than speculative ones. The scenario's closing fact that the team has never worked with this payment provider emphasizes the need for exploration before commitment, making investigation the clear priority.

**Why not A:** While risk assessment is important, immediately scheduling a workshop and updating a formal risk register reflects predictive project management practices rather than agile approaches. Agile teams integrate risk management into regular ceremonies like sprint planning, retrospectives, and backlog refinement rather than creating separate risk management events. Additionally, attempting to identify mitigation strategies before understanding the technical details through actual investigation would be premature and speculative.

**Why not C:** Creating a detailed risk management plan and freezing user stories represents an overly predictive response that contradicts agile values. Agile teams embrace change and uncertainty rather than seeking complete certainty before proceeding. Freezing stories would halt progress unnecessarily when investigation could quickly clarify options. The emphasis on documentation and escalation before exploration also reflects waterfall thinking where risks must be fully documented and approved before action, rather than agile's empirical approach of learning through experimentation.

**Why not D:** Waiting until Sprint 9 to assess the risk violates the principle of iterative risk assessment and wastes the team's advance warning. While agile teams avoid over-planning distant work, they do assess emerging risks that could affect near-term commitments. The team has a six-week warning about a change affecting work planned four weeks out—this is precisely when proactive investigation adds value. Agile responsiveness means acting on information as it becomes available, not ignoring known risks until they become immediate problems. The scenario specifically states the product owner needs to understand roadmap impacts, making waiting particularly inappropriate.