The problem is because you are either estimating your subtasks after start of sprint OR you are adding/creating the sub-tasks after start of sprint.
At the start of sprint, the scope should be clear toeveryone, all stories should be ideally estimated, sub-tasks created and estimated and added to sprint.
These tasks have to be done before the start of sprint and not after.
If you follow these guidelines, burndown will be more representative.
But this is precisely the point!
We can't estimate a subtask before the start of a sprint! Because of that we're obliged to estimates tasks after the start, and the burndown is completely screwed...
The question is how do we estimate a substask before the start of the sprint?
I have the same problem and I can't find an answer.
If you have the solution please tell us how to do, thanks a lot
The problem is that Jira doesn't work following Agile principle: A team isn't supposed to work on a user story outside a sprint. Then, when the sprint is started, the developer can split up his US in small sub-tasks and only at this moment otherwise it should exist a time between each sprint to review every US to look into them and create all sub-tasks which is ante Scrum !!!
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot