I think the key to stress-free estimation is, as a team, committing to a lower number of points/issues/stories/whatever per sprint/iteration/week. Less points committed to at the onset means more wiggle room in the event that the code you "estimated" at 2 is actually 5. And thus, I'd argue that it allows your estimations to actually BE estimations.
The fact that we even have the phrase "accurate estimation" and "precise estimation" and so on should tell us that we're fundamentally over-thinking it. As a mental exercise, try this:
Look at a random object somewhere in the room you're in now, and quickly estimate how far the object is from you. Just go with the first reasonable number that comes to mind without thinking too much about it.
I think if an "estimation" goes into any more depth than that then it's not estimating, it's grooming.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the key to stress-free estimation is, as a team, committing to a lower number of points/issues/stories/whatever per sprint/iteration/week. Less points committed to at the onset means more wiggle room in the event that the code you "estimated" at 2 is actually 5. And thus, I'd argue that it allows your estimations to actually BE estimations.
The fact that we even have the phrase "accurate estimation" and "precise estimation" and so on should tell us that we're fundamentally over-thinking it. As a mental exercise, try this:
Look at a random object somewhere in the room you're in now, and quickly estimate how far the object is from you. Just go with the first reasonable number that comes to mind without thinking too much about it.
I think if an "estimation" goes into any more depth than that then it's not estimating, it's grooming.