Skip to content
CAPMEasy

CAPM Practice: Determine how to document project controls for an adaptive project

Question 19 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.

Which document captures risks identified in an adaptive project?
Show answer & explanation

Correct answer: Risk register or risk backlog, maintained by the team and product owner

Explanation

Adaptive projects do identify and track risks, but they do so within adaptive conventions. Some teams maintain a risk register (same as predictive), while others use a 'risk backlog' integrated with the product backlog (risk items prioritized and addressed in sprints). The key is transparency about risks — how they're documented is less important than that they are visible and managed.

**Why not B:** Adaptive projects do track risks. Iterative delivery reduces some risks, but risks still need to be identified, made visible, and addressed — typically through a risk register or risk items in the backlog.

**Why not C:** Daily standup notes may surface impediments, but they are a short-lived record of the team's coordination, not a maintained repository where risks are captured, prioritized, and tracked over time.

**Why not D:** A sprint burndown chart shows remaining work in the sprint over time. It can reveal that progress is off track, but it does not capture or describe individual risks.

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).

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