The "cover your ass" strategy involves tracking 3 things: * Estimation time to complete each project task (hopefully estimated by the person who is going to do

The "cover your ass" strategy involves tracking 3 things: * Estimation time to complete each project task (hopefully estimated by the person who is going to do the job. Then add 20%) * Status of each project task (from 0% to 100%) * Time devoted to "support interruptions" each week. Doesn't need to be super detailed - something like "week 4: 5 man-days on support tickets x1, y4 and z6" That way at the very least you are equipped to answer the inevitable questions "why isn't feature C done?". The answer would be something like "we still need around 2 more weeks of full-time work in order to complete that task, but given the current rate of interruptions we will realistically have it ready in one month".