Iteration End - What to do with tasks/backlog items not completed?
Ralf Rottmann
Today we reached the end of an Iteration. (Actually, our first one since we moved to Scrum/V1 J). There are quite some tasks which could not be completed and have pending work to be done. How do we deal correctly with these? Do we move them to the next iteration? What will happen with the Backlog Items that clearly have to stay with both iterations than? We don’t want to do anything which could potentially break reporting. We also do not want to duplicate content where we can avoid.
Your advice is greatly appreciated?
Ralf
Jones, Ken
We use the Close Iteration tab off the Review screen. One of the options for each story is to Split Story. Split story allows you to take credit for work completed n the current sprint and move work not done to the next sprint.
When we use this, we split the story points for the original story between the two sprints.
It is preferred to complete all stories in the current sprint, but as you are learning to work in sprints this is an effective approach.
Ken
Ralf Rottmann
Thanks for your quick reply and sorry for asking for more details. We've really put a lot of efforts into defining all the BIs and Tasks and I don't want to do anything wrong. So avoiding risk is key with my next clicks in VersionOne.
I've navigated to the Review > Close Sprint Tab. I've created a new Iteration. Is the next step as simple as dragging all items from the Remaining Backlog Items and Defects list to the newly created Iteration?
Thanks again,
Ralf
Jones, Ken
It's not a drop and drag. In the Review -> Close Sprint screen where it has the grid for Remaining Stories and Defects (we use Scrum terminology, yours may be slightly different), there's a row for each story not yet Closed. On the far right, it shows Close Story with a downward arrow. Click the down arrow and you get a menu of other options. Choose Split, it will open up another dialog window for that story. At the top of that window (in the maroon colored title bar) there's a link to the right for Split. You have to click that to take story with tasks/tests that weren't finished in the current sprint (Original Story) and replicate them below as the New Story. As I said earlier, we normally split the original story points appropriately depending on how much was accomplished.
Ken
Ken Jones
Sr. Manager, Suite Integration and Technology Engineering
2 Omni Way
Chelmsford, MA 01824
978-947-4558
ken....@kronos.com
Maggie Bullington
Ken is correct about the way to use Split properly. If you have stories that have not been worked on at all, you can just drag them up to the box representing the next sprint. But if you have worked on them, use the split action first, then close the half of the story remaining in the sprint you are trying to close out.
-Maggie