here is what we did: Yesterday, first day of our new Sprint 9 (S9), we did our planning meeting between 14:00 and 18:00 and prepared all itmes in the Sprint under the Agile board in Plan mode. We put all estimates of size (Story Points) and Time (Hours/days for each sub-tasks). So far so good.
At the end of our planning meeting, when the team was sure that this was the all content for this sprint (stories, tasks, bugs...) we de'cided to start the sprint. We were proposed with today date and time and a end date and time. Naturally (can't remember what we did last times but I guess differently), this time, we used as start date the date of the day. And for the time, we said...well the Sprint has strated today so we should put as time 08:00 and that is what we did.
Not good... or....? The result is that the all sprint items are in scope change and that there is no guideline displayed or it is flat.
How can I chnage this? what is the problem, should we have put time at something after we did the planning meeitn or?
I'm glad you could figure it out on your own.
You are indeed correct: Jira will see that the Sprint has officially started at 8:00 in the morning and that you've added all stories only in the afternoon, which makes them scope changes.
The solution is indeed to start your sprint after the sprint plannings meeting, which is exactly how Scrum defines it. (Your sprint planning meeting isn't really part of the sprint itself, it might be part of the previous one ofcourse.)
OK, may be this was a very stupid question ;-) It seems obvious at first that as we start the sprint on a day at 08:00 we would reflect this in the Start sprint date and time as :à!:00 but the true is that:
If you do a sprintplanning and put the idetms in the sprint and then set the strat sprint time at say 08:00 morning before you do the planning meeting...well then all the items are considere'd being added after the time the sprint strated so ...scope change. Both situation are now obvious to me but I now better understand how jira treat the items in regards of the strat sprint time ;-)
What I did to solve this: rename the sprint into say "Sprint 9b", create a new sprint "Sprint 9" and move all items from Srpint 9b into 9. Start Sprint 9 at today's date and time after this operation. Now a clean burdown and no scope chnage (yet). ONly ewe have lost one day (yesterday in the plan of the sprint but OK...). Hope this help others....
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
👋Community members! Downtime happens. And great incident response takes a village. Teams like Support, Dev, SRE, Ops, IT, and Marketing have to come together to resolve the problem while keep...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs