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
How Agile Spikes help to Improve your Agile Product Delivery?, by Anca Onuta
Spikes - Scaled Agile Framework
Mobile app for Taiga agile management system : r/androiddev
What is a spike in Agile? - Improve your Agile with Taiga - Taiga Community
What are Spikes in Agile?
The Burn-up Chart: A Game Changer for Managing Agile Team Progress - Improve your Agile with Taiga - Taiga Community
What is an Agile Spike and When Should You Use It?
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
How to motivate your team to update your project management tool - Improve your Agile with Taiga - Taiga Community
Spike In Scrum: Definition, Benefits, And How To Use Them