nerdexam
PMI

PMP · Question #704

A project manager works at an organization that is transitioning to agile. The development team has recommended using a burndown chart to provide visibility on project progress to all stakeholders…

The correct answer is A. Advise the project management office (PMO) to use the burndown chart as the single. In an agile transition, the project manager should leverage the burndown chart's real-time progress visibility by advising the PMO to adopt it as a primary communication tool, especially for project progress. This promotes transparency and aligns with agile principles.

Submitted by carlos_mx· Apr 18, 2026Process

Question

A project manager works at an organization that is transitioning to agile. The development team has recommended using a burndown chart to provide visibility on project progress to all stakeholders. What should the project manager do to ensure effective communication throughout the project?

Options

  • AAdvise the project management office (PMO) to use the burndown chart as the single
  • BDevelop a communications management plan for each category in the stakeholder register.
  • CInclude the burndown chart in a monthly report that is distributed to all stakeholders.
  • DPostpone the recommendation since the organization does not currently have a defined agile

How the community answered

(34 responses)
  • A
    82% (28)
  • B
    3% (1)
  • C
    9% (3)
  • D
    6% (2)

Why each option

In an agile transition, the project manager should leverage the burndown chart's real-time progress visibility by advising the PMO to adopt it as a primary communication tool, especially for project progress. This promotes transparency and aligns with agile principles.

AAdvise the project management office (PMO) to use the burndown chart as the singleCorrect

The burndown chart is an excellent agile artifact for visually communicating sprint or release progress, showing remaining work against time. Advising the PMO to use it as a primary, singular source for progress visibility simplifies communication, enhances transparency, and supports the organization's agile transition by standardizing an agile reporting tool.

BDevelop a communications management plan for each category in the stakeholder register.

While a communications management plan is crucial, developing a separate plan for each category of the stakeholder register is an overly complex and potentially unnecessary approach, especially when a single, effective tool like a burndown chart can serve multiple stakeholders.

CInclude the burndown chart in a monthly report that is distributed to all stakeholders.

Including a burndown chart in a monthly report diminishes its real-time value and responsiveness, which is a key benefit of agile reporting for frequent progress updates and early issue detection.

DPostpone the recommendation since the organization does not currently have a defined agile

Postponing the recommendation would hinder the organization's agile transition and delay the adoption of valuable agile practices, rather than facilitating effective communication and progress tracking.

Concept tested: Agile Communication and Reporting

Source: https://www.atlassian.com/agile/scrum/reports/burndown-chart

Topics

#Agile Project Management#Communication Management#Performance Reporting#Stakeholder Communication

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PMP Practice