CAPM Iteration Goals, Capacity, and Planning Choices

Iteration planning is not only about fitting as many items as possible into a timebox. CAPM usually rewards a more disciplined choice: use the iteration goal, current capacity, historical pace, and work uncertainty together to decide what should fit now.

Why Goals Matter

An iteration goal gives the cycle a coherent purpose. Without one, the team may choose a scattered set of items that fits capacity mathematically but does not support a meaningful outcome.

The goal also helps when tradeoffs appear during the cycle. It gives the team a reference point for deciding what matters most.

That matters on the exam because many weak answer choices focus only on volume. A team can fill an iteration with high-value-looking items and still create poor outcomes if the work does not support a clear near-term objective. CAPM usually favors a coherent, goal-aligned slice of value over a larger but fragmented set of unrelated work.

Why Capacity And Velocity Both Matter

Velocity is a historical signal of what the team has usually completed. Capacity reflects the actual availability for the upcoming cycle. A team may have a stable past pace but still need to reduce scope because of vacations, onboarding, support work, or other interruptions.

The strongest CAPM answer usually combines both:

• use the goal to keep the work coherent
• use velocity as a reference point
• adjust for real upcoming capacity
• account for risk and dependency

CAPM may also test the difference between evidence and commitment. Velocity helps forecast what might be realistic. It is not a contractual promise. If the next iteration contains unfamiliar work, outside approvals, or cross-team dependencies, blindly copying past velocity is usually weaker than adjusting the plan.

Planning Logic

    flowchart TD
	    A["Iteration goal"] --> D["Draft scope"]
	    B["Historical velocity"] --> D
	    C["Current capacity and risk"] --> D
	    D --> E["Realistic commitment"]

What Good Iteration Planning Looks Like

Strong iteration planning usually asks these questions in sequence:

1. What outcome should this iteration achieve?
2. Which backlog items best support that outcome?
3. What is the team’s likely delivery range based on recent pace?
4. What is different about the upcoming iteration’s actual availability?
5. Which dependencies, blockers, or interruptions could reduce throughput?

This is why a strong planning response often looks selective instead of maximal. The team should not pull work solely because it fits on paper. It should select work that supports the goal and remains realistic given current conditions.

Capacity, Velocity, And Scope Negotiation

The exam often tests how these planning inputs interact:

If a scenario includes reduced availability and stakeholder pressure, the strongest answer is usually not “work harder” or “keep scope fixed.” It is to renegotiate scope while protecting the goal. In adaptive work, honesty about delivery limits is part of good planning, not a failure of commitment.

Example

A team usually finishes around 30 points, but two members will be out next iteration. A weak response is to plan the same scope anyway because stakeholders want more. A stronger response uses the goal and adjusts the commitment to match reduced capacity.

If the team also has one urgent compliance item and two optional enhancements, the best response may be to keep the compliance work and one enhancement that clearly supports the iteration goal, while deferring the lower-value item. CAPM generally rewards selective scope protection instead of broad overcommitment.

Exam Scenario

A sponsor asks the team to carry forward all unfinished work from the prior iteration and still pull several urgent new items into the next one. The team knows two developers will also spend time supporting a production issue.

The strongest CAPM response is to revisit scope using the new capacity picture and a clear iteration goal. Some items may need to be deferred, split, or re-prioritized. A scenario like this tests whether you understand that adaptive planning protects focus and realism, rather than preserving scope at all costs.

Common Pitfalls

• using the goal as only decorative text
• treating past velocity as a guaranteed future promise
• ignoring reduced capacity for the next cycle
• selecting unrelated work simply because it fits numerically
• carrying unfinished work automatically without reassessing fit and priority
• treating stakeholder urgency as a reason to ignore planning evidence

Check Your Understanding

Sample Exam Question

Scenario: A team has averaged 28 to 30 points over recent iterations. Next cycle, two members will be out part of the time, but stakeholders still want the team to pull in 35 points because several items are urgent.

Question: How should the team plan that iteration?

• A. Commit to 35 points anyway because urgency matters more than capacity
• B. Use historical velocity as a reference, adjust for reduced capacity, and choose work that still supports a coherent iteration goal
• C. Ignore historical data and plan from intuition only
• D. Cancel iteration planning until stakeholder urgency decreases

Best answer: B

Explanation: CAPM usually rewards realistic planning based on past pace, real capacity, and coherent goal-driven scope.

Why the other options are weaker:

• A: Urgency does not remove delivery limits.
• C: Ignoring useful data weakens planning.
• D: The team still needs a realistic plan even under pressure.