I just set-up my sprint perfectly... correct versions, epics, User Stories, Tasks, estimates, sub-tasks (where applicable and with estimates) and then hit start sprint.
I had estimated, based on resource planning, to need 11 work days to complete, including Retrospective... however, instead of Sept 3rd, I saw Sept 7th.
Is JIRA therefore auto-calculating sprint lengths based on the estimates??
[Please note, I did not select anything from the drop-down menus myself. This is the screen I was presented once it popped up]
Estimations don't affect to Sprint lenghts. Users have to configure it.
You have to use "Start date-End date" to make the Sprint planning.
Estimation depends on each user. 6 SP can be 6 days for you...6 hours for me...
Regards!
Thanks @Jorge_de_Carlos! Fast reaction :oD
So pleased to hear user have to configure, that's logical. Similar question slightly varied: Any idea why the dates are filled in automatically?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unless something has changed the duration is defaulted to previous sprint duration. I don't know what the default is for the "first sprint" but I expect it is just a default. It would be interesting to see if the sprint that is about to start is different than previous.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's an interesting point @Jack Brickey. Got another project about to start a new Sprint. I'll keep an eye out on that one. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suppose everything much simpler. Jira just trying to round total estimated time of the Sprint to the integer number of weeks. You have 11 days - 5 work days a week, so it will be 2 weeks and one day. Jira rounds it to 3 weeks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Gregor Kasmann_Actonic. Appreciated the rapid response. That's an interesting point you make there. Is that a known function in Jira; ever had it confirmed by someone from Atlassian?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.