In Agile, the Definition of Done (DoD) typically requires that the feature be both developed and fully integrated into the release package before it is considered complete. Even though the feature was successfully tested and demonstrated by QA, if it is not included in the release package, it is not technically completed according to the DoD. Therefore, its story points should not be added to the burndown chart until it is actually part of the release. This ensures that the team's progress is accurately tracked based on completed, released work.

In Agile, estimates are initially based on previous experiences or expert opinions, but as the team progresses through sprints, they gain more insight into the project's actual complexity and the team's capacity. Agile estimates evolve over time based on the team's velocity, which reflects how much work the team can realistically handle. This is why the actual scope and timelines can differ from initial estimates. The agile lead should emphasize that the initial estimates were helpful for understanding feasibility, but the true estimates are refined continuously as the team gains more experience and understanding of the work, and as complexities or dependencies become clearer during each sprint.

The correct answer is B - The stakeholder who can prevent the project from achieving its goals.
Stakeholder prioritization is based on power and influence. Those who can significantly impact or block project success (positively or negatively) should be prioritized. This ensures their concerns are addressed and their support is cultivated early.
PMI Agile Practice Guide:
"Stakeholder engagement is critical in agile. The team must identify those who have the most influence over project outcomes and ensure early and frequent communication." (PMI Agile Practice Guide, Section 4.1 - Stakeholder Engagement) PMBOK Guide:
"Stakeholder prioritization involves assessing who has the greatest influence on project success."

The correct answer is B - Two-way communication.
Agile thrives on collaboration and transparency. In sprint planning, the product owner presents the business needs (via user stories), and the team responds with estimates and commitments. This mutual communication fosters alignment, shared understanding, and trust, which is characteristic of two-way communication.
PMI Agile Practice Guide:
"Agile projects rely on high levels of communication and collaboration, especially between the product owner and development team." (PMI Agile Practice Guide, Section 4.2 - Communications and Collaboration) Mike Griffiths:
"Two-way communication allows feedback and clarification. Sprint planning is a prime example where the PO and team interact to shape and commit to sprint goals." (PMI-ACP Exam Prep, Chapter 4 - Team Performance) Incorrect options:
* A refers to managing emotions, not communication style.
* C is unrelated to agile practice.
* D (reciprocal communication) is a less common term and not directly aligned with the scenario.

The correct answer is B - Review possible options and make an informed decision to cut losses based on delivered business value. In agile, decisions are continuously evaluated based on value delivery, inspect-and- adapt principles, and business justification.
From the PMI Agile Practice Guide:
"Agile projects emphasize delivering the highest value features early and frequently. When new information emerges-such as the high risk of failure of a critical feature-the product owner must evaluate the cost- benefit, assess remaining value, and make a business-based decision." (PMI Agile Practice Guide, Section 3.4 - Value-Driven Delivery)
"The agile mindset embraces failure as a learning opportunity but also encourages continuous evaluation of whether a project should continue. It is better to stop a project early based on value delivery assessments than to continue wasteful efforts." (PMI Agile Practice Guide, Section 2.3 - Fail Fast to Learn Quickly) Mike Griffiths' PMI-ACP Exam Prep Book notes:
"Agile teams reassess business value frequently. If remaining features do not justify additional investment due to technical, market, or cost concerns, the product owner may decide to stop the project and preserve resources. This decision should always be informed by the value already delivered versus expected benefits." (Mike Griffiths, Chapter 3 - Value-Driven Delivery) Why the other options are incorrect:
* A is a possible outcome, but prematurely terminating without analyzing value delivery is hasty.
* C (bringing in experts) may increase costs and still not solve the fundamental issue of failing value.
* D ignores the significance of the critical feature and assumes it can be deferred without impact-this may not be viable.