CAPM Practice: Determine how to document project controls for an adaptive project
Question 10 of 60 in Determine how to document project controls for an adaptive project
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Outcome metrics tied to business objectives (e.g., user adoption, revenue impact, error reduction)
Explanation
Story points and velocity measure activity and throughput — how much the team is doing. Outcome metrics measure impact — whether what the team built actually achieved business goals. Teams can complete all planned stories at high velocity while delivering little business value if the stories don't drive meaningful outcomes. Linking work to business metrics (OKRs, KPIs) connects adaptive delivery to organizational purpose.
**Why not B:** Sprint velocity measures how many story points the team completes per sprint — a throughput and planning measure. High velocity shows the team is producing work, not that the work is delivering business value.
**Why not C:** Code coverage measures how much of the code is exercised by automated tests — a technical quality indicator. It says nothing about whether the delivered features achieve business outcomes.
**Why not D:** Counting completed stories measures output, not outcome. A team can complete many stories that have little or no effect on users or business goals.
Key Concept
This question covers Determine how to document project controls for an adaptive project under Determine how to document project controls for an adaptive project (Agile Frameworks/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