“A spike is an investment to make the story estimable or schedule-able.”
Purpose | A spike ticket is a preparatory measure that ensures smoother, more efficient progress in project development by allowing the team to proceed with confidence and clear direction. A spike story is created against a ticket that needs more information/investigation so the team can have better understanding to estimate how long the story will take to complete. Agile teams typically have a set amount of time outlined for spikes, which is why spike stories are often referred to as timebox investigation. |
|---|---|
Goal(s) | The goal of a spike story in Agile is not to determine the solution to a story, but rather to determine an estimate for how long the original story will take to complete. Spike stories might require team members to spend time splitting a story into smaller stories if the original user story is too large or complex, or it might require a team member to build an experiment to gather more information for the estimate. Goals:-
|
Benefits | Spike stories in Agile can benefit teams by enabling them to move forward with their Iteration after properly estimating the time needed for completing stories, allowing the team to create more accurate user stories. Spike stories should also reduce waste and increase the team’s understanding of a user story. |
The important questions to ask when treating a Spike is the (What, Who and Why) |
|---|
The Spike has a clearly defined description |
|
A Spike should NOT become a Proof of Concept (POC). Spikes should be small, infrequent, for the purpose of answering some questions about the direction to go in.
So a team may need to run one or more spikes to achieve a Proof of Concept (PoC).
0 Comments