What is the main purpose of spikes?

• A. To replace backlog items.
• B. To explore and clarify uncertain technical or functional aspects before work begins.
• C. To measure sprint velocity.
• D. To assign more work to the team.

Answer: (B)

Spikes are focused investigations designed to reduce uncertainty before committing to a solution. They are time-boxed efforts to explore uncertain technical or functional aspects, such as evaluating different approaches, proving feasibility, or clarifying ambiguous requirements. The goal is to produce concrete findings or recommendations that inform how the backlog item should be designed and implemented, and to improve future estimates and planning. This is different from delivering standalone functionality—the spike itself isn’t about producing a shippable feature, but about gaining the knowledge needed to proceed confidently.

Spikes aren’t used to replace backlog items, measure sprint velocity, or assign more work to the team. They exist to illuminate options and risks so the team can make informed decisions and plan work more effectively.