Skip to content
CAPMEasy

CAPM Practice: Explain when it is appropriate to use an adaptive approach

Question 44 of 61 in Explain when it is appropriate to use an adaptive approach

Pick an answer below — you'll get the explanation instantly, no signup.

An adaptive team member says their task is '90% done' every week for three weeks but never completes it. What does this illustrate?
Show answer & explanation

Correct answer: The 'almost done' syndrome — the value of adaptive methods comes from actually completing work and measuring it against definition of done

Explanation

'90% done' that stays at 90% for weeks is a classic project management anti-pattern. Adaptive approaches address this through: time-boxed sprints that force completion (or not), strict Definition of Done criteria, and transparency through burndown charts that show actual remaining work. Work is either done (meets all DoD criteria) or not done — partial credit creates false confidence.

**Why not B:** The task may well have been underestimated, but re-estimating does not fix the underlying problem: progress is being reported as a percentage instead of being measured against the Definition of Done. A re-sized task can stay at '90% done' just as easily.

**Why not C:** Velocity counts only work that is actually completed, so an unfinished task adds nothing to it. The problem is misleading status reporting, not how velocity is calculated.

**Why not D:** Nothing in the scenario points to a resource shortage. Adding resources does not address the habit of reporting partial progress instead of completed work.

Key Concept

This question covers Explain when it is appropriate to use an adaptive approach under Explain when it is appropriate to use an adaptive approach (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