One of my developers had a 'place holder' task within a story worth 80 hrs. He then added a bunch of 'real' tasks adding up to 80 hours. He then deleted the orginal task of 80 hours. The scope reduction did not reflect on Burn Down. Is this normal behavior on a deleted task? How can I reduce my Sprint scope by 80 Hrs to make the burndown accurate?
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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