CAPM Practice: Determine how to document project controls for an adaptive project
Question 6 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: Share the sprint burndown chart, velocity chart, and product backlog status — these provide real-time transparency into adaptive project progress
Explanation
Adaptive project progress is best communicated through adaptive artifacts: the sprint burndown shows current sprint progress; the velocity chart shows historical and projected performance; the product backlog shows remaining work and prioritization. These are more accurate and timely than traditional Gantt charts for adaptive projects and require no additional reporting effort.
**Why not A:** Adaptive projects still require transparency with stakeholders. Refusing the product owner's request ignores a legitimate information need; adaptive teams communicate progress through visible artifacts and information radiators rather than declining to report.
**Why not B:** A lengthy narrative report requires significant extra effort, quickly becomes outdated, and is harder to consume than visual adaptive artifacts. Adaptive approaches favor lightweight, real-time information radiators over heavy documentation.
**Why not C:** A traditional Gantt chart reflects a predictive, plan-driven schedule and does not fit how adaptive work is planned iteration by iteration. Burndown, velocity, and backlog artifacts provide more accurate and timely progress information for adaptive projects.
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