Spike
A short, time-boxed effort in a project when the team researches, experiments, or builds a quick prototype to test feasibility and guide the next steps.
Key Points
- Fixed-duration investigation aimed at answering a specific question or reducing uncertainty.
- Focuses on learning and feasibility; not intended to deliver production-ready functionality.
- Typical outputs include findings, recommendations, throwaway prototypes, and improved estimates.
- Planned as a backlog item with clear success criteria for what decision or insight is needed.
Example
A Scrum team is unsure about integrating a new payment gateway. They schedule a 2-day spike to prototype the API calls, assess security requirements, and measure response times. The result is a brief report, sample code, and a go/no-go recommendation for using the gateway.
PMP Example Question
During sprint planning, the team flags high uncertainty about a third-party API needed for the next feature. What is the best action?
- Add extra buffer and proceed with development as planned.
- Start building the full feature and learn during implementation.
- Create a time-boxed spike to research and prototype the integration.
- Escalate the risk immediately to the steering committee.
Correct Answer: C — Create a time-boxed spike to research and prototype the integration
Explanation: A spike systematically reduces uncertainty and informs decisions before committing to full implementation.