A seasoned project manager who used to work with me claims that when he gets the programmer's time estimate, it is multiplied by PI and then converted to the next order of magnitude to get the real value. 1 days into 3.14 weeks. He used to suffer because programmers were not good at estimating time. I created a table to translate programmer time estimates to minimize estimation errors. Time estimation is difficult. Each programmer has a realistic estimate interval. An estimate below this interval means that the time overhead (component, test, check code) is underestimated. An estimate exceeding this interval means that the task is too large to be estimated. This interval does not even exist for the primary developer. They ignore the time overhead (component, test, check code), while difficult tasks are not predictable. I want to say that an experienced developer should get things done in 0.5 to 24 hours. More than 24 hours, you need to subdivide. This work should be done in the developer's mind and then combined to 60 hours. But even some experienced developers need to use administrative chunks of time to think. It is also important to understand that programming experience is not equivalent to estimating experience. A developer who is not included in the estimation process will not be good at estimating. Similarly, if the actual time spent is not measured and used for comparison with estimates, then there will be no feedback to learn. Finally, each programmer should have the skills to estimate. To hone this skill, take on each task and decide what you want to do first. Then estimate the time required for the task before you begin. Finally, the actual time spent is measured and compared with the estimate. Also compare what you have actually done with the plan. This way you will improve your understanding of the details of a task as well as your estimation skills. Original link: Programmer time translation cheatsheet-or-why programmers is bad at estimating times
Programmer's time conversion table--Why programmers are not good at estimating time