Thanks for the once again for the advice. It has already proved useful.
Kind regards
James
On 6/19/07, Hans Wichman <[EMAIL PROTECTED]> wrote:
Hi,
i think i'd recommend 'code complete', 'the mythical manmonth', 'software
project survival guide', but that's just based on personal preference,
Hi,
i think i'd recommend 'code complete', 'the mythical manmonth', 'software
project survival guide', but that's just based on personal preference,
picking up some books about agile development methodologies could be a good
idea too. To be honest, I know the ideas in there, and read papers about
Thanks for taking the time to respond Hans. I actually record how long
things take already. I think you are right though perhaps the hard part is
having the arguments to hand to support why it will take a while.
Which books would you recommend?
Where I work there is another employee who is willi
Hi,
well one advice is to start recording your current measures and check
afterwards how close you were.
Record things you forget that made your estimates go wrong, records the
factor realhours vs estimate.
Assume that when you think you know everything, you only know about 40% of
whats going to
I'm looking to improve the accuracy of the estimations of time required
which I give to my project managers. Does anyone have any good advice?
Please note that I am far from a newbie as I have been programming
actionScript ever since it first came out (with that nasty slash syntax).
This is one a
5 matches
Mail list logo
