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
Innovation in Agile: 4 different approaches to stay competitive - Improve your Agile with Taiga - Taiga Community
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
Derive Benefits with Spike in Agile
Agile - Spikes and the art to run them!
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
What is a spike in Agile? - Improve your Agile with Taiga - Taiga Community
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
The Best 32 Project Management Tools 2020 [Unbiased]
How Agile Spikes help to Improve your Agile Product Delivery?, by Anca Onuta
Taiga - agile project management tool. Free & Open Source.
What is an Agile Spike Story? How to Use, Types & Benefits
The Burn-up Chart: A Game Changer for Managing Agile Team Progress - Improve your Agile with Taiga - Taiga Community