Team Foundation Server automatically instruments the development process so that a wide variety of metrics are gathered throughout the development life cycle. Decision makers can use this data to get a real-time snapshot of the state of their project allowing them to make corrections to their processes to ensure that the project is completed as desired.
The upper red area indicates the number of requirements that have been assigned to this iteration. The yellow area below that indicates the number of those requirements that have been resolved by the development team, but not yet confirmed as completed by the QA team. The green area along the bottom indicates the number of requirements that have been tested by the QA team and determined to be complete and subsequently closed.Notice that the boundaries of the yellow and green areas trend upwards, but by the end of the iteration all of the requirements have not been closed.
The teams did not make their milestone. For the development team to have completed all of their requirements on time, the green area must intersect with the red area before the end of the iteration.
This graph displays more favorable results. The trend displayed from the bottom green area shows that all of the requirements were resolved by the end of the deadline, but were not closed. Were there enough testers? Were your customers not participating in user acceptance testing in a timely fashion?
The dotted line displays the average number of Requirements resolved over the time span selected. The bug rates are quite high and stay high until the beginning of the stabilization iteration. The team seems to do an excellent job closing bugs once stabilization begins.
The red areas represent failed tests, the yellow area represents inconclusive tests, and the green areas represent passed tests. As you move from left to right, notice that the green areas expand while the yellow and red areas shrink. In an optimal scenario, the number of overall tests would also increase.The line graph that represents code churn should show a downward trend from left to right. In other words, over time, the number of lines of code that your development team is adding or changing should decrease as your application stabilizes.
The line that represents active bugs should show a downward trend from left to right. This indicates that over time, the number of active bugs in your application should decrease as your application stabilizes.
The line that represents code coverage should show an upward trend from left to right. This indicates that over time, the lines of code that are covered by automated tests should increase as your team writes more tests.
