What is a spike issue in Jira?

What is a spike issue?

A spike is a product development method originating from Extreme Programming that uses the simplest possible program to explore potential solutions. It is used to determine how much work will be required to solve or work around a software issue.

What is the point of a spike?

Their purpose is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate. Like other stories, spikes are estimated and then demonstrated at the end of the Iteration.

What is the purpose of creating a spike story?

Spikes are an invention of Extreme Programming (XP), are a special type of user story that is used to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate.

What does spike mean in Scrum?

A Spike is created when a user story or task cannot be estimated well enough until the team has done further research or investigation. The result of a spike is an estimate for the original user story so that the sprint can move forward.

Should you size a spike?

Spikes are just special user stories. They are accepted by the product owner and are put in the backlog and sized to fit into an iteration just like any other story.

THIS IS FUNNING:  Can I export a Jira queue to excel?

Should spikes be Timeboxed?

Timeboxing Spikes

Each of our spikes should be timeboxed, in story points, and that timebox should contribute to the team’s velocity for that sprint. … In this way, a spike contributes business value in the same way that the first iteration of a particular UX design contributes business value…