CAPM domain - 20% of the exam

Agile Frameworks/Methodologies

Agile Frameworks/Methodologies is 20% of the CAPM exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

60
Practice questions
3
Objectives
60
Medium

Where people go wrong

  • Misusing velocity as a target or a comparison

    The wrong answers treat velocity as something other than a record of completed story points. They set it as a target to exceed, compare one team with another, or stretch a forecast above what the team has delivered. Points are calibrated per team, so a figure means something only within that team. The correct answers use velocity as an observed average to forecast how much scope fits in a future sprint.

    See it in a sample question
  • Giving Scrum accountabilities to the wrong role

    The wrong answers make the scrum master a boss who assigns work, hand technical decisions to a line manager or the product owner, or let a stakeholder order the product backlog. In Scrum the developers decide how the work is done, the product owner is accountable for ordering the product backlog, and the scrum master is a servant leader who coaches and removes impediments. Stakeholders influence the product owner but do not decide.

    See it in a sample question
  • Swapping the commitments of Scrum artifacts

    The wrong answers name the definition of done where the sprint goal, the product goal or per-item acceptance criteria belong, and the reverse. Each artifact has its own commitment: the product goal for the product backlog, the sprint goal for the sprint backlog, and the definition of done for the increment. The definition of done is the shared quality standard that decides whether work counts as done.

    See it in a sample question
  • Offering predictive conditions as reasons to go adaptive

    The wrong answers present predictive conditions as grounds for an adaptive approach: stable and well-understood requirements, a fixed scope and date, a mandated sequence, a fixed budget. Those conditions favour a predictive plan. The correct answers point to requirements that are uncertain and expected to evolve, where frequent feedback and short iterations let the team learn and adjust.

    See it in a sample question
  • Reading a burndown line above the ideal as good news

    The wrong answers read a remaining-work line sitting above the ideal line as being ahead, as everything being done, or as a faulty chart. The line shows work still remaining, so a line above the guideline means the team is behind the planned pace and the goal is at risk. The ideal line is only a reference, and a gap is information to inspect and act on.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleAgile Frameworks/Methodologiesmedium

During sprint planning for the Aurora billing team, a manager states that the team's velocity of 30 points should be treated as a performance goal that each developer must be pushed to exceed every sprint. How should velocity actually be understood?

  • AAs a target that management sets in advance, so the team is accountable for hitting a rising point figure sprint after sprint.
  • BAs a productivity benchmark for comparing this team against other teams that estimate in their own points.
  • CAs a quality metric that shows how many defects the team removed during the sprint just completed.
  • DAs an empirical measure of how many story points the team has historically completed, used to forecast how much work fits in future sprints. Correct
Velocity is an empirical capacity measure used to forecast future sprint scope, not a target to be pushed upward. Velocity records the points a team actually finished in past sprints, giving an evidence-based basis for forecasting achievable scope. Turning it into a target encourages inflating estimates, which destroys its usefulness as a planning input.

Why A is wrong: This is the classic misuse; treating velocity as a target invites point inflation and gaming, which corrupts the very measure used to plan future sprints.

Why B is wrong: This is tempting but wrong because points are calibrated per team, so one team's velocity is meaningless when set beside another team's differently sized points.

Why C is wrong: This confuses velocity with a defect measure; velocity counts completed story points of delivered work and says nothing directly about defect counts.

Why D is correct: Correct. Velocity is an observed capacity figure derived from completed work, and its legitimate use is forecasting realistic sprint scope, not driving people to a quota.

Free sampleAgile Frameworks/Methodologiesmedium

On the Aurora analytics project the scrum master notices developers are blocked waiting for test-environment access and are unsure how to split a large story. A junior team member asks the scrum master to simply assign the remaining tasks and decide the split. Consistent with the agile mindset, how should the scrum master respond?

  • AAssign each developer a fixed task list and dictate the story split, since a scrum master is accountable for the team hitting the sprint target.
  • BEscalate both issues to the functional manager so that the manager can allocate the tasks and approve the split.
  • CRemove the environment-access impediment and coach the team to split the story themselves, serving the team rather than directing it. Correct
  • DTell the team to resolve the access problem on their own while the scrum master decides how the story is broken down.
A scrum master acts as a servant leader who removes impediments and coaches self-organisation rather than assigning work. Servant leadership means the scrum master serves the team by clearing obstacles and building the team's capability to organise its own work, so the correct action pairs impediment removal with coaching, not directive task assignment.

Why A is wrong: This casts the scrum master as a command-and-control boss assigning work, which contradicts the self-organising, servant-leadership model, so it is wrong.

Why B is wrong: Handing decisions to a functional manager is tempting for speed but undermines team self-management and the scrum master's facilitation role, so it is wrong.

