« Parking Lot Diagrams Revisited – Using Area to Show Effort | Main | Six Project Trends Every PM Should be Aware Of »

December 29, 2009


In one of the volumes of "Quality Software Management", Gerald Weinberg suggests using a "task tracking diagram" (not the exact name). Draw an empty rectangle for each story/task with its left edge representing the day the task is supposed to start, and the right edge representing the day it is supposed to end. Fill it up with green on the days it is actually worked on, or leave blank to indicate its not being worked on. Extend the rectangle with red when the task is still being worked on after the day it was supposed to be finished.

Like many Agilists today, he suggests using low-tech tools like paper and markers and posting this on a wall.

I also think Weinberg's task tracking diagrams were meant for iterations or short projects, not for the whole project.

Have you tried keeping the box width constant, so the eye compares the height of the box rather than trying to compare areas?

Hi Ckeithray,

Thanks for the suggestion. from a quick Google it looks like volume three, I will pick up a copy and take a closer look. Many thanks for the suggestion.


Hi Bill,

Thanks for the suggestion, I tried the opposite, keeping the box height constant, so the eye compares the box length, it worked OK, but looked a lot like a Gantt chart again, - these were the examples at the end of my original post. While bar graphs horizontally or vertically should not really make a difference, perhaps the vertical orientation is enough to fool us into thinking we are not viewing Gantt charts so therefore keep engaged. I will have a play and see how they look.


The comments to this entry are closed.

AddThis Social Bookmark Button

Your email address:

Powered by FeedBlitz


  • Google Analytics
Blog powered by Typepad
Member since 07/2006

November 2016

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30