Burn down charts

We already have a burn down chart at the iteration level. We could introduce one just lack that to track release scope and timeline. Here is my take on a simple burn down chart:

• Good
  • Rather straight forward to see if a team is going to finish on time, early or won't finish everything they committed to do.
  • Simple
• Bad
  • When variance occurs, there isn't any information about what caused the variance: added/removed scope, mis-estimation
  • There is no trend line to make the determination of on/off track in a very easy way

Mike Cohn thought about this and came up with an Alternative Release Burndown Chart