The correct answer is A - Conduct frequent demos and obtain feedback from users throughout the development of the next release. Agile is feedback-driven. Regular demonstrations (e.g., sprint reviews) help gather customer input to continuously enhance the product and optimize value.
From the PMI Agile Practice Guide:
"Frequent demonstrations and validation with stakeholders ensure that teams deliver value continuously and adapt the product based on real-time feedback." (PMI Agile Practice Guide, Section 5.2 - Feedback and Product Review) Mike Griffiths notes:
"Customer feedback loops are vital to agile. Demos provide a mechanism for validating delivered functionality, identifying improvement opportunities, and maximizing product value." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* B contradicts continuous delivery and customer collaboration.
* C may help with scale, but doesn't directly address value improvement.
* D is more about process quality than business value.
####################################

The correct answer is B - Have team members work in pairs to learn from each other and develop new skills.
Pairing encourages collaboration, knowledge sharing, and skill development, which helps reduce dependency on specific individuals and enhances engagement through variety.
From the PMI Agile Practice Guide:
"Pair programming and other collaborative work methods help reduce repetition, promote learning, and improve motivation. These techniques allow for shared ownership and skill diversity." (PMI Agile Practice Guide, Section 4.3 - Continuous Learning and Team Development) Mike Griffiths adds:
"Cross-training and pairing reduce boredom, eliminate knowledge silos, and increase team flexibility. They are effective responses to reduced motivation from repetitive work." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 - Continuous Improvement) Incorrect options:
* A may temporarily help morale but doesn't address the root cause.
* C is more suitable for analyzing inefficiencies, not directly resolving monotony.
* D adds cost and doesn't solve the underlying engagement problem.

The correct answer is D - Set up a meeting with the stakeholder to modify the working agreement and ensure future engagement.
Agile values regular collaboration with stakeholders. When a stakeholder becomes disengaged, the first step is to address it through open communication and mutual agreement. Revisiting or modifying the working agreement helps reset expectations and reestablish commitment in a collaborative and respectful way.
From the PMI Agile Practice Guide:
"Agile teams work closely with stakeholders and set expectations through working agreements that are revisited and refined as necessary. These agreements include communication preferences and participation expectations." (PMI Agile Practice Guide, Section 4.2 - Stakeholder Engagement) Mike Griffiths reinforces this:
"Creating and maintaining stakeholder engagement requires ongoing alignment of goals and expectations.
When participation drops, revisit agreements and reset expectations collaboratively." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 3 - Stakeholder Engagement) Why the other options fall short:
* A may help short-term but doesn't address the root issue of misalignment or expectation gaps.
* B comes across as directive rather than collaborative.
* C escalates prematurely without attempting resolution directly with the stakeholder.
##################################################

The correct answer is C - Low-risk and low-value. Agile teams prioritize features that deliver the highest value earliest while also addressing risk. Features with low business value and low risk can be deferred as they contribute the least to business objectives and present no urgency.
From the PMI Agile Practice Guide:
"Agile teams maximize value by focusing on delivering high-value and high-risk features early. Low-value, low-risk items are often deferred or dropped entirely if they don't contribute meaningfully to customer outcomes." (PMI Agile Practice Guide, Section 3.4 - Prioritization Techniques) Mike Griffiths supports this:
"Features should be prioritized by value and risk. Items with low value and low risk are the lowest priority.
Delivering high-value features quickly enables feedback and learning."
(Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery)
Incorrect options:
* A should be prioritized early to mitigate risk and deliver value.
* B are non-critical and risky-often avoided or discarded.
* D delivers value, and therefore should be prioritized above low-value items.

The correct answer is D - Create a space on the board to prioritize the threats, along with an update on the actions that are in progress and what still needs to be done.
Agile promotes visual management and transparency. By using a dedicated section on the team board (information radiator), risks can be prioritized, tracked, and made visible to the entire team, enabling ongoing awareness and proactive response.
PMI Agile Practice Guide:
"Information radiators can be used to display risk burndown charts, prioritization, and mitigation plans, allowing teams to manage and address risk openly." (PMI Agile Practice Guide, Section 7.3 - Risk Management) Mike Griffiths:
"Making risks visible and tracking them alongside features fosters collective ownership and ensures proactive handling." (PMI-ACP Exam Prep, Chapter 6 - Problem Detection and Resolution) Incorrect options:
* A is reactive and lacks persistent visibility.
* B may create fatigue and be seen as micromanagement.
* C involves the sponsor unnecessarily and doesn't address day-to-day risk management.