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 Story in Agile?
New to Taiga what is the difference between an issue and a task? - Taiga basics - Taiga Community
5 different setups for agile projects: Priority driven organic workflow
Spike In Scrum: Definition, Benefits, And How To Use Them
Agile Software Development: An Overview of Key Concepts, Principles, and Methodologies Covered in Modules 1-6 at Amity University, PDF, Agile Software Development
Spike In Scrum: Definition, Benefits, And How To Use Them
Agile Spikes
Difference between user stories and tasks - Improve your Agile with Taiga - Taiga Community
Effective Techniques for Agile Teams to Reduce Uncertainty - Improve your Agile with Taiga - Taiga Community
Taiga Pricing, Alternatives & More 2024
What these github repos stars are telling us, whether we wanted them or not, Kaleidos Blog
How Agile Spikes help to Improve your Agile Product Delivery?, by Anca Onuta
Spikes in Agile: Uncertainty's Archnemesis
Why Taiga? What makes Taiga's core proposition? - FAQ - Taiga Community