Skip to content
CAPMEasy

CAPM Practice: Determine how to plan project iterations

Question 20 of 61 in Determine how to plan project iterations

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

In adaptive planning, what is the purpose of 'spike' stories?
Show answer & explanation

Correct answer: Time-boxed research or investigation stories used to reduce uncertainty before committing to implementation

Explanation

A spike is a time-boxed research activity to answer a specific question or reduce uncertainty. For example, 'investigate whether Library X can handle our data volume' — a spike might take one sprint and produce a recommendation (not production code). Spikes are used when the team lacks information needed to estimate or implement a story. They have a defined question and time box, preventing unlimited research.

**Why not B:** Stories split from larger epics are simply smaller user stories produced by decomposition, not spikes. A spike is defined by its purpose — time-boxed research to reduce uncertainty — not by where it sits in the backlog hierarchy.

**Why not C:** Spikes are deliberately small and time-boxed, typically fitting within a single sprint. Highly complex work that would take many sprints should be split into smaller stories; a spike may help the team learn enough to split or estimate such work, but it is not the large story itself.

**Why not D:** Spikes produce knowledge, not velocity gains. They consume team capacity and usually deliver no shippable code, so they are not a technique for increasing velocity — although the uncertainty they remove can make later estimates and delivery more predictable.

Key Concept

This question covers Determine how to plan project iterations under Determine how to plan project iterations (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