Scrum for Team System 2.2 Released – More Reports, bug fixes, SQL Server 2008 and new Report Slide Show feature - Greg's Cool [Insert Clever Name] of the Day

Wednesday, October 15, 2008

Scrum for Team System 2.2 Released – More Reports, bug fixes, SQL Server 2008 and new Report Slide Show feature

Scrum for Team System – Announcements - Scrum for Team System Version 2.2 released

“Today sees the release of the Scrum for Team System version 2.2 process template.

Version 2.2 supports the following environments:

TFS 2008 / TFS 2008 SP1

SQL Server 2005 / SQL Server 2008

WSS 3.0 / MOSS 2007

What’s new in version 2.2?

New Engineering Practices reports:

Build Code Churn

Build Duration

Build Files

Build League

Build Quality

Build Static Analysis and Compile

Build Unit Tests

Builds

Code Coverage

Last Build Unit Test Results

SharePoint Portal

Installer now includes the fixes required to upgrade the SfTS 1.2 project portals

"Reports List" Web part fixed to show report list when Team Project Name contains spaces

…

Report Slide Show

A new feature of version 2.2 is the “Report Slide Show”. This is a web based utility to show a rolling display of reports which is ideal for display in the team area. The display duration and report selection is controlled by a configuration file hosted on the serve. The list of team projects reported on is controlled by the web page query string.

Upgrading 2.x projects to version 2.2

Included in the installed components is a command line utility that will upgrade your existing (Version SfTS 2.x) team projects to the latest (2.2) version.

…

Version 2.2 and SQL Server 2008

Also included in the installed components is a SQL Server 2008 patch…

…”

Sometimes it’s the little things… We have Project names with spaces, so the above mentioned SharePoint Portal fix will be nice to have. Much easier than not using spaces, underscores or building our own report lists manually.

The new reports are pretty cool too. Especially since in our current sprint we getting a good number of unit tests in and a fairly high code coverage… ;)