You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
I am new Scrum master and new in Jira also
I am trying to make a good prediction of tasks during a Sprint for my team and I want to use the old sprint to make a realistic prediction.
My question is if the calculation the velocity chart depending on the Story points number why jira doesn't cosider sub-tasks in the equations and put the Story (task type) to equal to 0
Isn't that make the velocity chart not so accurate?
Sub-tasks are not sprint-able items, they are a part of stories (which are). You don't commit to sub-tasks, you commit to doing the stories, and estimates measure commitment vs delivery.
There are a number of ways of doing estimates on sub-tasks, but Jira has taken the simple route and does not support them at all. In off-the-shelf Jira, don't put estimates on sub-tasks (or if you do, educate your users that they're nothing to do with your sprint velocity or progress)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.