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
Agile Spikes – What They Are and How You Can Use Them
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
What Are Agile Spikes? Agile Research Boosting Project Outcomes
What is a spike in Agile? - Improve your Agile with Taiga - Taiga Community
Taiga Project Management Platform
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
How Agile Spikes help to Improve your Agile Product Delivery?, by Anca Onuta
Difference between user stories and tasks - Improve your Agile with Taiga - Taiga Community
Difference between user stories and tasks - Improve your Agile with Taiga - Taiga Community
What is a Spike in Agile
Agile - Spikes and the art to run them!
What's the difference between priority and severity - Improve your Agile with Taiga - Taiga Community
Taiga, the Best Tool for Agile Project Management + Case Study
What is a spike in Agile? Definition & FAQ