We want to be able to do a better job tracking my team's velocity per sprint, but our sprints often include stories tied to epics that span across multiple sprints. What's the easiest way to make sure that burndown charts reflect only work that is tied to specific sprints?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot