Here is a code snippet that does all the work: I know this is quite some amount of code, so we’ll break it down into smaller chunks.

Sex talk longview washington - Tfs burndown chart not updating

explains what a burndown chart actually is and how the chart data can be interpreted.

It was this article that inspired me to have a look at how Microsoft’s TFS11 Team Web Access actually implements the burndown chart and to see if the functionality could be replicated using the client TFS API.

The value of this field is by default clauses to produce the complete query expression. Since we can have multiple team field values, and they can either include or not include child items, I’ve opted to first group all the team field values by their operator (as opposed to using multiple conditions which are OR-ed together).

You can see this on lines 40 through 50 in the above snippet.

In case it’s not that obvious, the ideal burndown trend line indicates the rate at which the remaining work should (ideally) decrease with time, in order for us to deliver all the work in time.

The actual trend line gives us a projection of how the work is actually decreasing and what it’s value will be by the end of the iteration.

We’ll need this field later in the second phase of the algorithm and that’s exactly why we’re returning it, rather then making more trips to the server to read it again later. We start of by retrieving an instance of the object for our team project.

This lets us know which work item field is the Remaining Work field, and which one is the Team field.

The value on the horizontal axis will most often be expressed as either a date or simply as an ‘iteration day’ (the -th day in the current iteration).