Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

dws (341)

dws
  (email not shown publicly)
http://www.davewsmith.com/

Journal of dws (341)

Friday January 24, 2003
01:05 AM

Project Tracking Tools Suck

[ #10153 ]
The project tracking tools I'm familiar with require that you keep a side tally of progress if you want any sort of useful historical graph. Each time you update the project plan, you take a separate set of notes, type them into a spreadsheet, then make a graph.

Screw that. I'm going to automate it. Unless it's easy to see the trend of progress against estimates (and the history of estimate changes as more is known about the problem), it's too difficult to learn to estimate better.

My last big project took a major hit because of lousy estimates.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Might want to check out http://twiki.org/cgi-bin/view/Plugins/XpTrackerPlugin before going and inventing your own. We have found the wiki way, xp style development & this plugin a decent compromise. --John Cavanaugh
    • I've actually been using an antecedant of XpTrackerPlugin. XpTrackerPlugin looks like a step in the right direction, though it still suffers from the "now" problem. You can see what the project/iteration looks like at any given moment, but to spot trends you need to record a lot of information on the side so that you can make your own graphs.