The correct answer is C - Seek regular input from project stakeholders, and reflect this input in the backlog's priorities. Agile is a stakeholder-driven process, and backlog refinement should be informed by continuous feedback. The product owner maximizes value by regularly reviewing stakeholder needs and reprioritizing accordingly.
From the PMI Agile Practice Guide:
"The product owner is responsible for maintaining the backlog and ensuring it reflects stakeholder priorities.
Ongoing engagement with stakeholders ensures the product delivers maximum value." (PMI Agile Practice Guide, Section 5.2 - Product Backlog Management) Mike Griffiths adds:
"Agile product owners engage stakeholders continuously to update priorities and deliver value incrementally." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A is good practice but doesn't address the stakeholder engagement challenge.
* B confuses story size with business value.
* D lacks the agility required in a fast-moving project.

Step 1: Identify Remaining MVP Story Points
The backlog lists the MVP-related stories that are not yet started:
Accessibility - color blind # 4 story points
Increase security # 21 story points
Add AI chatbot # 5 story points

Total remaining MVP story points = 4 + 21 + 5 = 30
Step 2: Consider Velocity and Sprint Progress
The risk register mentions a reduction of 1 story point per sprint from sprints 4 through 6 due to the holiday schedule.

If we assume the team's normal velocity is 10 story points per sprint (hypothetically), it would drop to 9 story points per sprint for sprints 4-6.

Step 3: Calculate Completion Sprint
If the team normally completes 10 story points per sprint, they would require approximately 3 sprints (Sprint
7, Sprint 8, and Sprint 9) to complete the remaining 30 story points.

The correct answer is D - Engaged key stakeholders periodically to collect requirements.
Agile is based on frequent stakeholder collaboration. Continuous engagement ensures evolving needs are captured and prevents misalignment. Waiting for planning meetings or demos is too late to catch missing input.
PMI Agile Practice Guide:
"Agile teams ensure stakeholder engagement is ongoing throughout the project. This helps validate requirements and prevent surprises during reviews." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths:
"Stakeholders should be consulted early and often. Relying on static requirements leads to gaps. Agile teams maintain constant feedback loops." (PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A is too early and one-time.
* B may help but is reactive.
* C is a predictive approach inconsistent with agile.

The correct answer is C - Work with the team to create a solution for disseminating team knowledge throughout the company.
Agile values shared learning and continuous improvement. A lack of accessible organizational knowledge is a systemic issue. The agile practitioner should help the team implement lightweight, repeatable knowledge- sharing practices-such as wikis, communities of practice, or internal retrospectives.
From the PMI Agile Practice Guide:
"Organizational learning is an essential part of agile culture. Sharing information across teams enables continuous improvement and avoids repeated mistakes." (PMI Agile Practice Guide, Section 7.1 - Organizational Learning) Mike Griffiths adds:
"Coaching agile teams includes promoting knowledge sharing mechanisms across the organization. Practices like open reviews, documentation wikis, or retrospective reports can help teams learn from each other." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 7 - Continuous Improvement) Why the other options are incorrect:
* A suggests reporting but may become overhead without solving the core issue.
* B avoids organizational improvement by isolating the team.
* D brings in external help when the issue can be resolved internally.

The correct answer is D - Turn the requests into user stories and prioritize them. In agile, all feature requests must be expressed in the form of user stories and added to the product backlog. Once added, they are prioritized collaboratively with the product owner and stakeholders, usually based on value, risk, and effort.
From PMI Agile Practice Guide:
"Product backlog refinement includes breaking down large items into user stories, reprioritizing items, and ensuring they are properly understood by the team. This activity is critical in ensuring the right items are worked on at the right time." (PMI Agile Practice Guide, Section 5.2 - Product Backlog Refinement) From Mike Griffiths' PMI-ACP Exam Prep Book:
"Agile teams transform customer needs into user stories during backlog grooming. These are then prioritized by the product owner to ensure maximum value is delivered early." (Mike Griffiths, Chapter 3 - Value-Driven Delivery) Option A ignores customer needs. Option B (ordering by complexity) does not consider value. Option C skips the important step of converting feature requests into properly structured backlog items.