How do you spike a story to de-risk it and define deliverables?
Whether you see spikes as time-boxed research, not feature work. Propose a fixed duration, define the specific question, deliver a decision record or prototype, and revise the story estimate. Never treat a spike as production code or skip the time box.
What's really being asked
This question tests whether you understand that a spike is a time-boxed research activity whose sole purpose is to deliver knowledge, not working software. Interviewers want to see that you can separate exploration from implementation and that you know how to turn uncertainty into an actionable plan.
The full answer
First, scope the spike around a single clear question such as can we authenticate with this API using our current token strategy. Second, set a hard time box of one to three days and get team agreement before starting. Third, define concrete deliverables such as a proof of concept showing end to end connectivity, a decision record documenting rate limits and error handling patterns, and a list of follow up tasks needed for real implementation. Fourth, explain how you will present findings to the team and update the original story with a refined estimate based on what you learned.
The mistakes people make
A major red flag is suggesting the spike should produce production ready code that ships to users. Another is omitting a time box which turns the spike into an open ended research project. Saying you will just read the documentation without a defined stopping point or deliverable also signals weak risk management.
What usually comes next
The interviewer may ask how you handle a spike that fails to answer the question within the time box, how you prioritize spikes against feature work in the sprint, or whether the product owner should be involved in defining spike acceptance criteria.
A concrete example
Suppose the story is integrate the new payment provider. You propose a two day spike with the question can we successfully authorize a test transaction and handle the webhook response. Deliverables include a small throwaway script proving the handshake, a matrix mapping provider error codes to our retry policy, and a revised story pointing estimate that accounts for the idempotency work you discovered. After the spike you discard the script and write the real story with clear tasks.
Interview question
A team needs to de-risk a story about integrating a new payment provider. Which spike plan best demonstrates proper discipline?
- a.Create a one-week spike story with story points, aiming to deliver a production-ready payment module that can ship to users if tests pass.
- b.Pause feature work for one to three days so the team can freely explore the provider capabilities without a predefined question, then vote on the best path forward.
- c.Set a two-day time box and task a senior developer with reading the API documentation, sharing verbal findings at the next stand-up.
- d.Scope a two-day spike around whether test transactions and webhooks work, producing a throwaway proof-of-concept and a decision record to refine the original estimate.Correct
Why? this is the answer
A proper spike is time-boxed research focused on a single question, with concrete deliverables like a throwaway prototype and decision record that enable a revised estimate. Treating the spike as a path to production-ready code confuses exploration with implementation, while open-ended reading or unstructured exploration lacks the focus needed to actually de-risk the story.
Just read this? Test yourself on what you have been reading.
Read the original → mountaingoatsoftware.com
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles