Hacker News new | ask | show | jobs
by zimbatm 2250 days ago
Same sentiment here. It would actually be useful if the "time tracking" supported sizing and estimations but right now it's completely focused on precise timing which makes this counter-productive.
1 comments

Just making sure that you are aware that GitLab supports sizing and estimations via weights https://docs.gitlab.com/ee/user/project/issues/issue_weight....
I still think it would be useful to specify an 95th percentile error value for time estimates. I told my PM that the estimate in jira has an error range once and she flipped. Having that idea backed up by the tools we use would really help planning be more realistic.
That is a great suggestion. GitLab has burn-down charts https://docs.gitlab.com/ee/user/project/milestones/burndown_... that show that progress isn't linear.

What is small change we can make to stress planning has error bands without affecting the usability?