> If you've committed to a feature or fixing a bug and it takes longer or shorter does it matter? It's not, but it's still nice to get a rough estimate, isn't

> If you've committed to a feature or fixing a bug and it takes longer or shorter does it matter? It's not, but it's still nice to get a rough estimate, isn't it? It's also useful when you need to prioritize things, because you often cannot fix all bugs or implement every nice to have feature. It can also be interesting to find out why a feature estimated to say 3 points took a whole sprint to be implemented: is there tech debt? was it badly specified? maybe even the dev would have needed help (pair programming, formation, etc.) but didn't ask for it? It's useful for self improvement