Last Thursday, I shared some insights into why Technical Spikes often don't improve estimation accuracy.
The idea was simple:
Spikes shrink estimates ONLY WHEN they shrink the solution space, not when they confirm a solution exists.
What we need is a “Decision Spike.”
A Decision Spike is a session where we focus on clearly defining what will be built, what won't be, and the clarity needed to keep the timeline on track.
In today’s weekly recipe, I’m sharing the template to help you run a workshop for a Decision Spike.
It’s a 60-minute (time may vary) session that takes a stakeholder request (often a vague request) and turns it into confirmed increments with estimates, assumptions, and (most importantly) clear NOT-TO-DOs.
Note: This is more of a scoping session than a sprint planning. It's a great opportunity to get a clear understanding of a request as it first comes in, ideally before anyone starts writing anything.
Let’s get started.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
