Agile & Delivery playbook/Module 4 · Backlog & requirements
Day 38 / 100 · Backlog & requirements · Spikes
Buy knowledge, not code.
A spike is a short, timeboxed piece of work to answer a question, so the team can make a decision or estimate with confidence.
01
Frame the question
One specific question the spike will answer.
02
Timebox it
Usually one to three days. Stop when time's up.
03
Build to learn
A throwaway prototype, a test, a proof of concept.
04
Share the answer
A decision, and the follow-up stories it creates.
Read this day in the full version