Sprint-Stories on Product Backlog
Why is an story removed from product backlog when it is allocated to a sprint. We often have to add a new task on the same story in a next sprint which now needs a new story. I would leave it on the backlog and note down the allocation to the sprint. If after the sprint the story is not explicitly closed it would be nice that story can be allocated to the next sprint again. Completing a task should not automatically complete the story for this reason!
Statement from Kunagi Team
When you do Scrum with pen & paper, you would also move a Story card from the product backlog to the sprint backlog.
The product backlog also has some features (like drag-and-drop priorization, filtering and future-projection) which would not work with stories from the current sprint.
Status
Issue is closed.
Comments
Mon, Mar 12, 2012, 13:21 by Witek (SM,T)
The idea of Scrum sprints is to create a working product increment. The stories have to be complete. Why not define a smaller story for basic features which works sand-alone and define another story with the extra functionality for future sprints? That way you can priorize them seperately.
I think having stories which fit into a single sprint is a basic concept in scrum. Otherwise you wouldn't have a potentially shippable product after a sprint, which contradicts the whole idea.
Do you have a concrete example, when one would want a story to be spread over multiple sprints?
Tue, Mar 13, 2012, 00:11 by artjom (PO,T)
I'd like to add that the possibility to pull Stories other than the first one from the Product Backlog to the current Sprint is given only for some technical reasons. In general, the Team should never (ever) pull other Sories than the topmost (incomplete) Story to the Sprint.
The lack of 'incomplete stories' are due to the lack of such a notice in Scrum. Because Kunagi is a pure Scrum tool, we do not support such a thing.
You can, however, assign a common Theme to several Stories and thereby make them connected via the Related Stories field.