PMI Agile Certified Practitioner (ACP) Practice Exam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the PMI Agile Certified Practitioner Exam with multiple choice questions and flashcards. Each question includes explanations to help you gear up for your test!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


Which of the following best describes the primary role of a burn-up chart?

  1. To track team velocity over iterations

  2. To indicate the work-in-progress during a project

  3. To show completed functionality over time without indicating work-in-progress

  4. To assess team collaboration levels

The correct answer is: To show completed functionality over time without indicating work-in-progress

A burn-up chart is specifically designed to illustrate the amount of work completed over time, allowing teams to visualize their progress toward a project goal. This chart plots completed work against the total scope of work, thereby providing a clear view of functionality that has been finished and how it trends over time. By showing completed functionality, the burn-up chart helps stakeholders quickly understand how much progress has been made and how much work remains, without delving into the complexities of work-in-progress. This focus on completed work is crucial for tracking milestones and forecasting project completion dates. Other options do not align with the primary function of a burn-up chart. For instance, while team velocity tracking is important, it typically relates to historical performance and estimation rather than the visualization of completed work over time. Indicating work-in-progress, though relevant to project monitoring, is outside the purview of a burn-up chart, as its emphasis lies in showcasing work that has been finished. Assessing team collaboration levels is unrelated to burn-up charts, as this metric speaks more to interpersonal dynamics within the team rather than tracking workflow progress.