Some notes on Dec. CTP and VSTS
I actually posted this to the VSTS Newsgroups and realized that not everyone reads those, so I am putting it here as well. This was in response to someone that had been to the Visual Studio 2005 Training in Dallas as part of the Ascend program. He was trying to reconcile the VSTS labs done there (I was the instructor) to the new build.
Currituck is Work Item Tracking, drill down in there and you will see the ability to create queries, etc.
Hatteras is source control, and the featureset there is richer than what was in Beta 1R. I haven't played with branching/merging yet though.
The Public Build stuff is going to be part of the new build process that was discussed in the Ascend training, it's still not in the Dec. CTP though, that's more of a place holder, similar to reports. On that note, reports still aren't included.
The work item tracking features seem to be working well, as do the basic source control features. I can create project plans in MS Project if I initiate them from Project, not from Team Explorer. In all, most of the features from the Ascend training should work, but you'll have to change the workflow a bit. The profiling doesn't seem to work at all now (even though I posted otherwise to one of the forums). In Beta 1R, instrumentation worked, sampling did not, in the CTP, it detects that you are in a VPC and just aborts.
You should notice a lot more information about MSF Agile, one thing to be sure and do is to go into your services and start the WebClient service. I'm not sure what that is, but it's required to get the process guidance going. I set that to Autostart in my VPC. Once you do that, you can navigate to Documents > Process Guidance for your project in Team Explorer and double-click ProcessGuidance.html - very cool stuff.