[kplato] Summary of Data Discussion

[Jim Sabatke]

They would be calculated just like standard PERT values.  I think the 
best way to describe it is to put together a diagram of what gets done. 
 I'll see if I can generate something meaningful in the next day or so.

bilbo wrote:

>On 19 Jun 2001, at 16:43, Jim Sabatke wrote:
>
>>Every line should have a confidence (risk) associated with it.  However, 
>>with tasks that have subtasks, the values should be computed, not entered.
>>
>On what basis? Are you going to sum all the confidences for all the 
>subtasks? Just those on the critical path? Or perform some 
>statistical calcualtion like "half the confidence for each subtask on 
>the critical path". I think that we should at least consider having a 
>separate confidence even for a task with subtasks, but it could be 
>optional.
>In many projects I have been involved with the 
>contingency/confidence/risk has been an uncertainty, and thus a 
>plus/minus value, not just possible overrun. This is why I am 
>suggesting a separate value for task - if you add up all the 
>plus/minus values you can get back to zero.
>
>It seems that the terms Contingency, Confidence, Risk and 
>Uncertainty are possibly all referring to the same thing, but maybe 
>not. I see it as either underrun or overrun and not just overrun.
>But then I am only familiar with software projects.
>Yes even these sometimes come in ahead of time!
>
>
>
>regards,
>        Bill
>_______________________________________________
>kplato mailing list
>kplato@master.kde.org
>http://master.kde.org/mailman/listinfo/kplato
>
>

-- 
Jim Sabatke
SuSE 7.1 Linux
Kernel - 2.4.0
http://www.execpc.com/~jsabatke

"People tell me that I'm fading fast, that I can't last the whole night through" Janis Ian