The spike story is not completed in multiple sprints which is effecting the sprint velocity? What is the best way to have a spike story and be completed in the same sprint?
Hi @Rachana gupta , welcome to the community!
I recommend not including spike stories in your sprints; they don't have story points and you're right, they will impact your velocity. Instead the Scrum team self-assigns the spike and conducts the research outside of the sprint and uses it to define/estimate stories for following sprints.
Since the spikes don't have story points and are not part of a "potentially shippable product" they should be counted as project work through time tracking and treated like other job duties and administrative work that members of the team do outside of sprints.
Hope this helps,
Edit: I manage non-development issues that don't fit into sprints through Kanban boards in the project using filters on issue types, teams, components, etc. You could do the same for spike stories, that would give you a way to track them easily without impacting your sprints.
Scott - Spikes do have story points. The idea of spikes is to try to accommodate additional work that was not foreseen at the start of the sprint or it is perhaps the result of wrong estimation on a user story. Therefore, if the team deems necessary to add more work, the spike will provide the additional estimation points needed to complete the work in a given sprint.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events