Spike (software development)
This article relies largely or entirely on a single source. (October 2015)
A spike is a product-testing method originating from Extreme Programming that uses the simplest possible program to explore potential solutions. It is used to determine how much work will be required to solve or work around a software issue. Typically, a 'spike test' involves gathering additional information or testing for easily reproduced edge cases. The term is used in agile software development approaches like Scrum or Extreme Programming.
- As a way to familiarize the team with new hardware or software
- To analyze a problem thoroughly and assist in properly dividing work among separate team members.
- Spikes tests can also be used to mitigate future risk, and may uncover additional issues that have escaped notice.
A distinction can be made between technical spikes and functional spikes. The technical spike is used more often for evaluating the impact new technology has on the current implementation. A functional spike is used to determine the interaction with a new feature or implementation.
To track such work items, in a ticketing system, a new user story can be set up for each spike, for organization purposes.
Following a spike, the results (a new design, a refined workflow, etc.) are shared and discussed with the team.
|This software-engineering-related article is a stub. You can help Wikipedia by expanding it.|