Before an of that, I would first clarify: what is the purpose of estimations? The great downside IMHO is that they invariably enable management to press for "when is it done" (project, task, story).
If you observe Scrum 101, aside from no mention of stories, it's that plannings are meant to clarify how much the team can do, not when is it done. It might be done at the end of the Sprint. That's that.
If we estimate, we estimate to be able to say how much we can do.
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.
Before an of that, I would first clarify: what is the purpose of estimations? The great downside IMHO is that they invariably enable management to press for "when is it done" (project, task, story).
If you observe Scrum 101, aside from no mention of stories, it's that plannings are meant to clarify how much the team can do, not when is it done. It might be done at the end of the Sprint. That's that.
If we estimate, we estimate to be able to say how much we can do.