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.