Over on Agile Kiwi, John has posted a new article talking about a simple graph he’s using to track progress on a few projects. The suggested approach is a lot like the Scrum methodology Burn Down Chart but with additional information that relates to budget spend.

I’m going to suggest that we include a graph like this in a major project that is just ramping up for me - should make the weekly project status reports a lot more informative.

One small point, though … I think John is being far too nice when he talks about Microsoft Project. In my view, a typical Gantt Chart has only one real redeeming feature: You can use the back for notepaper.

Why am I so negative about Gantt charts? Mostly because they have little or no relation to reality - and because some Project Managers mistake “Updating the Gantt Chart” for “Managing the Project.”. But, the details of that can wait for another day - another post.


blog comments powered by Disqus
Next Post
Code Margins  23 Aug 2005
Prior Post
NicheSQL Tool goes Public  30 Jul 2005
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
August 2005