[Background]
I have been assessing the effort for a program change request for the last few days.
[/Background]
I have been colouring little excel boxes for the last few days, giving generous estimates to the program effort. I planned the scheduling, with 3-4 programmers in mind.
HK: "What you doing? We're lucky if we have 1 programmer".
Oh ya...
Me: "Have you seen my updated calculations?"
LT: "Can you give a breakdown for programmer and analyst's efforts?"
Oh ya...
-During the internal meeting
LT: "Does this contain User Acceptance Test?"
Me: "Yup."
LT: "Documentation?"
Me: "Nope." Darn...
This is a good thing, I guess. It highlighted my problem of thinking too much from a programmer's point of view. I broke down the programmer's tasks easily, but neglected the analyst's. Surprisingly, my coding efforts' estimate matched that of an earlier assessment, so that put my mind to ease that I was padding too much time.
A good learning opportunity. Ironically, just as I am leaving, with "lack of growth" as a reason.
No comments:
Post a Comment