I'm a former teacher writing articles about software development and everything around it. My ambition is to provide people all around the world with free education and humorous reading.
Pretty well-planned approach you have there. I think it could work quite good. In my opinion it's quite time consuming though. You have to remember that time estimations normally involves many people, so an hour estimation meeting can be many more hours effectively.
I would suggest using agile metrics. In that way you can plan in points and the points will automatically correspond to a certain amount of time based on the actual time it takes to develop. The process is described here.
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.
Pretty well-planned approach you have there. I think it could work quite good. In my opinion it's quite time consuming though. You have to remember that time estimations normally involves many people, so an hour estimation meeting can be many more hours effectively.
I would suggest using agile metrics. In that way you can plan in points and the points will automatically correspond to a certain amount of time based on the actual time it takes to develop. The process is described here.