I've just recently come across an agile term called SPIKES.
How do you, or how can you, use this in JIRA - specifically within Scrum Boards?
Any info would be useful.
Lot of people do this creating an issue type named Spike. This will help you differentiate spikes from actual stories or tasks.
As quoted in the link, "the purpose of the spike is to gain the knowledge necessary to ...". Hence, a story or task will come out of a Spike and and you can link it back to the Spike using the JIRA issue links (for traceability).
Spikes will be estimated for a specific amount of time and can be added into the boards just like you add stories or tasks.
Everything is an issue in Jira. Like a story, task, spike is also an issue, whereas a spike cannot be treated as a story because it is termed as a spike because of lack of clarity. The agile team should self-assign the responsibility for investing and conversion of it as a story and the time required. The assignee who investigates the spike allocates the time to resolve (Not Story points). Once resolved it should converted as a story.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot