>
> On Feb 17, 2010, at 1:37 PM, Tamas Rudnai wrote:
>
> Hmm, interesting input here, Vitaliy. Actually in one project
> management course the presenter suggested similar thing -- he said an
> excel table is just as fine.
>
> Anyway, I am really interested to see how would you recognise risks,
> like you have a dead line, and the hours needed to finish that project
> / tasks are to much (aka you obviously cannot finish it on time). And
> how would you synchronise many tasks together that has dependency on
> this and that tasks? Or what happens if a programmer is sick so one of
> the major resource is out and that would risk a task to finish in
> time, that will also fail many other tasks that are depending on that?
> Or to see what happens if you assign this or that guy to work on
> another task that is on trouble, how would it affect the overall
> project, would it help or would it be worse? Overall I just thought a
> computerised system might help on these early recognition of risks,
> but I really do not have an idea at this stage?
>
> Thanks,
> Tamas

Read some GoldRatt.
Perhaps "Critical Chain"
http://en.wikipedia.org/wiki/Critical_Chain_Project_Management
Gus

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist