The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Why my sprint have to start after I added my stories to record the Commitment in velocity chart?

Why my sprint have to start after I added my stories to record the Commitment in velocity chart?

Ricardo Hernández Gómez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 2, 2019

I understand that Sprint planning meeting is part of an Sprint, so it suppose that the sprints starts when the Sprint planning meeting is being done. If you do so, setting the start of the sprint to the date and hour when the sprint planning meeting starts, makes your commitment zero when you end the sprint due jira thinks you added issues after th start of the sprint. It shouldn't be like that.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Ste Wright
Community Champion
November 3, 2019

Hi @Ricardo Hernández Gómez

The Velocity Chart (like a number of the reports) work best when sprints are started at the day/time you press the button.

This is because it takes into account what happened prior to the time you start the sprint otherwise - which can discount stories added or estimates. 

In reality, the sprint does begin once planning starts - is there a concern with starting it then rather than earlier?

Ste