Definition
A Spike is a time-boxed investigation or experiment within an agile framework, designed to gain knowledge or answer a question that is blocking progress on a user story or feature. It is not intended to deliver production-ready code but rather to reduce uncertainty and inform future development efforts. Spikes are typically implemented as tasks within a sprint, allowing the team to explore technical challenges, assess feasibility, or research potential solutions. This practice is crucial for mitigating risks associated with complex or unknown requirements, preventing costly rework later in the project. For instance, a team might conduct a Spike to determine the best third-party API for integrating a new payment gateway. Unlike a user story that delivers direct business value, a Spike's value lies in the information it uncovers, enabling more accurate estimation and planning for subsequent work. Spikes are frequently encountered in preparation for the PMI-ACP, CAPM, and PMP certifications.