Art of Spike

Spike is used to finding out the missing element of the user story to complete. Developer has to estimate the spike story during the Sprint planning session.

Why a Spike?

The reason to introduce a spike is that further analysis is required to determine the fesability to implement a technical solution is required. Also, when further study is required to determine the associated risk and/or cost benefits of functional solution options

This was the time when I have introduced SPIKE. The purpose of Spike is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate. -© Scaled Agile, Inc.

Spike Outcome - Next Steps

Once the solution is identified, the person who was working on Spike, will document the approach and share it with the team. The Product Owner will create a new implementation story. In the sprint planning session, the Product Owner will prioritize the story. The team will estimate the story and start work on it.

Two types of Spikes

Functional

They are used to determine the system behavior and solutions such as identifying the risk or implementation decision.

Technical

They are used to find the technical approach to solve the problem such as the technical implementation of the user story or performance of the system on the implementation of a new change.

Resources

Art of Spike - Medium