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
What is a Spike in Agile
What Is a Spike Story in Agile?
Mobile app for Taiga agile management system : r/androiddev
Innovation in Agile: 4 different approaches to stay competitive - Improve your Agile with Taiga - Taiga Community
Taiga: Free Open Source Agile Project Management
5 different setups for agile projects: Priority driven organic workflow
New to Taiga what is the difference between an issue and a task? - Taiga basics - Taiga Community
Taiga tutorial - Agile Project Management
New to Taiga what is the difference between an issue and a task? - Taiga basics - Taiga Community
Taiga - agile project management tool. Free & Open Source.
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Quick intro to Scrum module - Tutorials and Guides - Taiga Community
What is a spike in Agile? - Improve your Agile with Taiga - Taiga Community
Agile - Spikes and the art to run them!