CAPM Practice: Determine how to document project controls of predictive, plan-based projects
Question 4 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.
Show answer & explanation
Correct answer: Status information on scope, schedule, cost, and quality against the approved baseline
Explanation
Performance reports in predictive projects show how the project is performing against approved baselines (scope baseline, schedule baseline, cost baseline). They include metrics like SPI, CPI, earned value data, milestone status, quality metrics, and risk status. This baseline-versus-actual comparison is fundamental to predictive project control.
**Why not A:** Daily standup notes and retrospective action items are agile artifacts, not components of predictive project performance reports. Predictive projects use formal status reports based on baseline comparisons, not agile ceremony outputs.
**Why not B:** User story acceptance criteria and definition of done are agile concepts used in adaptive projects. Predictive projects track performance against approved baselines using metrics like earned value, not against user story criteria.
**Why not C:** Product backlog items and sprint velocity are agile metrics specific to Scrum and other adaptive frameworks. Predictive project reporting focuses on scope, schedule, cost, and quality performance measured against approved baselines, not on backlog management or iteration velocity.
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).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free