I wonder if you can help/advise with the following.
- We have stories with sub tasks in a given sprint and some of them need to be carried over to the next sprint simply because they are not fully completed.
- We only use time estimation and each story has allocated Original estimate and the team is logging the actual work time too.
When you carry over stories for lets say 2 sprints and eventually close them I cannot see in any report how much time was actually spent on that story in each sprint.
It also affects the overall time estimates. Lets say I have a story with 3 subtasks estimated for 16 hours in total. The story is not fully completed in the sprint and I have to move it to the next one, although we have logged 12 hours of work and only 4 is remaining.
Unfortunately it will still calculate the sprint effort with the original 16 hours which is not true because I only need 4 hours to finish it and it means that resource who is working on it could do more stories.
I hope this make sense :-) I would appreciate any help or advise.
I have the same question. Did you ever get an answer to your question in regards the handling of tasks that get carried over to the next sprint? I was thinking that any carried over tasks should be re-estimated by updating the "Original Estimate" field with the "Remaining Estimate" value from the previous sprint.
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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