I had a manager institute PERT estimations for every task/sticky, which was interesting but not necessarily worth it.
In the end, the work takes the time it takes, and nobody knows how long that will be ahead of time. Fiddling around with estimates helps with ranking but not prediction.
If the work takes the time it takes and nobody knows how long with that, why not track and iterate on the predictions versus outcomes creating experience and data that would enable prediction and prediction refinement?
Over time the estimates should be trending closer to outcome, as the process improves in breaking down and specifying the details that impact prediction & work, and the statistical gap from previous estimates gets baked into future estimates. The process, capabilities, ability to identify diverging factors, and correction of initial estimates should all be maturing concurrently.
The entire point of using fuzzy numbers is to enable fuzzy yet usable predictions. Similar work in a similar situation, armed with specific statistics and outcome, should be highly predictable at the team and individual level over time.
Sure, that’s the theory behind middle management. Unfortunately the bosses who run the places keep saying yes to things that have never been done before and for which few priors exist.
Alternately, it captures a bit of so many things (tech-debt in codebase, mental health of team, task risks) that it's best to avoid trying to link it to any one thing.
The past X weeks of point-estimates is what you use to forecast which things fit in the next Y weeks, and you can't have both stability and forecast accuracy. Any attempt to permanently "peg" a point to a certain number of man-hours is going to interfere with that accuracy.
In the end, the work takes the time it takes, and nobody knows how long that will be ahead of time. Fiddling around with estimates helps with ranking but not prediction.