Agile SCM Talk

Record of TFS 2010 Beta 1 and 2 installations

The VS 2010 Training Kit looks really great! I'm just starting it and Brian K. and the team did a great job. It was a bit of a surprise to see the roadmap RTM date in the "What's New in Visual Studio 2010" PowerPoint presentation.

The training kit is posted on channel 9 and can be downloaded from there. Once installed it provides a complete set of material for VS2010 training that includes presentations, videos and labs.

I plan to work through all of it over the next week.

I have reached the point where I can say that I have installed beta 2. There are many features that I have yet to perform. But, I'm moving on and will create separate posts for that. Overall, Beta 2 was a great install experience. Lab Management still has a whole lot of room for improving the install/setup experience, but beta 2 was a big improvement over beta 1. Bob :)
- Last updated: 12/3

2010 beta 2 is available for MSDN subscribers today and is to be generally available this Wednesday.

Check out the video with Brian Keller on installing beta 2 on Channel 9: 10-4 Episode 33: Downloading and Installing Visual Studio 2010 Beta 2.

A training kit is also available that appear to be very comprehensive.

There's quite a long list of downloads to pick from. Here's what I selected:

There are a number of tools out there for time tracking and some that work with TFS. For example, see the TFS Timesheet application on Codeplex. The problem is that developers have to leave the IDE.

Some people are often surprised to hear that many people think this is a big deal. I am one of the many. The reason is that I have observed this over the past 20 years. It is because it is. A reasonble explanantion is that developers have a very focused work context that takes time to get into.

Having spent just a few weeks using the 2010 beta and exploring how it could be used by SW project teams, I found a WBS structure that seems to work very well.

The game changed with 2010 because it supports work item hierarchy.

Under your implementation phase in the WBS, list the user stories. Then under each user story list the implementation tasks.

Implementation

• Story one
• Code A
• Code B
• Code C
• Test Story one

Run test case

Fix bugs

When I installed TFS 2010 I used a domain service account (DSA) everywhere I was prompted for a service account. I was unable to deploy Lab Management (LM) environments from the MS Test and Lab Manager (MTLM).

The resolution was that (somehow) the application tier service account was using the local network service account and not the DSA. Once I corrected this I was able to deploy the VM environments as part of a test run from the MTLM.

Now that I have the 2010 beta 1 installed, I'm working on a demo that I will then further expand into walk-throughs for supporting training and VSTS/TFS evaluation by our SW Engineers.

I'm still having problems getting the MS Test and Lab Manager (MTLM) to deploy an environment (I'm a Hyper-V/SCVMM newbee). However, I'm moving on still keeping the fire burning on getting thoses MTLM issues resovled ASAP.

For the demo I'm using a team collection with three team projects assuming a product line (shared code) development model. I'm using the MSF Agile v5 process template.

Posting this link to the Teams WIT Tools blog for posterity: Team Explorer 2010 Beta 1 Compatibility