Saturday, January 23, 2010

Microsoft Rangers Projects

When I start talking to people about the Rangers project that I was working on last night or over the weekend I get a lot of blank looks. "You know the Microsoft Rangers". More blank looks. OK so maybe they're not as widely known to everyone as they are to me. The words on their home page state it well.

"Team System Rangers deliver out of band solutions for missing features and guidance in the Team System suite of products."

The Rangers themselves are Microsoft employees that are dedicated to working on these out of band solutions. The Rangers also leverage MVP members to contribute to these projects as well. That's were I come in.

Currently I am working on two upcoming projects that I am very excited about. Visual Studio Database Guidance and Visual Studio Architect Guidance.

I have felt that the database projects that are commonly known as the "Data Dude" pieces have been vastly under utilized by the development community. There are some really amazing tools there that will change the way you develop database solutions. I've been huge proponent of them since they were first delivered and I'm exceptionally pleased to be part of crafting this guidance.

The other project is also quite dear to me as I have been working quite closely with the team up in Redmond that has been building the Architect tools for quite some time. It has been very cool watching these tools evolve over the past many months. This guidance will be very relevant as the architecture tools the are being delivered with Visual Studio 2010 are all brand spanking shiny new.

So, that's what's been keeping me amused besides the ton of work that's involved when starting a new job as a a Software Engineering Manager for Sage Software. Phew....

Visual Studio 2010 TFS Upgrade Guide

Visual Studio 2010 Team Foundation Server is no small change from 2008. It's big, really big. The team back at Microsoft really took to heart the feedback from the users and community and incorporated some great new features and capabilities. Of course, this means that a lot of stuff under the covers had to change. Which means that moving from 2008 to 2010 isn't necessarily an extremely straight forward experience, especially if you want to use some of those cool new features in your existing projects.

Enter the Guidance. This is yet another Microsoft Rangers project that was recently delivered to Codeplex here. Great work guys!

Visual Studio 2010 TFS Upgrade Guide
Welcome to the Team Foundation Server (TFS) 2010 Upgrade Guide. This guide covers scenarios which may be encountered during and after the upgrade process. It provides examples of most common and potential issues. It covers scenarios related to general Upgrade Process, Work Item Templates, Reports, and Enterprise TFS Management (ETM). Although this guide refers to TFS 2008 scenarios, almost all the concepts apply also to TFS 2005.

Visual Studio ALM Rangers
This guidance is created by the Rangers who have the mission to provide out of band solutions for missing features or guidance. This content was created with support from Microsoft Product Group, Microsoft Most Valued Professionals (MVPs) and technical specialists from technology communities around the globe, giving you a real-world view from the field, where the technology has been tested and used.

What is in the package?
A single document with the following contents:
1 Introduction
2 Upgrade Process
3 Scenarios
3.1 Upgrading Projects from Multiple TFS 2008 servers into one TFS 2010 server
3.2 Upgrading severs when SQL Mirroring is enabled
3.3 Recovering system if upgrade fails midway
3.4 Updating Team Project Portal for an existing Team project
3.5 Splitting Team Project Collection into Multiple Collections
3.6 When I move a Team Project Collection, how do I move the reports?
3.7 Bringing Workgroup Machine inside Domain
4 Frequently Asked Questions
4.1 Can I use a TFS2008 Process Template to create team projects in TFS 2010
4.2 How can I enable Agile Workbooks in upgraded Projects
4.2.1 Enabling the Product Backlog Workbook
4.2.2 Enabling the Iteration Backlog Workbook
4.3 How can I enable Test Case Management in upgraded project
4.4 How can I enable Branch Visualization in upgrade projects
4.5 How can I enable Lab Management in upgrade projects
4.6 What is WIT Admin Tool
4.7 What happens to my custom reports created in TFS2008 post upgrade?
4.8 Will my old TFS2008 reports work post upgrade?
4.9 Can I add a new Database to my existing TFS 2010 farm?
4.10 Error bringing cloned Team Project Collection online
4.11 Move Team Project Collection Database from one Database server to another Database Server
4.12 How to enable the TFS reports if the WSS server is upgraded to MOSS server?
4.13 How to Move Team Projects from one Team Project Collection to another
5 References

Team
Pramod Vasanth, Bijan javidi, Willy-Peter Schaub, Anthony Borton, Neno Loje, Bryan Krieger, Aaron Bjork, Mario Rodriguez

Saturday, January 16, 2010

Visual Studio 2010 Team Foundation Server Requirements Management Guidance

It has been a long time coming but on Thursday January 14, 2010 the "Visual Studio 2010 Team Foundation Server Requirements Management Guidance" was finally released. You can get this set of documents from codeplex here!

It is always exciting to see a project that you have been involved with come to a conclusion and see the light of day. I encourage everyone to take a look at the guidance. Bijan, Willy and Mike worked very hard on this along with me and several other Microsoft Rangers and MVPs. Here is the blurb from the codeplex site:

"This Ranger solution addresses the People, Process, and Technology guidance for Requirements Engineering (RE) using Team Foundation Server. The goal of this guidance is to provide formalized Microsoft field experience in the form of recommended procedures and processes, Visual Studio Team System and Team Foundation Server configurations, and skill development references for the Requirements Engineering discipline of your application lifecycle."

As one of the contributors to this project I am excited to hear any feedback that you may have and I hope that you find it helpful.