CAPM Practice: Explain when it is appropriate to use an adaptive approach
Question 53 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.
Show answer & explanation
Correct answer: 10 sprints — assuming velocity remains constant and no new items are added to the backlog
Explanation
350 story points ÷ 35 story points/sprint = 10 sprints forecast. This estimate assumes: current velocity remains constant (no increase or decrease); no significant new items are added; and no significant changes in team composition. These are important caveats — backlog velocity forecasts give a planning estimate that should be revisited as the project progresses.
**Why not A:** 7 sprints would require a velocity of 50 points per sprint (350 ÷ 7). Velocity-based forecasting uses the team's demonstrated velocity, not an assumed future improvement. Planning on speculative velocity gains produces an optimistic forecast the team is unlikely to meet.
**Why not B:** While backlogs in adaptive projects do evolve, this does not mean a project can never be forecast or completed. Velocity gives a reasonable planning estimate for the current backlog, and the forecast is simply revisited as items are added, removed, or reprioritized.
**Why not C:** 14 sprints would imply a velocity of 25 points per sprint (350 ÷ 14). There is nothing in the scenario indicating velocity will decrease, and forecasting should be based on the team's observed velocity rather than an assumed decline.
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).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free