A spike in Agile is a focused effort to address uncertainties and gather insights before committing to a full implementation. In a previous article on how to manage uncertainty, I already mentioned this and other techniques that are often used interchangeably, so I believe it’s worth knowing more about spikes. In this article I’ll also cover the origin of this metaphor (including the answer directly from one of its authors), and its pros and cons. And finally, I’ll suggest how to add spikes to
5 tips on how to adopt Agile within a team and one corollary - Improve your Agile with Taiga - Taiga Community
Spike In Scrum: Definition, Benefits, And How To Use Them
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Spike in Scrum Agile Academy Dictionary
New to Taiga what is the difference between an issue and a task? - Taiga basics - Taiga Community
What is an Agile Spike Story? How to Use, Types & Benefits
Agile - Spikes and the art to run them!
Why Taiga? What makes Taiga's core proposition? - FAQ - Taiga Community
The Use of Spikes in Sprints. What is a Spike, and how can we use it?, by Luke Pivac, Agile, Adapt
