The correct answer is A - Kaizen. Kaizen is a Japanese term meaning "continuous improvement." In Agile, Kaizen refers to the practice of regularly reflecting on processes and results, then making incremental improvements. By tracking impediments and resolving them transparently, the team engages in Kaizen behavior.
From the PMI Agile Practice Guide:
"Agile teams embrace a mindset of continuous improvement (Kaizen), regularly inspecting their work and processes and adapting them for better outcomes." (PMI Agile Practice Guide, Section 6.6 - Continuous Improvement) Mike Griffiths writes:
"Agile is rooted in lean thinking, including Kaizen. Teams reflect on what went well and what needs to change, often using tools like Kanban boards to visualize and track improvements." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 7 - Continuous Improvement) Incorrect options:
* B refers to goal-setting, not process improvement.
* C are metrics, not an outcome of experimentation.
* D (Muda) refers to waste, which Kaizen seeks to reduce.

In Scrum, theproduct owneris the primary point of contact betweenstakeholders and the development team
. According to thePMI Agile Practice Guide (Section 3.3: Roles and Responsibilities), the Scrum Master ensures thatcommunications flow properlyand protects the team from distractions.
Mike Griffiths in thePMI-ACP Exam Prep Book (Chapter 4: Stakeholder Engagement)emphasizes the importance of having asingle point of contactfor stakeholder feedback to avoid miscommunication and overload.
* Option Ais correct: redirecting communication through the product owner keeps the team focused and the backlog structured.
* Option Bis unprofessional and discourages stakeholder engagement.
* Option Cbypasses review and prioritization-backlog management should be intentional.
* Option Dcould blur roles and bypass proper channels.

The correct answer is B - Evaluate the impact of the change request and let the team and Product Owner decide and reprioritize based on value. Agile allows for mid-iteration changes only in exceptional cases where business value is at risk. Such changes must be evaluated collaboratively.
From the PMI Agile Practice Guide:
"Agile teams may allow scope changes mid-iteration if the benefit clearly outweighs the cost. In such cases, the Product Owner and team collaboratively assess and decide whether to accommodate the change." (PMI Agile Practice Guide, Section 5.2 - Iteration Planning and Scope Flexibility) Mike Griffiths also explains:
"While mid-iteration changes are discouraged, if the change is critical to business value, the team and Product Owner may replan collaboratively. Agile encourages flexibility with customer-focused decision-making." (Mike Griffiths, PMI-ACP Exam Prep, Chapter 3 - Value-Driven Delivery) Incorrect options:
* A and D bypass collaborative evaluation.
* C is too extreme for a small but valuable change.

The correct answer is D - Create a risk burndown chart showing the reduction of risks over time.
In Agile, risk management is integrated into each iteration. A risk burndown chart is a visual information radiator that tracks the total risk exposure and how it changes over time, making risk transparent and easy for the team to understand.
From the PMI Agile Practice Guide:
"A risk burndown chart can be used to communicate the decreasing level of project risk over time and encourage discussion on risk mitigation strategies." (PMI Agile Practice Guide, Section 6.4 - Risk Management) Mike Griffiths also states:
"Agile teams use tools like risk burndown charts to visualize risks and track mitigation. They provide real- time understanding of current and remaining risks." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 6 - Problem Detection and Resolution) Other options:
* A is a responsibility assignment matrix (not risk-focused).
* B and C are traditional (predictive) methods and don't align with Agile risk communication.

The correct answer is B - Recommend an Agile delivery approach and provide information to the stakeholders on Agile values and principles.
Agile enables early and continuous delivery of valuable software, short feedback loops, and faster time to market. When competitive advantage and speed are critical, introducing Agile principles allows the organization to remain flexible, respond to change, and deliver increments faster.
From the PMI Agile Practice Guide:
"Agile approaches provide quicker feedback, faster time to market, and more opportunity to deliver business value early. They are ideal in dynamic environments with evolving customer needs." (PMI Agile Practice Guide, Section 1.3 - When to Use Agile) Mike Griffiths states:
"Agile emphasizes early and continuous delivery, allowing organizations to test, learn, and adjust quickly to changes-critical for achieving business agility and competitive advantage." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 1 - Agile Mindset) Why other options are not optimal:
* A suggests a predictive mindset and planning before implementation.
* C focuses only on Scrum roles, which may be too narrow for organizational-level change.
* D relies on traditional governance structures that may resist Agile change.