Good post, I hold perhaps a contrarian view on this and that is that estimation is a waste of time. Why? because it's hard and in 90% of the cases people get it wrong.
What is the alternative? No estimation! You have your team create tasks/issues that take roughly 1 day (8 hours) (or whatever metric you prefer) to complete. Over time you'll see the burn rate of your team and you'll get a productivity average your team is able to produce during a week's time or even sprints of several weeks if you want to use something like Scrum.
Depending on the type of task, and the team maturity you'll end up with a certain level of accuracy. This is true regardless of actually estimating your tasks or you ballpark it with this method.
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.
Good post, I hold perhaps a contrarian view on this and that is that estimation is a waste of time. Why? because it's hard and in 90% of the cases people get it wrong.
What is the alternative? No estimation! You have your team create tasks/issues that take roughly 1 day (8 hours) (or whatever metric you prefer) to complete. Over time you'll see the burn rate of your team and you'll get a productivity average your team is able to produce during a week's time or even sprints of several weeks if you want to use something like Scrum.
Depending on the type of task, and the team maturity you'll end up with a certain level of accuracy. This is true regardless of actually estimating your tasks or you ballpark it with this method.