About
Exploring Solution Spaces, Keith Ray's blog on Software development and other topics.
Send comments to:
keithray@mac.com
| For Agile Training, eLearning, or Coaching contact: |
| Industrial Logic, Inc. |
| 866-540-8336 (toll free) |
| 510-540-8336 (Berkeley, California) |
| Links |
| xpminifaq |
| Résumé |
| “Adopting XP” Article 2002 (pdf) |
| “ Refactoring” Article 2006 |
| AYE Conference |
| Lucien W. Dupont |
| Elisabeth Hendrickson |
| Johanna Rothman's Managing Product Development |
| Brian Marick's Exploration Through Example |
| Esther Derby's Insights You Can Use |
| Laurent Bossavit's Incipient(thoughts) |
| Dale Emery's Conversations with Dale |
| Martin Fowler's Bliki |
| Creating Passionate Users |
Archives
Subscribe
RSS Exploring Solution Spaces XML
2003.Oct.22 Wed
Burn-Down Charts graph the work left to do, which is reduced by having done work, or by reducing scope. See the "progress" chart here. The project is done when the work left to do reaches zero (or time runs out).
John Brewer describes Burn-Up Charts here and here. The "finish line" -- "total work to be done", is drawn as separate line from the graph of the "work done so far". The project is done when the work done so far reaches up to the finish line. If the finish line is changed by reducing scope, the finish line is moved. The burn-down chart confuses velocity (work done per iteration) with reduction of scope; the burn-up chart keeps those ideas separate.
Here's an ascii art burn-up chart where, about half-way through the project, scope was reduced in order to be able to finish by the ship date:
| FINISH
| ------+ |
| | |
S| +-----+----
C| . |
O| . |S
P| . |H
E| . |I
| . |P
| . |
+-------------+----
TIME