CAPM Practice: Determine how to document project controls for an adaptive project
Question 60 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: Transparency makes project status, progress, and process visible to all — enabling timely inspection and adaptation, which are the foundation of empirical control in Scrum
Explanation
Scrum's empirical model (transparency → inspection → adaptation) makes transparency foundational to all controls. Without visibility into what's really happening, inspection is impossible and adaptation is uninformed. Artifacts like the sprint backlog, burndown chart, and task board all support transparency-based control.
**Why not B:** Transparency in Scrum is about making the work, progress, and process visible to those who inspect and adapt it — not specifically about sharing project financials with the whole team. Narrowing it to financial disclosure misses its role in empirical control.
**Why not C:** Transparency is not an optional guideline; it is one of the three pillars of Scrum's empirical process control. Without it, inspection and adaptation cannot work, so treating it as rarely followed undermines the entire framework.
**Why not D:** Scrum achieves transparency through visible artifacts and events such as the sprint backlog, task board, and Daily Scrum — not through daily written reports. Requiring written status reports adds overhead without improving the shared visibility that empirical control depends on.
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