Allow users stories to span more than one sprint
Users stories can be assigned to a sprint, but not tasks. Sometimes one user story has 2 tasks, but only one gets done in the sprint. My only option is to move the entire user story to the next sprint (including the completed task), so I lose my statistics on velocity for work accomplished and velocity for the previous sprint.
The only good workaround is to build a user story for every single task and actually use Epics to group them together. But that just makes a task a pointless extra step.
Jason Hartfield
shared this idea
-
Arthur Lee
commented
Interesting that we're running into the same issue. Newly adopting Scrum, we're still trying to get a good feel for the user stories, hence, there's incomplete work. Moving the user stories to another sprint screws up the stats. I can duplicate them and move them into the next sprint, but these will still show as under development.
I'm not sure what the right solution is, but perhaps a status to say it's incomplete and that it doesn't show up as under development in the backlog?
-
vinceangel3d
commented
Agreed, velocity is not the main issue : in the sprints stats the sprint does just appear with the completed task, the "planified but not completed" stories are not visible anywhere so we don't know how much and what was planified in the previous sprints
-
Amr Abdel-wahab
commented
By definition the velocity shall calculate only the user stories that are completely done done