By A Mystery Man Writer
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
Agile - Spikes and the art to run them!
Agile Spikes Deliver Knowledge So Teams Can Deliver Products
What these github repos stars are telling us, whether we wanted them or not
The Best 32 Project Management Tools 2020 [Unbiased]
How Agile Spikes help to Improve your Agile Product Delivery?, by Anca Onuta
How to measure sprint progress through closed tasks - Improve your Agile with Taiga - Taiga Community
New to Taiga what is the difference between an issue and a task? - Taiga basics - Taiga Community
Derive Benefits with Spike in Agile
Agile - Spikes and the art to run them!
5 different setups for agile projects: Priority driven organic workflow
Taiga, the Best Tool for Agile Project Management + Case Study
Latest Improve your Agile with Taiga topics - Taiga Community
Move individual tasks from a user story to a given sprint - Improve your Agile with Taiga - Taiga Community