Dear all,
I am a bit confuse on the Estimate field on jira issue.
I have seen where in the field you can enter :
In some other situation I have seen the field where you can enter only number ( story points)
Actually my customer never well estimate an issue so we have set up a custom field where he can enter S (small), B (big), L( very long) instead of using native Estimate
Now my questions are as below :
In order to get a good clear view about the issues, especially in a sprint ( are we on target or not ), what is the proper way to configure the estimate field ? Should we better use story point or not , how good correlation is bases on estimate type field
regards
Typically, the way teams use story points and hours is like this :
An alternative is to not use story points, but still use a time estimate on sub-tasks. If a parent doesn't have any sub-tasks, then a time estimate is added directly to the parent.
There are probably other ways as well, you need to find out what works best for you.
If your customer only works in S, M, L, you could come up with a meaning for them e.g.
S = 3 story points
M = 5 story points
L = 8 story points
XL = 13 story points
or even
S = 2 hours
M = half day
L = 1 day
Thanks for your reply.
The key point is that I need to define good practice rule in order to define estimation in order that in dashboard, or using gant Chart, the claculation is working correclty.
For instance if customer is usin S, M L and in order to map it to 2, 5, 10 story point, what is teh proper way to populate automatically the default native field accordingly in order that it is still correct for calculation on chart ?
Thanks for help
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.