Accounting for Spikes

This content is syndicated from George Dinwiddie's blog by George Dinwiddie. To view the original post in full, click here.

The term Spike Solution is associated in my mind with the early days of Extreme Programming.  I’m sure that it is built from prior ideas, as everything seems to be. If the term and the concept it describes predates the Chrysler C3 project (Ron Jeffries mentions using it there), I’ve not yet uncovered it. Ron credits Ward Cunningham for the term.  I’m sure there are predecessors, even if not expressed as distinctly.

The goal of a spike solution is to answer a question. For example, a spike may be used to test the feasibility of an algorithm or 3rd party library. It may be used to explore design alternatives for solving a sticky problem.  It’s called a spike because it drives all the way through the problem, but as narrowly focused as possible. It’s not a complete implementation. Associated complexity that is secondary to the question is likely stubbed out to reduce the clutter and increase the focus.

The output of a spike should be the answer to the question. It’s important to articulate the question as clearly as possible, as that helps in answering it. Sometimes “as clearly as possible” just isn’t very clear, though. When we don’t know something, we often can’t describe what it is that we don’t know.

We also often don’t know how long it will takes us to learn something that we don’t know. A spike is time-boxed so it doesn’t become a permanent research project. If, at the end of the timebox, the question is still unanswered, then you have a decision to make. You may decide to spend more effort on the answer, or to abandon it and try something else.

I frequently hear Scrum teams discovering the concept of a spike, particularly when they’re having a hard time estimating items in their product backlog. Sometimes they have an incomplete notion of what a spike is–hence the description above. Other times they wonder about how to account for them in the Scrum process.

If it takes more than minimal time and effort, I usually put a card on the wall (i.e. in the sprint backlog) to make the spike visible. It’s different from a story card, however, in that it has no value to the system. Sometimes people want to put them into their velocity to get “credit” for the work. It’s not an output of development, just a bit of work to aid the team. I reserve velocity for work delivered, not for work expended.

Sometimes people worry that they won’t correctly estimate the team’s capacity for work in a sprint if they don’t keep track of them. I would not worry too much about the “accounting” for spikes. They’re just part of dealing with the uncertainty of creation, though more visible than some other such parts. If spikes become a significant drain on the team’s productivity, I would ask myself “why is this happening?” Otherwise, I wouldn’t worry–they’re just part of the noise in the velocity data.

In fact, I would not generally use a spike just for the purpose of better estimation. It may be better to just do the story. If the estimation is wrong, well, that’s OK. That’s why they call it an estimate.

Leave a Reply

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

15 − 4 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch