There are several reasons why we don't find the tradition burndown to be an useful indicator of progress and overall health. (That's the topic for an upcoming post.) In the meanwhile, here's the mark-up for a Fixed Date Progress Report, which we (ThoughtWorks Studios) feel is more useful than a burndown:
aggregate: SUM('Story Points')
start-date: (Release start date)
end-date: (Release end date)
target-release-date: (Release end date)
chart-conditions: Type = story
scope-series: All Stories
completion-series: Completed Stories
- conditions: Status = Accepted
label: Completed Stories
- label: All Stories
The underlined bit show the parts you might need to change to make this fit into your project:
- aggregate: SUM ('Story Points') -- This should be an aggregate (SUM, COUNT, etc) of any numeric property. This will be the basis for the Y axis.
- start-date / end-date -- Either hard code these to a date or use a project variable, as shown in this example. If you are putting chart on a card (not a wiki page) you can also use THIS CARE.'Start Date', assuming of course that the card has a property with that name. These values determine the scope of the X axis.
- Type = Story -- Tells Mingle which card type to use for the data in the chart
- target-release-date -- This sets the fix date that is the deadline for the work shown in the chart
- conditions: Status = Accepted -- This is a MQL statement that will determine which stories are counted as done
That mark-up produces this chart:
In this example, we can see that currently (ie, on Jun 6 when this screenshot was taken) the total scope is 144 points, of which 58 points have been complete. This chart is forecasting a 21 point deficit on the deadline of Sept 30, 2012.
Please sign in to leave a comment.