This could just be the programming side of me that doesn't want to worry about estimates coming out too strongly, but it seems odd that managers want everything to be estimated ahead of time. The current item in question is knowledge transition. I'm leaving the company I'm currently working at and need to sit down with the developer taking my place. We've come up with a number of things to review and we've got about 10 days to do it in. So I'm trying to figure out what the estimate would be giving my manager.
I suspect the concern is that the project needs to continue moving forward even while we're working on this knowledge transfer. So they want to account for this time in the main project. So that we have an "accurate" end date for the project. My issue that I have not faith in any accuracy of my estimate. The project has been in the works for three years and during that time we've been working in fairly isolated roles. So while I'm really not certain what it's going to take for my replacement to pick up on the stuff. I almost forgot the other catch is that my replacement is part-time.
Hrm - I just don't see how beneficial having the estimate is in the grand scheme of the project.
