creating a Story and seveal technical tasks under it creates a dillema or at least I do not know how to handle the scenario when not all of the technical tasks are resolved by the end of the sprint in the Rapid Board.
Ending the sprint moves the Story and all subtasks to the new sprint!
How do you handle such scenario? Is it not possible that resolved subtasks are left behind and only Story and unresolved tasks are moved forward to the new sprint?
It's a little unusual to have a story with tasks where some of those tasks get completed and others don't. In that case many people would say that the story therefore isn't complete and it should go back to the backlog (with it's tasks that are still marked as complete).
I can see your point that in some circumstances a task or two might not make it, there are two ways I think you could deal with this:
In the future we plan on implementing a 'Split story' function in to GreenHopper. This would allow you to split the story and keep the done subtasks as children of the existing story but have the not done subtasks attached to the new story (so they can go in to a future sprint).
I think this behaviour is correct, because the tasks belong to the story and if the story is moved to another sprint, all the task are moving with this story, because they all are parts of the story.
If they should stay in the closed sprint, they would need a new story they can belong to. This has to be handled manually.
If one goes into the detail planning, that is specifying all the technical tasks, one can easely create a task or two which for whichever reson do not get completed by the end of the sprint.
So the alternative is not to create subtasks (technical tasks) and only stories, which makes the process of removing them manually from the sprint with the menu action "Remove from sprint" or automatically to the new sprint a no-brainer in greenhopper rapid board.
You have to be really sure to end all the subtasks within the sprint to use them! That somehow defeats the idea of estimating work if there is no tool support to easely manage such cases. Don't you think?
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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