Generally, I've tended not to use story level estimates in Jira, focussing on subtasks and estimates based on real time.
However, now I want to do some sprint velocity tracking/prediction and if possible id like to do this in Jira either (using real-time or story points). When I tried this, the burndown added the story estimate to the task estimates! So then i thought maybe I could prevent this by tracking the stories in points and the tasks in time... but I dont think Jira allows this.
To summarise, id like:
Burndown should use task estimates/remaining.
Other reports should use story points/time.
Or any other suggestions of how to work around this issue!
Many thanks,
David
Thanks for taking the time to reply Nic,
I think i've got it working how I want now.
I set the Estimation Statistic to 'Story Points', which allowed me to add point estimates to Stories but it still lets me track sub tasks with time. :D
So now my burndowns are based on time remaining on sub tasks.
AND hopefully, ill be able to review sprint velocity as we proceed through sprints.
I'll consider your suggestion at the end too. Im not trying to equate points and time, so thats ok and ill look into swapping time and points around... i think thats quite easy to do in Jira... (famous last words)
The usual way to do this is at https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html
But do not equate story points with estimates - they are not the same thing, there's no equivalence between them. And normally, you would do it the other way around - burn-down on Story points, but report on time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.