The correct answer is D — Up-to-date project radiators.

Information radiators provide at-a-glance visibility into project status, progress, blockers, and other key metrics. Sharing or including these visual tools in extended stakeholder communication ensures transparency and up-to-date awareness, which aligns with agile values.

PMI Agile Practice Guide:

“Information radiators provide immediate and transparent access to project health and status. They reduce the need for formal reporting and keep stakeholders aligned in real time.”

(PMI Agile Practice Guide, Section 5.6 – Information Radiators)

Mike Griffiths:

“Using radiators to keep stakeholders informed improves trust, accelerates decision-making, and supports ongoing engagement.”

(PMI-ACP Exam Prep, Chapter 3 – Value-Driven Delivery)

Incorrect options:

A and B are not relevant for stakeholder reporting.

C is too narrow and lacks the holistic view offered by radiators.

Answer: D

The correct answer is C – Ensure that members begin to self-organize as small teams with efficiently distributed skills.

Agile emphasizes self-organizing teams. When teams are too large, splitting into smaller teams is a good practice (Scrum recommends 5–9 members per team). However, rather than top-down assignment, the Scrum Master should enable and support self-organization. Teams should be encouraged to form organically while ensuring knowledge-sharing and cross-functional capabilities.

From the PMI Agile Practice Guide:

“Agile leaders support team self-organization by creating an environment of trust and encouraging the team to determine how best to accomplish their work.”

(PMI Agile Practice Guide, Section 5.2 – Team Composition)

Mike Griffiths writes:

“Agile teams are self-organizing, and the role of the leader is to facilitate the conditions for that to occur, not to direct assignments.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why other options are less appropriate:

A suggests command-and-control behavior, which is contrary to Agile values.

B makes assumptions about comfort levels and may ignore skill diversity.

D disregards team input and imposes a solution, limiting buy-in and trust.

Answer: C

══════════════════════════════════════════════════

Velocity is a measure of how much work a team completes in a given sprint, typically measured in story points or other units of effort. While velocity can be useful for tracking progress and forecasting future work, it has some limitations when it comes to accurate capacity planning.

Velocity can vary from sprint to sprint due to multiple factors, such as the complexity of the tasks, interruptions, or even external influences. This variability can make it difficult to predict how much work a team can handle in future sprints, leading to inaccurate capacity planning.

The correct answer is B – The duration of feedback cycles has increased.

In Agile, quick feedback is crucial to success. An increase in feedback cycle time indicates breakdowns in communication, delayed decision-making, or weak collaboration—all of which are signs that a distributed team may not be functioning effectively.

From the PMI Agile Practice Guide:

“Distributed teams require more intentional efforts to maintain communication and reduce feedback loops. Lag in feedback reduces responsiveness and impedes value delivery.”

(PMI Agile Practice Guide, Section 2.3 – Agile Team Communication)

Mike Griffiths highlights:

“One of the key risks in distributed teams is the degradation of feedback speed. Long feedback cycles result in slower adaptation and lost opportunities.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Other options:

A (more emails) is neutral—could be communication, not dysfunction.

C (increased velocity) is a positive sign.

D (rescheduling meetings) is an adjustment, not necessarily dysfunction.

Answer: B

══════

══════════════════════════════════════════════════

Task boards (or visual boards) are a great way to facilitate communication within the team. By using a task board, team members can easily see what work has been completed, what is currently being worked on, and what still needs attention. This visual aid helps keep everyone on the same page, ensures that information is shared transparently, and can help identify potential bottlenecks or communication gaps. It improves collaboration and visibility, making it easier for the team to coordinate and align on tasks, leading to fewer delays in the development process.

Value stream mapping is a key Lean technique used to visualize the sequence of steps involved in delivering value to customers. It maps out both the value-creating activities and the non-value-creating activities (waste), providing a clear view of the entire process. This helps identify inefficiencies and opportunities for improvement to optimize the flow of value.

The burndown chart displayed shows two lines:

