Continuing from my previous posted. I’d like to give an overview to the new engineering practices reports included in the Release 2.2.
Across a user selected time period (defaulting to the current sprint), this report shows the total builds per day broken down by status.
Build Static Analysis and Compile
This displays the number of Errors and Warnings either compile or static analysis the last N number of builds.
Build Unit Tests
Shows the total number of units test run from the last N number of builds. The total is broken down by number status of unit tests for each build.
Last Build Unit Test Results
This report displays the list of each test that was run for the last build and shows the result of that build. If the unit test failed it will also display the fail message as well. The last build is taken to be the last build within the data warehouse.
This report shows the code coverage of and the total of code churn for last N number of builds. The coverage units can be selected between blocks, which is the visual studio default, lines or partial lines.
Build Code Churn
This report shows the total “Code Churn Counts” of the last N number of builds broken down by Added, Modified and Deleted lines. This report also features a drill down option which links to the Build Files reports.
This report, which is also a drill down for the Build Code Churn report, will display the files which were in the build or between two builds. The files are grouped by the folder in which they are located within source control and display the number of Added, Modified and Deleted lines for each of the change sets. Also included is the following change set information: Check-in by, Date, Policy Override Comment.
This report is a based on the MSF for Agile Software Development Quality Indicators. This has been added by popular request and inspired by a blog post by Ed Blankenship: (http://blogs.infragistics.com/blogs/eblankenship/archive/2007/06/18/msf-agile-quality-indicators-report-for-conchango-scrum-process-template.aspx).
This shows how long the last N builds took to complete.
This will show a League table of the Top N number of people on their total number builds of Fail or Successful Builds (using either an absolute number or percentage base). This report will run for a selected period defaulting to the currently running sprint. A successful build is defined as any build which not in a state of failed. (Which is not the same as a successful build.)
There is one caveat: The way in which a build is counted against a person is if their change set is linked to a build. So some people will gain some builds fails even if their change set is actually not the reason why the build failed.
All the reports will have the option to select which build type to run against. Also where the reports allow an N number of last builds they have been limited to the following values 10,15,20,25 or 30.
These reports are not actually link to the Scrum methodology but are helpful tools in the engineering practices. There will be a separate forum for issues and question which can be found here: Engineering Practices – v2.2 Reports
New Reporting Features available in Scrum for Team System v2.2
Build Reports added to Scrum for Team System v2.2
The Scrum for Team System report slide show tool
Scrum for Team System Version 2.2 support for SQL Server 2008