Why C is correct: Clearing impediments and coaching self-organisation is the servant-leader role of the scrum master, which is why this is the correct response.

Why D is wrong: This ignores the impediment the scrum master should remove and takes over a decision the team should own, mixing up the responsibilities on both counts, so it is wrong.

Free sampleAgile Frameworks/Methodologiesmedium

At the sprint review for the Larkspur booking platform, the product owner points to a completed backlog item and asks whether it is genuinely done. The team realises it has passed unit tests but has not met the agreed quality standard the team applies to every item. Under The Scrum Guide, which artifact commitment tells the team whether the increment is releasable?

  • AThe definition of done, the formal description of the quality standard an increment must meet to be considered releasable. Correct
  • BThe sprint goal, which is the single objective for the sprint and confirms an increment meets the team's shared quality standard.
  • CThe product goal, the long-term objective for the product that establishes when an individual increment is releasable this sprint.
  • DThe acceptance criteria, the product owner's per-item conditions that serve as the team-wide standard for every increment.
The definition of done is the increment's commitment and states the quality standard an item must meet to be releasable. Each Scrum artifact carries a commitment, and the increment's commitment is the definition of done, which sets the shared quality standard that determines whether work is truly complete and releasable.

Why A is correct: Correct: the definition of done is the commitment for the increment and sets the quality standard an item must meet before it counts as done.

Why B is wrong: This is tempting because the sprint goal is the sprint backlog's commitment, but it states the sprint objective; it does not define the quality bar for a done increment.

Why C is wrong: This is tempting because the product goal is a real commitment tied to the product backlog, but it describes a future target for the product, not the quality bar for a single increment.

Why D is wrong: This is tempting because acceptance criteria do gate individual items, but they are per-item conditions, whereas the team-wide quality standard for a releasable increment is the definition of done.

Free sampleAgile Frameworks/Methodologiesmedium

A programme office must classify the Redgum research initiative as better suited to an adaptive approach or a predictive one before it starts. Several facts about the initiative are on the table. Which single condition most strongly signals that an adaptive approach is more appropriate than a predictive one?

  • AThe final scope and acceptance criteria are fully understood and stable now
  • BThe requirements are likely to evolve as the team learns from early work Correct
  • CThe work must follow a fixed regulatory sequence that is hard to vary
  • DThe sponsor has fixed the total budget and delivery date in advance
An adaptive approach fits best when requirements are uncertain and expected to change, so the work can be delivered and refined incrementally. Adaptive approaches suit high-uncertainty work where requirements emerge and change, because incremental delivery and frequent feedback let the team refine the product, whereas stable, well-defined scope with fixed sequences favours predictive planning.

Why A is wrong: A well-defined and stable scope actually favours a predictive approach, so this condition points the opposite way from adaptive and is a tempting reversal of the correct signal.

Why B is correct: High uncertainty with requirements expected to change as knowledge grows is the core signal for an adaptive approach, which delivers in increments so learning can reshape the work.

Why C is wrong: A mandated fixed sequence removes the freedom to reorder and iterate, which suits a predictive plan, so this condition argues against adaptive rather than for it.

Why D is wrong: Fixed cost and date constraints are common on predictive projects and do not on their own make adaptive the better fit, so this is a plausible but misdirected indicator.

Free sampleAgile Frameworks/Methodologiesmedium

Halfway through a two-week iteration, the Cascade team's iteration burndown chart shows the remaining-work line sitting well above the ideal line and running roughly parallel to it rather than sloping down toward zero. What does this pattern most directly indicate about the iteration?

  • AThe team is completing work faster than planned and will likely finish the iteration early
  • BThe team has added new scope to the iteration, which a burndown chart is designed to display
  • CThe chart is faulty because a burndown line should closely track the ideal line
  • DRemaining work is not being burned down as planned, so the iteration goal is at risk Correct
A burndown line sitting above the ideal line signals that remaining work is not being completed on plan and the goal is at risk. An iteration burndown chart plots remaining work against an ideal line to zero. When the actual line stays above and parallel to the ideal, completion is lagging the plan, which surfaces schedule risk early enough for the team to adjust.

Why A is wrong: A line dropping below the ideal line would signal being ahead, so this reading confuses the axes; a flat line above the ideal shows the opposite of finishing early.

Why B is wrong: Scope changes are more visible on a burnup chart, which tracks scope separately; a flat burndown line points to a slow completion rate rather than confirming added scope.

Why C is wrong: The ideal line is only a reference for even progress, not a rule the actual line must follow, so divergence is informative rather than evidence of a broken chart.

Why D is correct: A remaining-work line above and parallel to the ideal line means little work is being completed relative to plan, which flags the iteration goal as at risk and prompts a team response.

Other domains in this exam

See also the CAPM cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by PMI. Original, blueprint-aligned practice material only.