Skip to content
CAPMEasy

CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Question 21 of 85 in Determine how to document project controls of predictive, plan-based projects

Pick an answer below — you'll get the explanation instantly, no signup.

Which of the following is NOT typically part of project performance reporting in a predictive project?
Show answer & explanation

Correct answer: Sprint velocity and burndown charts

Explanation

Sprint velocity and burndown charts are agile artifacts, not tools used in predictive project reporting. Predictive performance reports include: earned value metrics (SPI, CPI, SV, CV), milestone status, risk register updates, quality metrics, issue status, and cost/schedule forecasts — all based on comparison against approved baselines.

**Why not A:** Risk status and issues summary is a standard component of predictive project performance reporting. Monitoring risks and issues against the risk register and issue log is a core predictive project control activity reported regularly to stakeholders.

**Why not C:** Milestone status is a fundamental element of predictive project reporting. Tracking progress against planned milestones is one of the most common and important ways to communicate schedule performance in predictive projects.

**Why not D:** Earned value analysis (SPI, CPI, SV, CV) is a hallmark of predictive project performance monitoring. These metrics compare actual performance against approved baselines and are central to how predictive projects measure and report progress.

Key Concept

This question covers Determine how to document project controls of predictive, plan-based projects under Determine how to document project controls of predictive, plan-based projects (Predictive, Plan-Based Methodologies).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free