<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Sprint Planning · Jared Lynskey</title>
    <link>https://jared.lynskey.co.nz/en/tags/sprint-planning/</link>
    <description>Short stories of value on software engineering and engineering leadership — performance reviews, hiring and scaling teams, CI/CD, DevOps monitoring and agentic AI. Written from Seoul.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2026 Jared Lynskey</copyright>
    <lastBuildDate>Mon, 16 Nov 2026 00:00:00 +1300</lastBuildDate>
    <atom:link href="https://jared.lynskey.co.nz/en/tags/sprint-planning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Definition of Done vs Acceptance Criteria, With Examples</title>
      <link>https://jared.lynskey.co.nz/en/posts/2026/definition-of-done-vs-acceptance-criteria/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2026/definition-of-done-vs-acceptance-criteria/</guid>
      <pubDate>Mon, 16 Nov 2026 00:00:00 +1300</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Definition of Done</category>
      <category>Acceptance Criteria</category>
      <category>Agile</category>
      <category>Scrum</category>
      <category>User Stories</category>
      <category>Sprint Planning</category>
      <category>User Acceptance Testing</category>
      <category>Managing</category>
      <description>Acceptance criteria say what one story must do. The Definition of Done is the quality checklist every story must pass. How they differ, with examples and templates.</description>
      <content:encoded><![CDATA[<p>Acceptance criteria are the conditions one user story has to meet before the product owner accepts it. They describe what this particular piece of work should do. The Definition of Done is a single checklist the whole team applies to every story, whatever it is: the quality bar the work has to clear before anyone calls it finished. Acceptance criteria answer &ldquo;did we build the right thing?&rdquo; and are different for every story. The Definition of Done answers &ldquo;did we build it properly?&rdquo; and barely changes from one sprint to the next. A story is done when it passes both.</p>
<p>People mix them up for understandable reasons. Both are lists of checkboxes, both sit at the bottom of a ticket, and both decide whether something gets to move to the last column of the board. The argument they cause usually goes like this. A developer says a story is done because it does everything the ticket asked for. Someone else says it isn&rsquo;t, because it hasn&rsquo;t been reviewed, or it&rsquo;s only been tested on a laptop, or nobody has looked at the Korean error messages. They&rsquo;re both right, about different lists. When I wrote down the <a href="https://jared.lynskey.co.nz/en/posts/2024/2024-05-05-team-norms/" >team norms</a> for the first team I managed, &ldquo;what done actually means&rdquo; was one of the unspoken assumptions on the list, and this distinction is most of the answer.</p>

<h2 class="relative group">The difference in one table
    <div id="the-difference-in-one-table" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-difference-in-one-table" aria-label="Anchor">#</a>
    </span>
    
</h2>
<table>
	<thead>
			<tr>
					<th></th>
					<th>Acceptance criteria</th>
					<th>Definition of Done</th>
			</tr>
	</thead>
	<tbody>
			<tr>
					<td>Applies to</td>
					<td>One user story or backlog item</td>
					<td>Every item the team finishes</td>
			</tr>
			<tr>
					<td>Question it answers</td>
					<td>Does it do what this story needs?</td>
					<td>Is it built to our standard?</td>
			</tr>
			<tr>
					<td>Written by</td>
					<td>The product owner, refined with the developers</td>
					<td>The whole team, or the organisation as a minimum</td>
			</tr>
			<tr>
					<td>Written when</td>
					<td>Before the story enters a sprint, in refinement</td>
					<td>Once, then revisited in retrospectives</td>
			</tr>
			<tr>
					<td>How often it changes</td>
					<td>Different for every story</td>
					<td>Rarely, and it should only get stricter</td>
			</tr>
			<tr>
					<td>In the Scrum Guide?</td>
					<td>Not mentioned</td>
					<td>Yes, as the commitment for the Increment</td>
			</tr>
			<tr>
					<td>Example</td>
					<td>&ldquo;An expired reset link says so and offers a new one&rdquo;</td>
					<td>&ldquo;Reviewed by another developer, tests pass in CI&rdquo;</td>
			</tr>
	</tbody>
</table>
<p>The Scrum Guide row surprises people. The 2020 guide defines the Definition of Done as &ldquo;a formal description of the state of the Increment when it meets the quality measures required for the product&rdquo;, and says that an item that doesn&rsquo;t meet it &ldquo;cannot be released or even presented at the Sprint Review&rdquo;. Acceptance criteria don&rsquo;t appear in it at all. They come from the user story tradition, Extreme Programming and later behaviour-driven development, and most Scrum teams use them anyway because a story without them is an invitation to guess.</p>

<h2 class="relative group">One story, both lists
    <div id="one-story-both-lists" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#one-story-both-lists" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Here&rsquo;s a story most products have somewhere in their backlog:</p>
<blockquote><p>As a customer who has forgotten my password, I want to reset it by email so that I can get back into my account.</p>
</blockquote><p>Its acceptance criteria, written as Given/When/Then scenarios:</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gherkin" data-lang="gherkin"><span class="line"><span class="cl"><span class="k">Scenario:</span><span class="nf"> Requesting a reset link
</span></span></span><span class="line"><span class="cl"><span class="k">  Given </span><span class="nf">I&#39;m on the sign-in page
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">When </span><span class="nf">I choose &#34;</span><span class="s">Forgot password</span><span class="nf">&#34; and enter the email address on my account
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">Then </span><span class="nf">I receive a reset link by email within a minute
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">And </span><span class="nf">the page tells me to check my inbox
</span></span></span><span class="line"><span class="cl"><span class="nf">
</span></span></span><span class="line"><span class="cl"><span class="k">Scenario:</span><span class="nf"> Email address with no account
</span></span></span><span class="line"><span class="cl"><span class="k">  Given </span><span class="nf">no account uses the address I enter
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">When </span><span class="nf">I request a reset link
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">Then </span><span class="nf">the page shows the same &#34;</span><span class="s">check your inbox</span><span class="nf">&#34; message
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">And </span><span class="nf">no email is sent
</span></span></span><span class="line"><span class="cl"><span class="nf">
</span></span></span><span class="line"><span class="cl"><span class="k">Scenario:</span><span class="nf"> Expired link
</span></span></span><span class="line"><span class="cl"><span class="k">  Given </span><span class="nf">my reset link is more than </span><span class="s">30</span><span class="nf"> minutes old
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">When </span><span class="nf">I open it
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">Then </span><span class="nf">I see that the link has expired
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">And </span><span class="nf">I can request a new one from the same page
</span></span></span><span class="line"><span class="cl"><span class="nf">
</span></span></span><span class="line"><span class="cl"><span class="k">Scenario:</span><span class="nf"> Choosing the new password
</span></span></span><span class="line"><span class="cl"><span class="k">  Given </span><span class="nf">I&#39;ve opened a valid reset link
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">When </span><span class="nf">I enter a new password that meets the password rules
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">Then </span><span class="nf">I&#39;m signed in
</span></span></span><span class="line"><span class="cl"><span class="nf">  </span><span class="k">And </span><span class="nf">the old password and any other reset links stop working</span></span></span></code></pre></div></div>
<p>The second scenario is the kind of thing acceptance criteria are for. Showing the same message whether or not an account exists stops the form from telling strangers which email addresses are registered. That&rsquo;s a product decision, someone has to make it, and the best time to make it is before anyone writes the code, not in a review comment afterwards.</p>
<p>And here&rsquo;s the team&rsquo;s Definition of Done. It&rsquo;s the same for this story as for every other one:</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl"><span class="k">- [ ]</span> Code reviewed and approved by another developer
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Automated tests written for the new behaviour, all passing in CI
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Acceptance criteria checked on staging, not only locally
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> No new errors in the error tracker after the staging deploy
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> User-facing text added in every language the product supports
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> API docs or changelog updated if behaviour changed
</span></span><span class="line"><span class="cl">- [ ] Product owner has seen it working</span></span></code></pre></div></div>
<p>Notice the third line. The Definition of Done says the acceptance criteria have to be met, and the acceptance criteria say what they are. That&rsquo;s how the two lists connect, and it&rsquo;s why neither one should try to do the other&rsquo;s job.</p>

<h2 class="relative group">Where the Definition of Ready fits
    <div id="where-the-definition-of-ready-fits" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#where-the-definition-of-ready-fits" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>The third term in this family is the Definition of Ready: a short checklist a story has to meet before the team pulls it into a sprint. A typical one asks for acceptance criteria, an estimate, known dependencies, and a size the team can finish within the sprint. It isn&rsquo;t in the Scrum Guide either. The 2020 guide only says that items &ldquo;that can be Done by the Scrum Team within one Sprint are deemed ready for selection&rdquo;.</p>
<p>So the order is: the Definition of Ready at the start, acceptance criteria written before the sprint and checked at the end, and the Definition of Done at the finish line. A story with no acceptance criteria isn&rsquo;t ready. If it can&rsquo;t get them because nobody knows enough yet, it probably needs a <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/" >spike</a> first. Keep the Definition of Ready short, though. Treated as a strict gate, it turns into a way of refusing work, and the useful conversations about a half-understood story stop happening.</p>

<h2 class="relative group">Writing acceptance criteria that help
    <div id="writing-acceptance-criteria-that-help" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#writing-acceptance-criteria-that-help" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Describe what the user or the system does, not the tasks. &ldquo;Create a reset_tokens table&rdquo; is how you&rsquo;ll build it, and it belongs in the developers&rsquo; plan. &ldquo;The old password stops working&rdquo; is what has to be true, and that&rsquo;s a criterion.</p>
<p>Make each one pass or fail without debate. &ldquo;The email arrives quickly&rdquo; will be argued about at the review, and &ldquo;within a minute&rdquo; won&rsquo;t.</p>
<p>Cover the unhappy paths. The expired link, the unregistered address and the second click on the same link are where the bugs live, and they&rsquo;re also where the undecided product questions hide.</p>
<p>Aim for somewhere between three and seven. Much more than that and the story is usually two stories.</p>
<p>Pick the format per story. Given/When/Then comes from behaviour-driven development and maps directly onto automated tests and UAT scripts, which is why I like it for anything with a flow. A plain checklist is fine for simple rules (&ldquo;the field accepts 1–200 characters&rdquo;). Forcing every criterion into Given/When/Then just produces long sentences.</p>
<p>Write them in refinement, with developers in the room. The product owner owns them, but the people who&rsquo;ll build the thing are the ones who ask &ldquo;what happens if the link is opened twice?&rdquo;</p>

<h2 class="relative group">Writing a Definition of Done people actually use
    <div id="writing-a-definition-of-done-people-actually-use" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#writing-a-definition-of-done-people-actually-use" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Start with what the team already does on a good day, not with an aspirational list. A Definition of Done that everyone quietly skips half of is worse than none, because it teaches the team that the checklist is decoration.</p>
<p>Put it where the work happens. The teams I&rsquo;ve worked on kept theirs on a wiki page. That beats not writing it down at all, but a page only gets read when someone remembers to open it, and that tends to be at the retrospective. A checklist in the pull request template gets ticked on every change:</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl"><span class="cm">&lt;!-- .github/pull_request_template.md --&gt;</span>
</span></span><span class="line"><span class="cl"><span class="gu">## What changed and why
</span></span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">## Definition of Done
</span></span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Tests added or updated, passing in CI
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Acceptance criteria checked on staging
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> New user-facing text added in every supported language
</span></span><span class="line"><span class="cl">- [ ] Docs or changelog updated if behaviour changed</span></span></code></pre></div></div>
<p>Make every line checkable. &ldquo;Code is clean&rdquo; isn&rsquo;t a line anyone can tick honestly. &ldquo;Reviewed and approved by another developer&rdquo; is.</p>
<p>Raise the bar on purpose. When the team is comfortably meeting the current list, add the next thing, such as a feature flag for anything risky or an alert for anything new that can fail quietly. The <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-09-01-retrospecs/" >retrospective</a> is the natural place to decide that.</p>
<p>If several teams work on one product, the Scrum Guide says they &ldquo;must mutually define and comply with the same Definition of Done&rdquo;. And if the organisation has a standard one, every team follows it &ldquo;as a minimum&rdquo;, which leaves teams free to add to it but not to take anything away.</p>

<h2 class="relative group">Mistakes I&rsquo;d watch for
    <div id="mistakes-id-watch-for" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#mistakes-id-watch-for" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Copying the Definition of Done into every story&rsquo;s acceptance criteria. &ldquo;Tests written&rdquo; and &ldquo;code reviewed&rdquo; don&rsquo;t belong in a story. They bloat every ticket and hide the criteria that are actually about the story.</p>
<p>Acceptance criteria that are really tasks, or really designs. &ldquo;Use a modal&rdquo; is a design decision. &ldquo;I can request a new link without leaving the page&rdquo; is a criterion, and it leaves the designer room to do better than a modal.</p>
<p>Changing acceptance criteria halfway through the sprint without saying so. If the requirement has changed, that&rsquo;s a conversation with the product owner and often a new story, not a quiet edit to the old one.</p>
<p>&ldquo;Done, but not done-done.&rdquo; If a story counts as done when it&rsquo;s merged but before anyone has checked it on staging, the team is running two definitions and calling them one. Say in the Definition of Done exactly where done ends.</p>
<p>A Definition of Done so long that nobody can meet it in a sprint. Then everyone skips different lines and nobody says so.</p>

<h2 class="relative group">How they connect to UAT
    <div id="how-they-connect-to-uat" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#how-they-connect-to-uat" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Acceptance criteria are the natural starting point for <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-08-27-user-acceptance-testing/" >user acceptance testing</a>: each scenario becomes a test case someone outside the team can follow. UAT also checks the criteria themselves. Sometimes users get through every scenario and still can&rsquo;t do their job, which means the criteria were wrong, not the code. That&rsquo;s useful to know before the next story is written.</p>

<h2 class="relative group">Templates
    <div id="templates" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#templates" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Acceptance criteria:</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl">**Story:** As a [kind of user], I want [goal] so that [reason].
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gs">**Acceptance criteria**</span>
</span></span><span class="line"><span class="cl"><span class="k">-</span> Given [starting state], when [action], then [result].
</span></span><span class="line"><span class="cl"><span class="k">-</span> Given [starting state], when [action], then [result].
</span></span><span class="line"><span class="cl"><span class="k">-</span> Given [starting state], when [action], then [result].
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gs">**Out of scope:**</span> [what this story deliberately doesn&#39;t do]</span></span></code></pre></div></div>
<p>The &ldquo;out of scope&rdquo; line is optional, and I&rsquo;d keep it. It ends a lot of review-time arguments before they start.</p>
<p>A starting Definition of Done, to cut down or add to:</p>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl"><span class="k">- [ ]</span> Code reviewed and approved by another developer
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Automated tests written and passing in CI
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Acceptance criteria checked on staging
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> No new errors or warnings in monitoring after the staging deploy
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> User-facing text added in every supported language
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> Docs, changelog or release notes updated if behaviour changed
</span></span><span class="line"><span class="cl">- [ ] Product owner has seen it working</span></span></code></pre></div></div>

<h2 class="relative group">The short version
    <div id="the-short-version" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-short-version" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p>Acceptance criteria belong to one story. They say what it must do, they&rsquo;re written by the product owner with the team before the sprint, and they&rsquo;re different every time. The Definition of Done belongs to the team. It&rsquo;s one checklist of quality standards every story has to pass, it lives somewhere the team sees it on every change, and it only changes when the team decides to raise the bar. The Definition of Ready, if you use one, sits in front of both and says a story has enough detail, acceptance criteria included, to be worth starting.</p>

<h2 class="relative group">Further reading
    <div id="further-reading" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#further-reading" aria-label="Anchor">#</a>
    </span>
    
</h2>
<p><strong>On this site:</strong></p>
<ul>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/" >What Is a Spike in Agile?</a> for the stories that can&rsquo;t get acceptance criteria yet</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-08-27-user-acceptance-testing/" >User Acceptance Testing (UAT)</a>, where acceptance criteria become test scripts</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2024/2024-05-05-team-norms/" >Engineering Team Norms That Actually Stick</a>, including agreeing what &ldquo;done&rdquo; means</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-09-01-retrospecs/" >Retrospectives</a>, where the Definition of Done should get revisited</li>
</ul>
<p><strong>Elsewhere:</strong></p>
<ul>
<li><a href="https://scrumguides.org/scrum-guide.html"  target="_blank" rel="noreferrer">The Scrum Guide (2020)</a>, for the Definition of Done in its own words</li>
<li><a href="https://dannorth.net/introducing-bdd/"  target="_blank" rel="noreferrer">Introducing BDD</a> by Dan North, where Given/When/Then comes from</li>
<li><a href="https://martinfowler.com/bliki/GivenWhenThen.html"  target="_blank" rel="noreferrer">Given When Then</a> by Martin Fowler</li>
</ul>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2026/definition-of-done-vs-acceptance-criteria/featured.jpg" medium="image" type="image/jpeg" />
    </item>
    <item>
      <title>What Is a Spike in Agile? When Your Team Can&#39;t Estimate a Story</title>
      <link>https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/</link>
      <guid isPermaLink="true">https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/</guid>
      <pubDate>Wed, 18 Oct 2023 00:30:03 +0000</pubDate>
      <dc:creator>Jared Lynskey</dc:creator>
      <category>Managing</category>
      <category>Spike</category>
      <category>Agile</category>
      <category>Development</category>
      <category>Scrum</category>
      <category>Technical Debt</category>
      <category>XP</category>
      <category>Sprint Planning</category>
      <category>Risk Management</category>
      <description>In agile and Scrum, a spike is a short, time-boxed investigation that answers one specific question, so a story nobody could estimate can be. When one is worth running, technical vs functional spikes, how I structure one, and the template I use.</description>
      <content:encoded><![CDATA[<p>In agile and Scrum teams, a spike is a short, time-boxed investigation, usually one to three days, that answers one specific question so the story that was stuck on it can be estimated. You come out of it with findings and a recommendation, not code you&rsquo;d ship. Run one instead of estimating when it&rsquo;s the unknowns, not the size of the work, that stop the team putting a number on a story.</p>
<p>Every so often in sprint planning, a story lands that nobody can point. Estimates range from a 2 to a 13, someone says &ldquo;well, it depends&rdquo;, and the discussion goes in circles. <em>Should we use GraphQL or REST? Can the system actually handle 10,000 concurrent users? Is this third-party library production-ready?</em> You can&rsquo;t estimate your way out of questions like that. You have to go and find out. That&rsquo;s what a spike is for.</p>
<figure><div class="film-pair">
  <div class="mc-film film-dark">
  <video
    class="my-0 rounded-md"
    controls playsinline preload="none"
    poster="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film-poster.jpg" style="background:url('data:image/webp;base64,UklGRnIAAABXRUJQVlA4IGYAAADQBACdASogABIAPw1urEqmIyIYDAQAYxDE9IABUYPdO/3zunWXI5Y++RXZ033PzAD+69Brt+c++t0PqdK8JhIPZzv0VGuupeeaSXpH9idHVq2vGiKrk0KLlu00ZC2+riXAfWPqAAA=') center/cover no-repeat"
    width="1280"
    height="720"
    aria-label="A short narrated film of this post">
    <source src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film.webm" type="video/webm">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_en.vtt" srclang="en" label="English">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_ja.vtt" srclang="ja" label="日本語">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_ko.vtt" srclang="ko" label="한국어">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_vi.vtt" srclang="vi" label="Tiếng Việt">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_zh-cn.vtt" srclang="zh-cn" label="简体中文">
  </video>
  </div>
  <div class="mc-film film-light">
  <video
    class="my-0 rounded-md"
    controls playsinline preload="none"
    poster="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film-light-poster.jpg" style="background:url('data:image/webp;base64,UklGRoYAAABXRUJQVlA4IHoAAAAQBQCdASogABIAPw1uqUemIyIYBABjEMT0gAFRZY1nI7e+Z9WXp25bT866PmeGEKMAAP7vuc/vn2NnuWoVrgzJhJogpo5KKhxNgO07wl/eccgzsx50emjDH9WsqjRurx3jQoIxUmSB4LbUXTJj/75F99Y44I/KAAAAAA==') center/cover no-repeat"
    width="1280"
    height="720"
    aria-label="A short narrated film of this post">
    <source src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film-light.webm" type="video/webm">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_en.vtt" srclang="en" label="English">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_ja.vtt" srclang="ja" label="日本語">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_ko.vtt" srclang="ko" label="한국어">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_vi.vtt" srclang="vi" label="Tiếng Việt">
    <track kind="subtitles" src="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/spike-film_zh-cn.vtt" srclang="zh-cn" label="简体中文">
  </video>
  </div>
  <script>(function(){if(window.mcFilm)return window.mcFilm();var a={play:'<path d="M8 5.6v12.8a1 1 0 0 0 1.52.85l10.2-6.4a1 1 0 0 0 0-1.7L9.52 4.75A1 1 0 0 0 8 5.6z"/>',pause:'<rect x="6.5" y="5" width="4" height="14" rx="1.2"/><rect x="13.5" y="5" width="4" height="14" rx="1.2"/>',volume:'<path d="M4 9.5v5a1 1 0 0 0 1 1h3l4.4 3.6a.6.6 0 0 0 1-.47V5.37a.6.6 0 0 0-1-.47L8 8.5H5a1 1 0 0 0-1 1z"/><path d="M16.5 8.5a5 5 0 0 1 0 7M19 6a8.5 8.5 0 0 1 0 12" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/>',muted:'<path d="M4 9.5v5a1 1 0 0 0 1 1h3l4.4 3.6a.6.6 0 0 0 1-.47V5.37a.6.6 0 0 0-1-.47L8 8.5H5a1 1 0 0 0-1 1z"/><path d="M16.5 9.5l5 5m0-5l-5 5" fill="none" stroke="currentColor" stroke-width="1.8" stroke-linecap="round"/>',cc:'<rect x="3" y="5.5" width="18" height="13" rx="3" fill="none" stroke="currentColor" stroke-width="1.8"/><path d="M10.5 10.3a2.2 2.2 0 1 0 0 3.4M17 10.3a2.2 2.2 0 1 0 0 3.4" fill="none" stroke="currentColor" stroke-width="1.6" stroke-linecap="round"/>',full:'<path d="M4.5 9V5.5a1 1 0 0 1 1-1H9M15 4.5h3.5a1 1 0 0 1 1 1V9M19.5 15v3.5a1 1 0 0 1-1 1H15M9 19.5H5.5a1 1 0 0 1-1-1V15" fill="none" stroke="currentColor" stroke-width="1.9" stroke-linecap="round"/>',exit:'<path d="M9 4.5V8a1 1 0 0 1-1 1H4.5M19.5 9H16a1 1 0 0 1-1-1V4.5M15 19.5V16a1 1 0 0 1 1-1h3.5M4.5 15H8a1 1 0 0 1 1 1v3.5" fill="none" stroke="currentColor" stroke-width="1.9" stroke-linecap="round"/>'},s={en:["Play","Pause","Mute","Unmute","Subtitles","Off","Full screen","Exit full screen","Seek"],ko:["재생","일시정지","음소거","음소거 해제","자막","끄기","전체 화면","전체 화면 종료","탐색"],ja:["再生","一時停止","ミュート","ミュート解除","字幕","オフ","全画面","全画面を終了","シーク"],zh:["播放","暂停","静音","取消静音","字幕","关闭","全屏","退出全屏","进度"],vi:["Phát","Tạm dừng","Tắt tiếng","Bật tiếng","Phụ đề","Tắt","Toàn màn hình","Thoát toàn màn hình","Tua"]},r=(document.documentElement.lang||"en").toLowerCase().slice(0,2),e=s[r]||s.en,t=function(e){return'<svg viewBox="0 0 24 24" aria-hidden="true" focusable="false">'+a[e]+"</svg>"},o={},i=function(e,t){if(o[e]||typeof window.gtag!="function")return;o[e]=!0;var n=(t.currentSrc||(t.querySelector("source")||{}).src||"").split("/").pop();window.gtag("event",e,{film:n.replace(/-light(?=\.)/,"")})},n=function(e){(!isFinite(e)||e<0)&&(e=0),e=Math.floor(e);var t=Math.floor(e/3600),n=Math.floor(e%3600/60),s=String(e%60).padStart(2,"0");return t?t+":"+String(n).padStart(2,"0")+":"+s:n+":"+s};function c(s){var a,r,c,d,u,m,p,g,v,b,j,_,w,O,C,E,k,A,o=s.querySelector("video");if(!o)return;s.classList.add("is-ready"),o.controls=!1,o.removeAttribute("controls"),s.insertAdjacentHTML("beforeend",'<button type="button" class="mc-film__big" aria-label="'+e[0]+'">'+t("play")+'</button><div class="mc-film__bar"><button type="button" class="mc-film__btn" data-act="play" aria-label="'+e[0]+'">'+t("play")+'</button><span class="mc-film__time"><span data-cur>0:00</span><span class="mc-film__of"> / </span><span data-dur>0:00</span></span><input class="mc-film__seek" type="range" min="0" max="1000" step="1" value="0" aria-label="'+e[8]+'"><span class="mc-film__cc"><button type="button" class="mc-film__btn" data-act="cc" aria-label="'+e[4]+'" aria-haspopup="true" aria-expanded="false">'+t("cc")+'</button><span class="mc-film__menu" role="menu" hidden></span></span><button type="button" class="mc-film__btn" data-act="mute" aria-label="'+e[2]+'">'+t("volume")+'</button><button type="button" class="mc-film__btn" data-act="full" aria-label="'+e[6]+'">'+t("full")+"</button></div>"),A=s.querySelector(".mc-film__big"),a=s.querySelector(".mc-film__bar"),j=a.querySelector('[data-act="play"]'),p=a.querySelector('[data-act="mute"]'),u=a.querySelector('[data-act="full"]'),d=a.querySelector('[data-act="cc"]'),r=a.querySelector(".mc-film__menu"),c=a.querySelector(".mc-film__seek"),w=a.querySelector("[data-cur]"),O=a.querySelector("[data-dur]"),g=!1,v=0,b=function(){return Array.prototype.filter.call(o.textTracks,function(e){return e.kind==="subtitles"||e.kind==="captions"})},b().length||(d.parentNode.hidden=!0),_=null;function f(e){var n,i,t=!s.classList.contains("is-idle")&&s.classList.contains("is-started");if(e!==!0&&t===_)return;_=t,n=o.clientHeight,i=n?Math.max(40,100-(a.offsetHeight+22)/n*100):85,b().forEach(function(e){if(e.mode!=="showing"||!e.cues)return;for(var n,s=0;s<e.cues.length;s++)n=e.cues[s],t?(n.snapToLines=!1,n.line=i,n.lineAlign="end"):(n.snapToLines=!0,n.line="auto",n.lineAlign="start")})}m=function(){f(!0)},window.addEventListener("resize",m),Array.prototype.forEach.call(o.querySelectorAll("track"),function(e){e.addEventListener("load",m)});function y(){o.paused||o.ended?o.play().catch(function(){}):o.pause()}function l(){s.classList.remove("is-idle"),f(),clearTimeout(v),v=setTimeout(function(){!o.paused&&r.hidden&&!a.querySelector(":focus-visible")&&(s.classList.add("is-idle"),f())},2600)}function M(){clearTimeout(v),h(),s.classList.add("is-idle"),f()}function h(){r.hidden=!0,d.setAttribute("aria-expanded","false")}function F(){var t=b(),n=t.filter(function(e){return e.mode==="showing"})[0];r.innerHTML="",[null].concat(t).forEach(function(s){var o=document.createElement("button");o.type="button",o.setAttribute("role","menuitemradio"),o.setAttribute("aria-checked",String(s?s===n:!n)),o.textContent=s?s.label||s.language:e[5],o.addEventListener("click",function(){t.forEach(function(e){e.mode=e===s?"showing":"disabled"}),h(),setTimeout(m,0),l()}),r.appendChild(o)}),r.hidden=!1,d.setAttribute("aria-expanded","true")}function x(){var n=!o.paused&&!o.ended;s.classList.toggle("is-playing",n),j.innerHTML=t(n?"pause":"play"),j.setAttribute("aria-label",n?e[1]:e[0]),n||l()}function S(){if(w.textContent=n(o.currentTime),!g&&o.duration){var e=o.currentTime/o.duration*1e3;c.value=e,c.style.setProperty("--p",e/10+"%")}}A.addEventListener("click",function(){o.play().catch(function(){})}),C="mouse",s.addEventListener("pointerdown",function(e){C=e.pointerType}),o.addEventListener("click",function(){if(!s.classList.contains("is-started"))return o.play().catch(function(){});if(C==="mouse")return y();s.classList.contains("is-idle")?l():M()}),j.addEventListener("click",y),o.addEventListener("play",function(){s.classList.contains("is-started")||i("film_play",o),s.classList.add("is-started"),x(),l()}),"IntersectionObserver"in window&&(E=new IntersectionObserver(function(e){if(!e.some(function(e){return e.isIntersecting}))return;E.disconnect(),i("film_view",o)},{threshold:.5}),E.observe(s)),o.addEventListener("pause",x),o.addEventListener("ended",x),o.addEventListener("timeupdate",S),o.addEventListener("durationchange",function(){O.textContent=n(o.duration),S()}),o.addEventListener("loadedmetadata",function(){O.textContent=n(o.duration)}),o.addEventListener("volumechange",function(){p.innerHTML=t(o.muted?"muted":"volume"),p.setAttribute("aria-label",o.muted?e[3]:e[2])}),p.addEventListener("click",function(){o.muted=!o.muted}),c.addEventListener("input",function(){g=!0,c.style.setProperty("--p",c.value/10+"%"),o.duration&&(o.currentTime=c.value/1e3*o.duration,w.textContent=n(o.currentTime))}),c.addEventListener("change",function(){g=!1}),d.addEventListener("click",function(e){e.stopPropagation(),r.hidden?F():h()}),document.addEventListener("click",function(e){!r.hidden&&!r.contains(e.target)&&h()}),u.addEventListener("click",function(){document.fullscreenElement||document.webkitFullscreenElement?(document.exitFullscreen||document.webkitExitFullscreen).call(document):s.requestFullscreen?s.requestFullscreen().catch(function(){}):s.webkitRequestFullscreen?s.webkitRequestFullscreen():o.webkitEnterFullscreen&&o.webkitEnterFullscreen()}),k=function(){var n=(document.fullscreenElement||document.webkitFullscreenElement)===s;s.classList.toggle("is-fullscreen",n),u.innerHTML=t(n?"exit":"full"),u.setAttribute("aria-label",n?e[7]:e[6])},document.addEventListener("fullscreenchange",k),document.addEventListener("webkitfullscreenchange",k),s.addEventListener("pointermove",function(e){e.pointerType==="mouse"&&l()}),s.addEventListener("focusin",l),s.addEventListener("keydown",function(e){if(e.target===c&&/^Arrow/.test(e.key))return;var t=e.key.toLowerCase();if(t==="k"||t===" "&&e.target===o)y();else if(t==="arrowleft")o.currentTime=Math.max(0,o.currentTime-5);else if(t==="arrowright")o.currentTime=Math.min(o.duration||0,o.currentTime+5);else if(t==="m")o.muted=!o.muted;else if(t==="f")u.click();else if(t==="escape"&&!r.hidden)h();else return;e.preventDefault(),l()}),o.tabIndex=0}window.mcFilm=function(){document.querySelectorAll(".mc-film:not(.is-ready)").forEach(c)},window.mcFilm()})()</script></div>
  <script>
  new MutationObserver(() => {
    const dark = document.documentElement.classList.contains("dark");
    document.querySelectorAll(".film-pair").forEach((pair) => {
      const from = pair.querySelector(dark ? ".film-light video" : ".film-dark video");
      const to = pair.querySelector(dark ? ".film-dark video" : ".film-light video");
      if (!from || !to || !from.currentTime) return;
      const playing = !from.paused;
      from.pause();
      to.currentTime = from.currentTime;
      [...from.textTracks].forEach((track, i) => { if (to.textTracks[i]) to.textTracks[i].mode = track.mode; });
      if (playing) to.play().catch(() => {});
    });
  }).observe(document.documentElement, { attributes: true, attributeFilter: ["class"] });
  </script><figcaption>This post as an eight-minute film, if you&rsquo;d rather watch than read.</figcaption>
</figure>


<h4 class="relative group">Where spikes come from
    <div id="where-spikes-come-from" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#where-spikes-come-from" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>The term is from Extreme Programming, where it meant a &ldquo;very simple program to explore potential solutions&rdquo; — driving a spike through the problem. The modern version is a short, time-boxed research task whose output is knowledge, not working software. A spike isn&rsquo;t a user story and delivers no customer value on its own, and that&rsquo;s fine. Its job is to answer one specific question so the real work can be estimated and planned honestly.</p>
<p>In practice they come in two flavours. Technical spikes explore the how: evaluating a framework or library, prototyping an architectural pattern, performance-testing under realistic conditions, or finding out how painful an integration will really be. Functional spikes explore the what: clarifying an ambiguous story, testing a UI idea with a throwaway prototype, or poking at domain complexity until it makes sense.</p>

<h4 class="relative group">Why they&rsquo;re worth the time
    <div id="why-theyre-worth-the-time" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-theyre-worth-the-time" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>Trying to estimate work with big unknowns gives you one of two things: padded estimates or missed deadlines. A spike converts &ldquo;no idea&rdquo; into actual data, so the team can commit to something with a straight face. It also replaces opinion wars with evidence — instead of arguing about which database is better, you spend two days measuring, and the findings feed straight into your <a href="https://jared.lynskey.co.nz/en/posts/2024/2024-12-03-decision-docs/" >decision documents</a>.</p>
<p>Mostly, though, it&rsquo;s cheap insurance. A two-day spike that reveals a library&rsquo;s limitations costs far less than discovering the same limitation three sprints into development.</p>

<h4 class="relative group">When a spike is (and isn&rsquo;t) the right call
    <div id="when-a-spike-is-and-isnt-the-right-call" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#when-a-spike-is-and-isnt-the-right-call" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>Reach for a spike when the team can&rsquo;t confidently estimate a story because of technical unknowns, when several viable options exist and you need data to pick one, when you&rsquo;re considering a new technology or integration, when performance is both uncertain and critical, or when requirements stay ambiguous no matter how many stakeholder meetings you sit through.</p>
<p>Don&rsquo;t use one for work the team already knows how to do, or as a way to delay a decision you could make with the information you have. And a spike is not a substitute for proper requirements gathering or <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-08-27-user-acceptance-testing/" >user acceptance testing</a> — it answers a question, it doesn&rsquo;t validate a product.</p>

<h4 class="relative group">How I run one
    <div id="how-i-run-one" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#how-i-run-one" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>Start by writing down the question. Not &ldquo;research caching&rdquo; but &ldquo;can a Redis cluster meet our 50ms latency requirement?&rdquo; Give it explicit scope — what&rsquo;s in, what&rsquo;s out — a time-box of one to three days (if it needs more, the question is too broad), and success criteria so you&rsquo;ll know when you&rsquo;re done.</p>
<p>Then investigate: read the docs and case studies, build a minimal proof of concept, talk to people who&rsquo;ve done it before, and measure things with real code. Spike code is disposable by design.</p>
<p>When the time-box ends, write up findings, a recommendation with the reasoning, and any risks you uncovered, with links to the prototype clearly marked as spike output. Present it to the team, take questions, and adjust the backlog — create, refine, or kill stories based on what you learned. It&rsquo;s also worth reflecting on how the spike itself went in your next <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-09-01-retrospecs/" >retrospective</a>; teams get noticeably better at spiking with practice.</p>

<h4 class="relative group">The template I use
    <div id="the-template-i-use" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-template-i-use" aria-label="Anchor">#</a>
    </span>
    
</h4>
<div class="highlight-wrapper"><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-markdown" data-lang="markdown"><span class="line"><span class="cl"><span class="gu">## Spike: [Title]
</span></span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gs">**Time-box**</span>: [X days]
</span></span><span class="line"><span class="cl"><span class="gs">**Owner**</span>: [Name]
</span></span><span class="line"><span class="cl"><span class="gs">**Sprint**</span>: [Sprint number/name]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Question to Answer
</span></span></span><span class="line"><span class="cl">[Single, focused question this spike will answer]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Background
</span></span></span><span class="line"><span class="cl">[Why this spike is needed; what triggered the uncertainty]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Assumptions
</span></span></span><span class="line"><span class="cl"><span class="k">-</span> [Assumption 1]
</span></span><span class="line"><span class="cl"><span class="k">-</span> [Assumption 2]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Scope
</span></span></span><span class="line"><span class="cl">**In Scope**:
</span></span><span class="line"><span class="cl"><span class="k">-</span> [Item 1]
</span></span><span class="line"><span class="cl"><span class="k">-</span> [Item 2]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gs">**Out of Scope**</span>:
</span></span><span class="line"><span class="cl"><span class="k">-</span> [Item 1]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Success Criteria
</span></span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> [Criterion 1]
</span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> [Criterion 2]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Findings
</span></span></span><span class="line"><span class="cl">[To be completed during spike]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Recommendation
</span></span></span><span class="line"><span class="cl">[To be completed after spike]
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="gu">### Follow-up Stories
</span></span></span><span class="line"><span class="cl"><span class="k">- [ ]</span> [Story 1]
</span></span><span class="line"><span class="cl">- [ ] [Story 2]</span></span></code></pre></div></div>
<p>The assumptions section earns its place. Writing down &ldquo;our data model is primarily relational&rdquo; and &ldquo;reads will outnumber writes 10:1&rdquo; before you start does two things: it lets people challenge your framing before you burn the time-box, and it means that if an assumption turns out to be wrong mid-spike, you&rsquo;ve learned something valuable rather than wasted two days.</p>

<h4 class="relative group">Ways spikes go wrong
    <div id="ways-spikes-go-wrong" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#ways-spikes-go-wrong" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>The classic failure is scope creep — the spike quietly becomes an open-ended research project. When new questions appear (they will), write them down as candidate spikes rather than expanding the current one. The second failure is goldplating: the moment you catch yourself adding error handling or tests to spike code, you&rsquo;ve crossed from exploration into implementation. Third, skipping the write-up — six months later someone will face the same question, and your two days of learning will be gone. And finally, treating the spike as a commitment to a predetermined answer. A spike that proves an approach won&rsquo;t work has done its job perfectly.</p>

<h4 class="relative group">Fitting them into sprint planning
    <div id="fitting-them-into-sprint-planning" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#fitting-them-into-sprint-planning" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>A few habits that have worked when <a href="https://jared.lynskey.co.nz/en/posts/2023/2023-10-08-planning-an-api/" >planning sprints</a>: if a story has real unknowns, spike it this sprint and schedule the actual work for a later one. Keep it to one or two spikes per sprint — more than that and focus evaporates. Don&rsquo;t put story points on spikes; they produce knowledge, not software, so track them by their time-box. And present spike findings during refinement, before the team estimates the related stories, not after.</p>
<p>The next time a story generates more questions than answers, consider that a spike might be the most useful work in the sprint. Sometimes the fastest way forward is to stop and learn.</p>

<h4 class="relative group">The short version
    <div id="the-short-version" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-short-version" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p>A spike is a time-boxed investigation, one to three days, into a single question the team can&rsquo;t estimate its way past. It&rsquo;s the right call when unknowns are what&rsquo;s blocking the estimate: several viable options and no data to choose between them, a new technology or integration, performance that&rsquo;s both uncertain and critical, or requirements that stay vague. It isn&rsquo;t for work the team already knows how to do, or for putting off a decision you could make with what you already know.</p>
<p>What it produces is knowledge rather than software: findings, a recommendation with the reasoning, the risks you uncovered and a throwaway prototype. The backlog changes to match. Spikes get a time-box rather than story points, and the findings should reach refinement before anyone estimates the related stories.</p>

<h4 class="relative group">Further Reading
    <div id="further-reading" class="anchor"></div>
    
    <span
        class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none">
        <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#further-reading" aria-label="Anchor">#</a>
    </span>
    
</h4>
<p><strong>Related Articles on This Site:</strong></p>
<ul>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-09-01-retrospecs/" >Retrospectives: Reflecting on Spike Outcomes</a> - Folding spike learnings into continuous improvement</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-08-27-user-acceptance-testing/" >User Acceptance Testing</a> - Validating that spike-informed decisions meet user needs</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2024/2024-12-03-decision-docs/" >Decision Documents</a> - Structuring the decisions that come out of spike findings</li>
<li><a href="https://jared.lynskey.co.nz/en/posts/2023/2023-10-08-planning-an-api/" >API Planning</a> - How spikes can inform API design decisions</li>
</ul>
<p><strong>External Resources:</strong></p>
<ul>
<li><a href="https://framework.scaledagile.com/spikes/"  target="_blank" rel="noreferrer">Spikes - Scaled Agile Framework (SAFe)</a> - The SAFe guide to spikes at scale</li>
<li><a href="http://www.extremeprogramming.org/rules/spike.html"  target="_blank" rel="noreferrer">Spike Solutions - Extreme Programming</a> - The original XP concept</li>
<li><a href="https://scrumguides.org/"  target="_blank" rel="noreferrer">The Scrum Guide</a> - Where spikes fit into sprint planning</li>
<li><a href="https://martinfowler.com/bliki/TechnicalDebt.html"  target="_blank" rel="noreferrer">Martin Fowler on Technical Debt</a> - How spikes help prevent technical debt</li>
</ul>
]]></content:encoded>
      <media:content url="https://jared.lynskey.co.nz/en/posts/2023/2023-10-18-spike/featured.jpeg" medium="image" type="image/jpeg" />
    </item>
  </channel>
</rss>
