Once everything was setup I started to play. Here's how it went:

1. Connected to the VSTS app server from Visual Studio
2. Created a new Team Project
3. Added a new task to Currituck to create the system design.
4. Ran the All My Team Project Work Items Query (found 49, 1 was mine, the others are there by default)
5. Ran the All My Team Project Work Items Query and sent it to MS Excel
6. Modified the status of a task in Excel and synchronized back the server
7. Created a new solution and added it to source control
8. Right click on the solution and view the class diagram
9. Created a class for person and address using the class diagram
10. Checked in my changes
1. When I did this I associated my code changes with the create architecture task.
2. When I did this, it prompted me for who reviewed my code, I added a reviewer name, and re-checked in.

I really like the integration of everything.  I love that I can now link both tasks and bugs with checkins.  The system I use at work now is a pain because I have to modify code, check it all in and then go and modify the status of any bugs that I may have fixed.  With team system this will all be integrated with the checkin.  Very nice.

I also am impressed with the class diagram stuff.  It will make it much faster to quickly design classes and object models. 

Finally I love that you can enforce rules at checkin.  We all know that when deadlines get close, tasks like unit tests, code/pier reviews, and fxCop gets put on the back burner to turning out code.  If you define a policy up front and enforce it through the whole project, then you can't forget about those very important tasks. 

I can't wait to do a real project using Team System.