Near the end of a sprint, we find that some items didn't finish, and will need to carry over into the next sprint. It would be convenient if we could use Portfolio to incorporate those items into the plan for the next sprint, perhaps by noticing that if an item in the current sprint has a Remaining Time Estimate that is larger than the number of days left in the sprint, the carry over time should be scheduled into the next sprint, and deducted from the assignee's capacity in that sprint. Is there a way to do this? Are there other workflows for carrying over an item in the currently open sprint into the next sprint?
UPDATE: After working on this more, it's worse than I thought. Let's say we've got two days left in Sprint 10, and I'm trying to plan Sprint 11. There are Stories still open in Sprint 10. If the time estimates are greater than the time left in Sprint 10, Portfolio will not be able to schedule those items any more, and any dependencies of those items in Sprint 11 will not be schedulable. What's the correct workflow here? We don't really use time logging to update the Remaining Time Estimate, but maybe that's the key?
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events