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
Taiga Tutorial 11 Taiga.io Understanding Assignment of Points
Taiga Review, Pricing, Key Info, and FAQs
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
Innovation in Agile: 4 different approaches to stay competitive - Improve your Agile with Taiga - Taiga Community
Agile - Spikes and the art to run them!
What is a spike in Agile? Definition & FAQ
PDF) Definition of an Agile Software Development Process for the European Space Industry
Effective Techniques for Agile Teams to Reduce Uncertainty - Improve your Agile with Taiga - Taiga Community
Taiga Open Source Agile Project Management Software
Taiga: Free Open Source Agile Project Management
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
What is an Agile Spike and When Should You Use It?