Re: [taskjuggler] How to best model the current state of a project

From: Chris Schlaeger (cs_at_suse.de)
Date: Mon Apr 04 2005 - 06:46:01 CEST


From: Chris Schlaeger <cs@suse.de>
Date: Sun, 3 Apr 2005 22:46:01 -0600
Message-Id: <200504032246.07544.cs@suse.de>
Subject: Re: [taskjuggler] How to best model the current state of a project


On Tuesday 22 March 2005 03:38, Max Hofer wrote:
> i guess i'm not the only one having this problem and it would be worth to
> spend some subjects on this problem in the documentation.

This topic has come up a few times on the lists. But I agree, the
documentation is pretty bad with regards to project tracking. Probably
because TJ offers quite a variety of ways to do it and everybody needs to
find the way that fits his or her project management style best.

Let me outline them quickly:

1) The lazy way:

Use 'complete' to document what's done. For completed tasks insert the real
start and end dates to avoid floating.

2) The meticulous way:

Use 'booking' to record all done work and schedule the scenario on
'projection' mode.

Those are the methods that we have used, but there are probably other ways to
do it as well. It all depends on how much work you are willing to invest and
how accurate the schedules need to be.

Chris

-- 
KDE 3.3: Conquer your Enterprise Desktop!  See http://www.kde.org!
GPG Key: 1024D/0500838B  A5FE C051 2AFC 9A14 768A  5125 5829 5750 0500 838B




This archive was generated by hypermail 2.1.7 : Mon Apr 04 2005 - 22:34:28 CEST