๐๐๐ง๐๐ซ๐๐ฅ ๐๐๐๐ข๐ง๐ข๐ญ๐ข๐จ๐ง:
Create spike solutions to figure out answers to tough technical โ๏ธ or design ๐ problems.
A spike solution is a very simple๐ก program to explore potential solutions.
Build the spike to only addresses the problem under examination ๐ and ignore all other concerns.
Most spikes are not good enough to keep, so expect to throw it away ๐งน.
The goal is reducing the risk of a technical problem or increase the reliability of a user story's estimate.
When a technical difficulty threatens to hold up the system's development put a pair of developers ๐ฉโ๐ป๐จโ๐ป on the problem for a week or two and reduce the potential risk.
๐ ๐จ๐๐ฎ๐ฌ ๐จ๐ง ๐ญ๐๐๐ก๐ง๐ข๐๐๐ฅ๐จโ๐ง ๐ฌ๐ฉ๐ข๐ค๐:
A technical spike can be used :
๐ to assess the potential performance or load impact of a new user story,ย
๐ to assess specific implementation technologies that can be applied to a solution, or for any other reasonย
๐ when the team needs to develop a more confident understanding of the desired approach before committing new functionality to a timeframe.ย
๐ก Mockups and wireframes are also spikes, however, they are classified as Functional Spikes.