Looks like people have been adding/removing things in the sprint, and/or adjusting the remaining time directly. I'd recommend finding the issues that are causing the spikes and working out why they've been doing it
Below is one of the scenarios for the issue in burndown chart;
What we missed in our initial planning was creating of testing subtasks in parent issue but one can argue subtasking anyways hasn’t happened for stories.
Ideally a task should not have estimated effort >1d which helps in measuring progress. Is it so?
Additionally total effort for a parent story should also consider effort for testing the feature which again need to be estimated during planning meeting based on the scope, complexity of feature.
Please let me know your suggestions.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs