As a SM, I am trying to start a new (first) sprint for a development team. I see Tasks, Technical and Exploratory spikes in the backlog.
What DEV want to
1. Does not want to create stories in the sprint.
2. but want to estimate and track all issue types by story points (an available field only to story)
Any advice on this, how should I handle the situation?
3. Is there any effect on velocity using different issue types such as task, Technical and Exploratory spikes? I believe it does not - please confirm
Hi @Su , welcome to the community!
You can edit the Story Points field context so that it applies to other issue types. By default, there are only two or three issue types that the story points field is scoped to.
When the stories/other tasks are created, they will go straight to the backlog, this is usually done by a Product Owner/Business Analyst/Project Manager or a similar role. Once the issues have been created, the developers can then have an estimation session to go through all of these issues on the backlog, refine them and then can provide an estimate for them.
For your 3rd and final question - velocity simply compares the number of story points committed at the beginning of the sprint to the number of story points completed within the Sprint. So regardless of what issue types you have points against, this is how the velocity chart will be calculated.
Hope this helps!
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
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