Spike

scroll down arrow
go back arrowGo Back
In Uncategorized

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”.

Simon Baker
Simon Baker
Simon Baker is chief swashbuckler at Energized Work, a guerrilla technology lab based onboard HMS President in London. Simon cofounded Energized Work and in 2009 received the Agile Alliance Gordon Pask Award. He speaks internationally about applying agile and lean principles and techniques in business, software development, and information technology. With 22 years experience delivering software in the media, retail, healthcare, financial services and banking sectors, Simon is a leader doing things differently to find out what matters and get the right things done in the right way. He isn't afraid to question conventional thinking and disrupt the status quo. Simon feels strongly that work shouldn't feel like work and he has a track record creating exciting working conditions that help people change the way they deliver software for the better.
Comments
pingbacks / trackbacks
  • […] 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 Comment

Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.