Published on

Spike and Stabilise


As a team we are starting to work on some new use cases for business. There are quite a few unknowns involved in this use case.

A colleague of mine -who has worked in R&D for some time now- suggested an approach to mitigating this called spike and stabilise.

The idea is that on project inception we have a sprint where we work on a spike. A spike is a sprint dedicated to taking on as many of these unknowns as possible and experimenting with them to get a better understanding of them. The aim of these sprints is not to deliver on the agreed upon products but rather understand some of the complexities related to these products so that as a team we can more effectively deliver in future sprints.

Following the spike sprint we then enter the next sprint where we are in a better position to stabilise and estimate on upcoming work.