Agile SCM Talk

I never did install RC as perf issues weren't a impediment for me. I upgraded a number of B2 environments. A few of which I describe below.

1. Windows 7 with VSTFS
I simply downloaded the ISO install DVD for VS 2010 Ultimate and Team Foundation Server; uninstalled VS and then uninstalled TFS. Then I installed VS 2010 for TFS and then Ultimate. No problems were encountered and everything worked fine.

2. WS08 SP2 x86 VM

This artile provides a summary of keynote and break out sessions I attended. Channel 9 coverage of the event is available here. Most of the new 2010 features were presented and demonstrated.

Monday Keynote – Visual Studio 2010 Launch

Here's a summary of TFS 2010 enabled improvement opportunities. This is based on my research and work with TFS 2010 to-date. Unlike a list of features, this information is organized around the typical work and tasks performed by software engineers.

Customer Management

• Integration with Microsoft Dynamics CRM software supports workflow integration between customer management and engineering

Requirements management

April 12 is the New Release Date for Visual Studio 2010. At least that the latest from Microsoft's Rob Caron. He's the Marketing Communications Manager for Developer and User Experience Runtimes and Tools at Microsoft — which includes of course Visual Studio. He recently presented a quick update on the new release date for Visual Studio 2010.

I assume this includes TFS (i.e. VS 2010 ALM)?

The VS ALM Rangers have just published a Visual Studio 2010 Quick Reference Guide. The guide is designed to quickly review the capabilities and features of the 2010 version.

When using TFS work items you may find that when you transition from one state to another that you selected the wrong reason code, or you found out shortly afterwards that the reason code you selected is incorrect.

Well, you may be surprised to find that reason codes (System.Reason) cannot be updated within the same state.

Those of us that started working with TFS 2005 know what a "terror" installation and upgrading can be. TFS 2010 holds out the promise to be different.

This recent post by Brian Harry provides a good example of the manageability that I hope 2010 will realize for us.

We don’t use the term “Bug,” rather we use “Software Action Request” or “SAR.” I renamed the Bug WI definition from Bug to SAR. I added a few custom fields to our SAR WI definition, but all the Microsoft fields are used and unchanged.

What I want is for the MTLM client to be configured to open a SAR rather than a Bug. In other words, out-of-the-box when a user is manually executing a test case with the MTLM Test Runner client and one of the steps fail, the user clicks a button to create a Bug or link to an existing Bug.

My goal was to have the burndown chart on the team project portal main page display the current iteration.

The default report displays the tasks for the entire team project starting 5 days before the current date and ending 25 days after the current date. FRUSTRATING, to say the least! I mean, what a useless report! Who's Agile book did they get that one from?

Here in sunny LA the annoucements at PDC 2009 are significant. Though many new features are catching up to what Apple can already do, the integration and breadth of the 2010 releases is big!

Software Releases Announced

• Public release of beta versions of:
  • Office 2010
  • SharePoint Server 2010