Also, for a few months, we decomposed features very deeply and tried to estimate those tasks to an hour. Then we time-tracked it and watched the results. By doing this we learned to estimate better and it taught us to see things for what they really are.
Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
So far, I've learned I'm freakin' terrible at estimating things! I need to be more focused, I'll be jumping between multiple tasks and next thing you know an hour has passed...and then another...whoops.
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 did exactly the same!
Also, for a few months, we decomposed features very deeply and tried to estimate those tasks to an hour. Then we time-tracked it and watched the results. By doing this we learned to estimate better and it taught us to see things for what they really are.
So far, I've learned I'm freakin' terrible at estimating things! I need to be more focused, I'll be jumping between multiple tasks and next thing you know an hour has passed...and then another...whoops.