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 A - Plan activities that will require the team to work collaboratively on a regular basis.
Agile teams thrive on collaboration, shared ownership, and collective problem solving. While individual performance may meet goals short-term, long-term value and quality come from integrated teamwork. An agile practitioner should help foster collaboration through team-building activities or practices like pair programming, collective backlog grooming, and swarming.
From the PMI Agile Practice Guide:
"Agile teams are self-organizing and collaborative. Encouraging collaborative practices builds trust, increases quality, and improves alignment." (PMI Agile Practice Guide, Section 4.1 - Building Agile Teams) Mike Griffiths states:
"Collaboration does not happen automatically-it must be supported. Facilitating shared work and group problem-solving leads to stronger team dynamics and better outcomes." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance) Why the other options are less effective:
* B introduces rigid evaluation that contradicts agile values.
* C bypasses coaching and assumes the current team can't improve.
* D ignores the growing problem of misalignment and disengagement.

The correct answer is A - Use an information radiator to help increase the transparency of work for key stakeholders.
Information radiators (such as Kanban boards, burndown charts, and story maps) make work status visible to the entire team and stakeholders in real-time, improving communication without additional meetings or reporting overhead.
From the PMI Agile Practice Guide:
"Agile teams use information radiators to promote transparency, show progress, and increase stakeholder engagement without adding administrative burden." (PMI Agile Practice Guide, Section 3.5 - Information Radiators) Mike Griffiths confirms:
"Effective agile environments display work status where everyone can see it. Visual indicators allow stakeholders and team members to remain informed without direct queries." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 5 - Agile Monitoring and Control) Other options explained:
* B creates unnecessary manual effort.
* C may disrupt team rhythm; daily stand-ups are sufficient in Scrum.
* D encourages siloed behavior and contradicts collaboration.

The correct answer is A - Perform value stream analysis to eliminate the processes with wastage. Value stream mapping is a lean and agile technique used to identify and eliminate non-value-adding activities, optimize flow, and increase delivery efficiency-especially crucial when facing tight deadlines.
From PMI Agile Practice Guide:
"Value stream mapping is used to analyze the flow of materials and information required to bring a product or service to a consumer. It helps teams eliminate waste and improve speed and quality." (PMI Agile Practice Guide, Section 6.4 - Continuous Improvement and Feedback Loops) From Mike Griffiths' PMI-ACP Exam Prep Book:
"Value stream analysis is a lean technique that helps agile teams identify delays, bottlenecks, and handoffs that waste time. When velocity lags behind expectations, understanding the end-to-end process is essential to improvement." (Mike Griffiths, Chapter 7 - Continuous Improvement) Option B (removing high-risk stories) may introduce more long-term risk and undermine value.
Option C suggests manipulating metrics instead of addressing root causes.
Option D may help identify risks early, but it doesn't address why velocity is low.

The correct answer is D - Iteration Burndown Chart.
An iteration burndown chart provides daily updates about the team's progress during an iteration (or sprint). It tracks the remaining work in the sprint backlog and helps both the team and stakeholders assess if the sprint goal is likely to be met. This visualization helps communicate real-time progress to key stakeholders and supports adaptive planning.
PMI Agile Practice Guide states:
"Burndown charts display work remaining in a timebox and are updated daily. They are effective for communicating iteration progress to the team and stakeholders." (PMI Agile Practice Guide, Section 5.6, Information Radiators) PMBOK Guide (6th Edition) and Mike Griffiths both emphasize using task boards and burndown charts as
"information radiators" for transparency.
Mike Griffiths' PMI-ACP Exam Prep Book elaborates:
"Iteration burndown charts are the most widely used artifact to track sprint progress. They offer insight into how much work remains and signal whether the team is on track to meet its sprint goal." Options A and B are long-term planning tools. Option C (velocity) is a forecasting metric and not updated daily.