Re: first time managing a project
- From: hmurray@xxxxxxxxxxxxxxx (Hal Murray)
- Date: Tue, 29 Nov 2005 23:36:47 -0600
>No matter what, if you track the actual schedule against your original
>estimate you can at least have an estimate of when you'll actually be
>done. Not only can you use this estimate to motivate the troops, but
>you can use it to warn your boss that things aren't going as fast as
>expected.
How well does that work?
I'd expect it would give horrible results in two common cases.
(Maybe just looking at the same thing two different ways.)
One is the one-last-bug problem. All the module tests go great
but then it doesn't work when you put it together.
The other is that halfway through a project, the nature of the
work changes. You shift from writing code to integrating/checking.
Knowledge of how well things worked during the first mode doesn't
tell you anything about how good your estimates for the second mode
will be.
--
The suespammers.org mail server is located in California. So are all my
other mailboxes. Please do not send unsolicited bulk e-mail or unsolicited
commercial e-mail to my suespammers.org address or any of my other addresses.
These are my opinions, not necessarily my employer's. I hate spam.
.
- Follow-Ups:
- Re: first time managing a project
- From: PeteS
- Re: first time managing a project
- From: amyler
- Re: first time managing a project
- References:
- first time managing a project
- From: gretzteam
- Re: first time managing a project
- From: Tim Wescott
- first time managing a project
- Prev by Date: Re: first time managing a project
- Next by Date: Re: Stupid reset question
- Previous by thread: Re: first time managing a project
- Next by thread: Re: first time managing a project
- Index(es):
Relevant Pages
|
