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
Appropriate Expertise  26 Feb 2006
Prior Post
A New Home  14 Jul 2005
Related Posts
SharpDox Tips  02 Jan 2016
Effective IO for the Modern Developer  21 Jun 2015
Blink Estimation  11 Aug 2013
Notifying Windows Explorer about files in use  01 Apr 2013
Code Analysis vs Code Contracts  16 Feb 2013
Comspec corruption - Solved  25 Jul 2012
Comspec corruption  10 Jul 2012
Configuration of Log4Net through code  14 Sep 2011
What to ask users ...  15 Aug 2011
Semantic Versioning  28 Jul 2011
More tips posts »
Related Pages
August 2005 archive