Jan 01, 2006
Simon Baker

Read our latest thinking on spikes.

A spike is an experiment that allows developers to learn just enough about something unknown in a user story, e.g. a new technology, to be able to estimate that user story. A spike must be time-boxed. This defines the maximum time that will be spent learning and fixes the estimate for the spike. William McKnight of 3M once said “Give it a try – and quick”.

1 Comment. Leave new

Real Options: Embracing Uncertainty | agile at heart
27th October 2014 5:23 pm

[…] can help to resolve uncertainty before investing in an option. In product development, we use a Spike to test risky decisions. Whilst the option to test an architecture or technical option before […]


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>