The correct answer is C - Facilitate a retrospective to identify areas of improvement.
In Agile, mistakes are viewed as learning opportunities. The Scrum Master should create a safe environment where the team can reflect, discuss issues openly, and identify ways to prevent similar mistakes in the future.
From the PMI Agile Practice Guide:
"Retrospectives provide a regular forum for teams to inspect and adapt. Teams discuss what went well, what didn't, and how to improve. This supports continuous learning and performance enhancement." (PMI Agile Practice Guide, Section 3.5 - Iteration Retrospectives) Mike Griffiths states:
"Mistakes are inevitable; agile teams embrace them to improve. Retrospectives are essential for structured reflection and action planning." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 - Continuous Improvement) Why other options are less appropriate:
* A may reinforce outdated or flawed processes.
* B may help in quality control but does not address the mistake constructively.
* D promotes fear and competition, which undermines team trust and collaboration.

Step 1: Identify Total Story Points in the Backlog
From the backlog table:

Total story points = 6 + 4 + 8 + 4 + 21 + 7 + 5 + 9 + 3 + 5 = 72
Step 2: Determine the Team's Velocity
The risk register mentions a burn reduction of 1 story point per sprint from sprint 4 to sprint 6 due to a holiday schedule. However, assuming a normal velocity of 5 story points per sprint, we can estimate sprint completion.
Normal sprint velocity: 5 story points per sprint
Reduced velocity for sprints 4-6: 4 story points per sprint
Step 3: Calculate Total Sprints Needed
First 3 sprints: 5 points per sprint # 5 × 3 = 15 story points completed

Sprints 4-6: 4 points per sprint # 4 × 3 = 12 story points completed

Remaining story points after sprint 6: 72 - (15 + 12) = 45 story points

Remaining sprints needed at normal velocity (5 story points per sprint): 45 ÷ 5 = 9 sprints

Total Sprints Required
Sprints 1-6: Already planned.

Additional 9 sprints needed.

Total sprints to complete the backlog: 6 + 9 = 15 sprints.

The correct answer is A - Conduct a requirements gathering workshop.
In Agile, workshops such as story-writing or backlog refinement sessions help the team and stakeholders collaboratively explore requirements. These sessions are interactive and iterative and allow for joint discovery, prioritization, and clarification of user needs.
PMI Agile Practice Guide:
"Collaborative workshops enable teams to gather requirements and clarify expectations in an iterative fashion.
They engage stakeholders in prioritizing and decomposing work into user stories." (PMI Agile Practice Guide, Section 5.2 - Backlog Refinement) Mike Griffiths writes:
"Workshops are a key practice for backlog development. They are particularly useful when initiating complex projects with minimal requirements, allowing the team to iteratively develop stories with stakeholders." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* B assumes delivery before refinement, risking misalignment.
* C places the burden on the product owner alone.
* D is waterfall-oriented and contradicts iterative backlog evolution.

The correct answer is C - Update current user stories.
Acceptance criteria are part of a user story's definition and describe the specific conditions under which the story is considered complete. As user stories evolve and more clarity is gained, acceptance criteria must be updated within the user story itself to ensure mutual understanding of scope and expectations between the product owner and the development team.
According to PMI Agile Practice Guide:
"Acceptance criteria are detailed during backlog refinement and are commonly added to user stories to define the done conditions. These are updated throughout the lifecycle of the story as more details emerge." (PMI Agile Practice Guide, Section 5.2 - Backlog Refinement) Mike Griffiths reinforces this:
"Acceptance criteria serve as the test conditions for confirming user stories. They are not fixed and can be elaborated collaboratively during grooming or development, and are updated directly in the user story." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Other options:
* A refers to adding more stories, not updating existing ones.
* B (retrospectives) are used for process improvement, not for editing user stories.
* D (project plan) reflects a traditional mindset and not applicable in Agile.

The correct answer is D - Facilitate a team retrospective.
A drop in team morale and performance signals the need for a structured conversation where the team can reflect, diagnose root causes, and propose changes. Retrospectives are the Agile mechanism for identifying and addressing performance issues in a collaborative, non-blaming environment.
PMI Agile Practice Guide:
"Retrospectives allow teams to reflect on their performance, discuss what's working or not, and commit to improvement actions. This is the key mechanism for continuous team development." (PMI Agile Practice Guide, Section 5.8 - Retrospectives) Mike Griffiths affirms:
"Team disengagement often stems from unresolved issues or lack of empowerment. Retrospectives are critical for rebuilding engagement, trust, and improving team dynamics." (PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A skips team-level resolution and risks undermining trust.
* B manipulates metrics without solving the root problem.
* C is useful for daily progress updates but not for deep reflection.
-