Loading Profile...
How to properly remove a requirement/user story/task from a running sprint?
How to properly remove a requirement/user story/task from a running sprint?
Half way through the sprint we realized that we won't be able to achieve the sprint goal, so the product owner decided, that one of the bigger features will be taken out of the running sprint.
This is how agilo renders the burndown chart, when we remove the sprint property value from the user story.
Before the user story has been taken out:
After the story has been taken out:
The problem I see with this is: The interpretation of the burndown chart now doesn't reflect the fact, that a user story was taken out from the sprint. In fact, now it looks like the task was never there in the first place. What we want to see there is a sharp vertical decline that would correctly reflect the removal of the user story.
Is there another option of removing user stories? Are we doing something wrong?
Thanks for the answer, and thanks for making Agilo. It's helping us immensely.
Half way through the sprint we realized that we won't be able to achieve the sprint goal, so the product owner decided, that one of the bigger features will be taken out of the running sprint.
This is how agilo renders the burndown chart, when we remove the sprint property value from the user story.
Before the user story has been taken out:
After the story has been taken out:
The problem I see with this is: The interpretation of the burndown chart now doesn't reflect the fact, that a user story was taken out from the sprint. In fact, now it looks like the task was never there in the first place. What we want to see there is a sharp vertical decline that would correctly reflect the removal of the user story.
Is there another option of removing user stories? Are we doing something wrong?
Thanks for the answer, and thanks for making Agilo. It's helping us immensely.
I’m confused
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Clearly the burndown does not look right in your situation :-/
Unfortunately Agilo does not track moved stories yet when it comes to the burndown chart so you did not do anything wrong, it's just our fault. In the true Agile way we tried to build something usable for the majority of the cases (and we removing stories from the sprint does not happen all the time) and focus on problems like yours afterwards.
We're aware of the problem and will think about a good solution (which has many different aspects because a 100% solution would include also historic capacity).
So I'm sorry to say that we can't help you right now but we fix this in the future. If you like to contribute some code, you're more than welcome :-)
fs
1 person says
this answers the question
1 Comment Add a comment
This answers the question
-
Thanks for your reply. I'm really glad you guys opened your Agilo (https://dev.agile42.com/) for the public to see, and I hope to find this feature in the backlog soon ;)
Cheers -
Inappropriate?We have run into the same issue. We see it most often at the end of the sprint if there was work that didn't get done or got change into a future spike. What we do to solve it is leave the ticket in that sprint and create a new ticket for the continuing work. We put a note in the new ticket that links back to the old ticket for tracibility. This isn't perfect and does involve some manual leg work, but it keeps the sprints looking accurate.
1 person says
this answers the question
2 Comments Add a comment
This answers the question
-
I guess that's a workaround that could possibly work. One way Agilo could take care of this, is to offer the user an action to "remove" a user story / task from a sprint, but instead of just removing it, it would create a 'shadow ticket' in its place, status of which would be closed, and it's resolution: removed. The shadow ticket would of course include proper links to the original story.
-
I really like this idea, and I entered it as an idea in our bugtracker at https://dev.agile42.com/ticket/799
EMPLOYEE
