Skip to content
BENIBIX Learn

Spike

Business📋 Agile DeliveryUser Stories

Also known as Spike Story, Research Spike

A short bit of research with a time limit. It answers a question so a story can be sized.

Think of it like

It is like dipping a toe in the pool before you jump in. A quick test tells you what you are in for.

Example

Jack's team does not know if a payment service can handle refunds. They spend two days on a spike. The answer lets them size the refund story at 5 points.

Why it matters

Guessing on a big unknown gives estimates nobody can trust. A small, fixed cost buys an answer first.

Definition

A spike is a short piece of research with a fixed time limit. A team uses one when it cannot size a story because something is unknown. They might try a new tool, or read how an old system works. The result is an answer, not a feature for users. With the answer, the team can split and size the real story. The name comes from Extreme Programming.
A story nobody can size gets a short spike first. The answer turns the question mark into a number.

Common mistake

Letting a spike run on with no end. Set the time limit up front, and stop when it runs out, answer or not.

Key takeaways

  1. 1
    Timeboxed. It has a fixed limit, like two days.
  2. 2
    Answers a question. It removes one unknown from a story.
  3. 3
    Learning, not product. The code it makes is often thrown away.

Learn it properly