What's the ideal order of events for Sprint Planning and starting a sprint?
Currently my team does things in this order, at the end of Sprint 1 (for example):
However, this means that any "carry over" stories from Sprint 1 are shown as "Issues Removed from Sprint", which is not quite correct. They are stories that were incomplete and moved to the next sprint. Doing it this way means that the reports are incorrect (e.g. it shows we completed 100% of what we committed but that's not correct).
What's the alternative? Is it:
This can help us decide how much to add to the sprint from the backlog.
If we do this, then will there be an issue with the reports with having a lot of stories added after we click Start Sprint?
Or is it something like this?
This may avoid a scope issue in the reports, but we don't get a full picture of the sprint before clicking Start Sprint.
What's the best order of events?
We have a couple of hour gap between sprints. Our process looks a bit like:
Sprint 2 is visible in the backlog view before the sprint is started.
Ah, so you can close Sprint 1, do some planning, and then open Sprint 2. That could work.
We would be avoiding step 2 above (splitting and updating estimates) as it's something to avoid. But the other steps could work for us:
1. Close Sprint 1 at start of Sprint Planning, moving stories to either backlog or Sprint 2
2. Add stories to Sprint 2 from backlog
3. Start Sprint 2
This seems like it could address both of our issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it will! That's actually what the software was designed to do, although I don't think it is obvious that that is the case!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to add to this - while a sprint is active you can edit its start date/time to be slightly later in case a few stories were added just after you started the sprint. That will fix your stats e.g. your burndown chart. If the sprint has finished I think it is harder/impossible to fix the start time retrospectively.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.