A diagonal guideline (ideal trend line) representing the expected or planned burndown rate.

A line with plotted black squares representing the actual progress of work completed during the iteration (typically in story points or hours).

The actual progress line (with black squares) stays consistently above the ideal line throughout the iteration.

This indicates that less work was completed than planned at each point in time.

Toward the end of the iteration (around the 30th or 31st), the chart shows that the total remaining work does not reach zero—implying incomplete work by the iteration’s end.

Analysis of the Chart:Interpretation According to Agile Standards:According to the PMI Agile Practice Guide (Section 5.4: Tracking Iteration Progress) and Mike Griffiths ' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning):

A burndown chart that remains above the ideal line and does not reach the baseline (zero) by the end of the iteration reflects that the team is behind schedule and did not complete all planned work.

The burndown chart is a primary information radiator for evaluating scope completion versus time and is a critical tool for monitoring iteration performance.

Therefore:

Option C is correct:

" It trended behind schedule and did not complete everything on time. "

Option A is incorrect — the chart clearly shows a lag behind schedule.

Option B is incorrect — there is no indication that the iteration time box was extended.

Option D is incorrect — the team did not finish early or complete all tasks.

The correct answer is B – Break the story up and focus on the most valuable parts. Agile promotes progressive elaboration, and large or complex stories (epics) should be broken down into smaller, testable user stories. This practice enables clarity, faster feedback, and more accurate planning.

From the PMI Agile Practice Guide:

“Large stories (epics) should be split into smaller user stories to enable understanding, estimation, and incremental delivery. Stories should be small enough to be completed within an iteration.”

(PMI Agile Practice Guide, Section 5.3 – User Stories and Story Splitting)

Mike Griffiths states:

“When a user story is too large or unclear, the team should break it down into smaller pieces, focusing on the most valuable parts first. Story splitting is a key agile practice.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 5 – Adaptive Planning)

Incorrect options:

A discourages collaboration and learning.

C delays the resolution unnecessarily.

D avoids solving the actual problem and abandons valuable work.

Answer: B

────────────────────────────────────

The correct answer is D – Ask QA team members experienced with the new automation framework to cross-train the other QA members. Agile emphasizes shared ownership, continuous learning, and eliminating skill silos. Cross-training is an effective way to improve team capability and reduce dependencies.

From the PMI Agile Practice Guide:

“Agile encourages cross-functional teams and skills sharing. When skill gaps are discovered, team members with the knowledge are encouraged to cross-train others to increase the team’s flexibility and productivity.”

(PMI Agile Practice Guide, Section 4.3 – Team Performance and Learning)

Mike Griffiths adds:

“Cross-training improves team resilience and reduces bottlenecks. When expertise is limited to a few people, risks increase. Agile teams overcome this by mentoring and shared learning.”

(Mike Griffiths, PMI-ACP Exam Prep, Chapter 4 – Team Performance)

Incorrect options:

A and C are reactive and delay resolution.

B encourages overwork and can lead to burnout.

Answer: D

────────────────────────────────────

The correct answer is D – Ensured that the team was comprised of cross-functional, generalized specialists.

Agile teams are expected to be cross-functional and self-sufficient. A lack of a required skill that halts progress typically points to an improperly constructed team. Building teams with broad (T-shaped) skills ensures they can collectively deliver value without external dependencies.

From the PMI Agile Practice Guide:

“Agile teams are ideally composed of cross-functional members who have both depth in a specialty and breadth across disciplines. This enables the team to self-organize and deliver complete increments of value.”

(PMI Agile Practice Guide, Section 4.1 – Building Agile Teams)

Mike Griffiths elaborates:

“Agile favors generalized specialists or T-shaped professionals who can collaborate across functions. This improves agility, resilience, and continuity within iterations.”

(Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 – Team Performance)

Why the other options are insufficient:

A is a reactive strategy; proactive skill assessment is preferred.

B may delay critical features unnecessarily.

C creates external dependencies, which agile seeks to avoid.

Answer: D

══════════════════════════════════════════════════