From: Matthias Welwarsky (welwarsky_at_archos.com)
Date: Tue Oct 25 2005 - 10:30:13 CEST
From: Matthias Welwarsky <welwarsky@archos.com> Message-ID: <17d3.435ded15@www.taskjuggler.org> Date: Tue, 25 Oct 2005 10:30:13 +0200 (CEST) Subject: [taskjuggler] Re: missing: highlight critical path in gantt chart
Yes, I know about the PERT generator. I tried it but it's not sufficient:
- it supports no filtering. It always draws the complete tree which becomes extremely complex for large projects
- it does not know about "rolluptask". Sometimes you need a way to hide complexity that is not relevant
- the chart is ugly :d
- it's not integrated
I start planning in a top down manner. First I identify the tasks on a high level, then I drill down to subtasks to identify the effort, but the first thing is always to become clear about the dependencies: You need to find parallelizable tasks in order to assign resources properly. Currently I'm using OOo-Draw for that. Ideally (for me), taskjuggler would display a dependency graph even independently from the scheduling, without taking effort and resources into account, only the explicit dependencies.
About visualizing the critical path(s): If you have two critical paths, well, then you have two critical paths. It does not make much sense to speculate about the degree of criticalness if they both match the criterion: if something goes wrong along this path, the final milestone will slip. Just draw both in a special color(?) and allow a report to display _just_ these paths and allocated resources.
-- To unsubscribe, email the address listed in the List-Unsubscribe header For additional commands, email: taskjuggler-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Oct 25 2005 - 10:30:21 CEST