How to estimate the duration of unforeseen tasks?

Question

I would like to know if anyone knows the methodology or something that can estimate the duration of unforeseen tasks.

Many times I need to leave some task and visit many others, I read about switching contexts , but my problem is that I cannot, because I do not know how to estimate the length of an unexpected task. Maybe?

Answer 1

I try to give estimates in hours of work, so if I get distracted by a task, I can indicate what I did and how much longer.

: http://www.joelonsoftware.com/articles/fog0000000245.html

, , , .

Answer 2

- .

, ( ) , , / . , , .., .

: , 10 , -:

time     note
10m
10m
1.5h     got pulled away to fix a production bug
10m
45m      server offline due to upgrade
10m
10m
4h       entire staff evacuated due to bomb scare
10m
10m

, 10 . , , , 45 . 5 , 45 .

, - 10 , 15 , FTP, rsync .. , .

Answer 3

, .

, , "120 ", "4 " ( "" ).

, , , .

Answer 4

, , , , .

Answer 5

-, . , .

, . .

Answer 6

If you have unforeseen tasks, then you can find out about the time during which you work on them and add as a buffer to determine the end date (not working for the project, because unforeseen tasks sound as if they were connected. other projects). There have been studies showing the mean. a programmer has 60% performance on a designated project, so buffering 30% -40% may seem high (or it may not be), but it will be a good starting point.