Re: Re[2]: Feature suggestion: 2 times for "duration of task": optimistic and pessimistic

tor 2002-08-22 klockan 23.45 skrev Michele Ravani:
> On 22 Aug 2002 13:49:36 +0200 Mikael Hallendal <[email protected]> wrote:

> Well only partially. Think at a situation were your plan changes because of
> additional requirements and similar things. This wouldn't be captured by a
> baseline, but would by a versioning system.
> On the other hand, baselines could be pushed further. Instead of having a
> snapshot (i.e. the last saved baseline) a history could be stored, e.g.
> everytime the project is saved (ok, that's versioning) and one could start
> producing rather interesting graphs showing the progress vs plan over time
> of the project, of a group of tasks, etc. 

Ok, I've added an issue in the issue tracker so that we don't forget to
look at this when we are about to implement baselines:

http://bugzilla.codefactory.se/show_bug.cgi?id=257

Please add yourself to the CC-line if you are interested in tracking it
(you need an account in the bugzilla first).

> Yes, but your are storing (and entering) three values instead of two.
> If I say (and enter in the system as a parameter) that from my experience
> Joe Coder is within 20% of his estimates most of the times, I can use this
> information to get the likelyhood that a task will be delivered in time.
> If the work of Joe Coder depends on other tasks, this can be factored into
> the computation the same way. Worst case scenarios could be computed.
> One could even run MonteCarlo models on such a thing :o)

From what I understand those three values are needed for the PERT. I
guess they could be entered as you suggest. Perhaps in some way make it
optional which way you'd like to input it?
 
Regards,
  Mikael Hallendal

-- 
Mikael Hallendal                [email protected]
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918