In our work methodology we estimate the subtasks of stories based on points.
Our stories contains an "initial score" estimate, but when we add tasks
it contains the sum total of points of subtasks, which we call "real effort".
Is there any way the story automatically calculate the score based real effort on subtasks?
And How do I do when I to complete a sub-task, my burndown lower the score? Because now it is only dropping when I conclude the whole story.
Sorry, I should really have said that too!
First, go to admin -> custom fields and find "story points". Edit the configuration for it and make sure it includes your sub-task types (by default, it only lives on stories I think, so you need to check and update this context)
Second, again as an admin, have a look at the project's "screens" - do they include the story point field for create, edit and view on subtasks? If not, then add it
Finally, go to your board as a board admin and look for the estimation tab - select story points in there
Absolutely not. They are completely different fields, because they are measuring different things.
An estimate is a length of time. Story points are a measure of complexity and do not have a simple linear relationship with time. If you are finding yourself thinking things like "well, 1 SP takes an hour", then you're not really using them and you should forget them and use estimates.
https://www.atlassian.com/agile/estimation is worth a quick read on this subject.
I understand, it is that our estimate is really different from the conventional. I say who "we invented" a way to estimate who is presenting a percentage of assertiveness very good. We estimate the tasks at points and not in hours (even these points are based on hours), and therefore would like my sprint had "remaining points" instead of remaining hours.
I'm trying to adapt the Jira to our reality, but it seems that is not possible.
You can do your sprints on "remaining points", you just need to put the points in a numeric field and tell the boards to work off that.
The important bit is that the "estimate" fields are built for handling times and durations, so that's what they expect as input and what they display. Points are simple dimensionless numbers, so you have to use a different type of field to handle them.
The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about 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