Hi!
If the team was not able to finish a story and would like to complete it in the next sprint, how it should be done?
move the story to the next sprint and also done tasks will be moved and history information of the sprint is affected.
create a new story using same name and create there only unfinished tasks and in this case the story in the previous sprint is unfinished and it will stay like that but the new sprint information is OK
Could you advise me if there are better options?
This page
Other pages
Account
New
Administration
Comments (2)
Feb 17
Ilkka Lehto says:
At the moment the best way to go about is to create a new story, move the prefer...At the moment the best way to go about is to create a new story, move the preferred tasks under it and then move the newly created story to the upcoming sprint. As far as I know the iteration history is not affected by moving tasks to other iterations; the burndown should be okay. Also the new iteration should be okay.
The only thing you need to be aware of is to have the story points corrected i.e. split among the two stories. This has to be done manually. Say, you have a story of 8 points and you move half of its work to another task. You would decrease 4 points from the original story and add 4 points to the new one.
Apr 26
Anonymous says:
@Anonymous Feb 17, 2010 Having never used iterations before I've been thinking ...@Anonymous Feb 17, 2010
Having never used iterations before I've been thinking about the same problem and I like Ilkka's suggestion. Here's how I think I might reorganize and rename things in such a situation:
If by the end of a sprint I had something like this:
I might do something like this:
Also, in Agilefant 2.0 you could make these stories the children of another:
Add Comment