Our company is in the process of migrating from Team System 2008 to Team System 2010 now that Beta 2 with the “Go Live” license has been released.
Why the hurry? Project Management and the improved Reporting are probably the 2 biggest improvements in Team 2010 that we are eager to use. Prior to Team 2010, Project Management via Team was less than adequate for us using linked-work items. But now with hierarchical Work Items, for us Project Management is now something we are willing to commit to in Team 2010 and so far we like what we see. Using the Agile template and a few little tweaks to the work item template to track a few extra fields specific to our software, we will be using Agile’s User Story work items to start enhancement projects and high-level projects. These User Stories can be directed to development leaders to be broken down into much smaller tasks, scheduled among the staff, and the work estimated. Once this has been done, we plan on returning the User Story back to the Project Manager who using the much improved built-in reporting can monitor all of the related tasks for that User Story. The backlog & burndown reports, the dashboards and the Excel integration are awesome and we are eager to get everything migrated to begin using it.
Prior to this we used Team solely for Source Control, Work Items for bugs, and nightly builds.
Rather than show you the reports and dashboard available – I will do you a bigger favor and direct you to Mr Brian Harry’s blog where he covered this in great detail (and with far more awesome screen shots that I could have) – Please check this post out – its incredibly detailed and thorough – Project Management using Team 2010
(If you are using Team System or thinking of and have not found his blog – stop right now and add him to your blogroll and RSS Feeds – you know you have found a gem when searching for different optics in Team continue to always bring you back to his blog – I have wised up and just start there now)
One little gotcha that may save you a headache that we suffered from for a few hours is this cute little error that popped up from a certain machine trying to Import/Export Team work items from Excel. The error would have you believe that TFS Integration tools are improperly installed on that machine
Team Foundation Error
TF80012: The document cannot be opened because there is a problem with the installation of the Microsoft Visual Studio v10.0 Team Foundation Office integration components. Please see the Team Foundation Installation Guide for more information.
The solution to this cryptic little guy is to enable the Team AddIn from Excel AddIn Manager – which would make for a better error message as well for RTM.
So far the migration has not been painful and we have had no issues continuing to work in VS 2008 while migrating our code and work items to TFS 2010. But don’t forget to upgrade any Visual Studio 2008 machines that will be connected to your TFS 2010 server to at least Visual Studio 2008 SP1. Much more information on the upgrade from TFS 2005/2008 to TFS 2010 Beta 2 can be found here again at Brian Harry’s blog. Brian’s blog is well written, jam packed with info and my primary source of Team information. I though that this short bio on Channel 9 summs up Brian well.
Well, so far its gone well, I’ll report back in coming weeks as to which features of Team 2010 we are liking the most but I’ll predict it will be the Reporting and Excel integration.
Implementing change across multiple teams can sometimes be difficult and require alot of coordination but another side-effect of this migration has been a good review of what our processes are – and in my eyes, forcing actions like that are always a win for the company.
Have a good weekend