Agile promotes maintaining the integrity of the sprint commitment once it begins. According to the PMI Agile Practice Guide (Section 5.4: Sprint Planning and Managing Change), new requirements discovered mid- sprint should be added to the product backlog and reprioritized for a future sprint unless they are critical blockers.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 7: Problem Detection and Resolution) explains that backlog management is key to handling emerging work. Agile teams should not reactively shift focus, as it disrupts flow and predictability.
* Option B is correct: placing the new requirement in the backlog respects sprint boundaries and ensures proper prioritization.
* Option A disrupts sprint scope mid-course.
* Option C is unnecessary unless the issue is blocking progress.
* Option D violates the principle of sprint focus and planning discipline.

The correct answer is A - Add risk mitigation tasks to the backlog, then prioritize in current and upcoming sprints. In Agile, risk is actively managed and addressed as part of the backlog. When the risk threshold is exceeded, the team should explicitly identify risk-related tasks and bring them into visibility for planning and execution.
From the PMI Agile Practice Guide:
"Agile teams manage risk by incorporating risk mitigation tasks directly into the backlog and addressing them early. Risk exposure is reviewed frequently, and responses are prioritized based on value and urgency." (PMI Agile Practice Guide, Section 6.7 - Risk Management) Also from the PMBOK Guide (6th Edition):
"Risks should be integrated into project activities. Agile teams identify, analyze, and prioritize risks continuously and handle them as regular backlog items." (PMBOK Guide, Section 11.5 - Risk Response Planning) Mike Griffiths further supports this by noting:
"Agile teams track risks visually and use backlog prioritization techniques to ensure they're addressed appropriately." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 6 - Problem Detection and Resolution) Incorrect options:
* B suggests padding estimates, which is an anti-pattern.
* C is arbitrary and not recommended.
* D delays risk response and contradicts proactive risk management.

The correct answer is A - Capture risks and make them visible, and use a burndown chart to focus on reducing risks early in the project.
Technical uncertainty is a key area of risk in Agile projects. These risks should be clearly communicated, visualized, and prioritized early in the project to allow timely mitigation. Agile teams are empowered to make decisions and highlight blockers rather than delay work or seek hierarchical intervention.
PMI Agile Practice Guide states:
"Agile teams actively manage risk through transparency and continuous feedback. Risks should be made visible on information radiators and addressed early in the project to prevent impact on value delivery." (PMI Agile Practice Guide, Section 7.3 - Risk Management) Mike Griffiths adds:
"Teams facing uncertainty must surface risks openly and early. Using charts such as risk burndown and dashboards helps keep focus on managing these risks iteratively." (PMI-ACP Exam Prep, Chapter 6 - Problem Detection and Resolution) Incorrect options:
* B contradicts the time-boxing principle of sprints.
* C raises awareness but lacks proactive risk mitigation.
* D introduces a command-and-control dynamic, which is not agile.

The correct answer is D - The team should reevaluate time and cost estimates to reflect the latest understanding of the work effort.
Agile supports progressive elaboration and adaptive planning. When actual effort consistently exceeds estimates, it signals a need to recalibrate estimation practices. The team should revisit their velocity, estimation techniques, and potentially re-estimate upcoming work with improved understanding.
PMI Agile Practice Guide:
"Agile uses adaptive planning, where teams update estimates based on new information. This supports better forecasting and risk management." (PMI Agile Practice Guide, Section 5.3 - Estimation and Velocity) Mike Griffiths:
"Estimation accuracy improves over time. Agile teams regularly inspect estimation practices and adjust based on historical data and team maturity." (PMI-ACP Exam Prep, Chapter 5 - Adaptive Planning)
-

Agile roles are clearly defined to avoid overlap and confusion. According to the PMI Agile Practice Guide (Section 3.3 Agile Roles), the Product Owner is responsible for backlog prioritization and stakeholder communication, not managing team tasks. Task management is the domain of the self-organizing team and facilitated by the Scrum Master or Agile Project Manager.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement) reinforces that resolving role confusion through discussion helps realign expectations and improve team performance.
* Option C is correct: by clarifying roles and responsibilities, the agile project manager helps prevent overreach and ensures smoother collaboration.
* Option A addresses the issue too late and in the wrong forum.
* Option B misrepresents agile dynamics (self-organizing teams).
* Option D risks team morale and doesn't address the root cause.