Before I get started, I apologize for being under the radar since TechEd US.  Although there are no excuses, I do have reasons.  :)  Here goes:

1. We've been very heads down making a push to release TeamSpec.  A few weeks ago I was going through the original specs from early 2006 and not only has it been a long time, we have learned an incredible amount about Word and TFS and how to integrate the two.  If you ever run into Joe, Tyler, Victor, or Rob at a conference and have about 8 hours to spare, ask them about what they've learned over the last year and a half.  We have a build coming, and we're VERY excited about it, we hope that you will be as well.
2. On the topic of learning, we've been doing a lot of learning about how software teams use document and spreadsheets to break out the plan, requirements, work in progress, progress reports, estimates, among other SDLC artifact type.  Brian and Eric have done some pretty exciting work around project planning and delivery for the Personify Web Application business using TFS work item tracking/reporting plus time tracking.  I'll try to lobby those guys to publish a whitepaper about how it's helping the services business measure work and scale.  In addition to learning from our organization, I've spent some time doing TFS SDLC Process Consulting to keep my hand on the pulse of the types of problems teams are facing.  If you are reading this blog you probably already know the good news: TFS can really help teams measure progress and scale interactions between team members.  The even better news is that TFS can be used to identify and manage the interaction between team members.  For example, a very typical interaction between two people in a team is defined in a Bug.  One person finds the bug and logs it against another person in the team.  The other person fixes the bug and assigns it back to the original person to verify the fix.  Every one gets this interaction, but it gets more interesting with other interaction (ie. between a Business Analyst or Account Manager and a Project Manager, between a Customer and a Developer and everything in between).  I'll leave the details of the learnings for a future whitepaper, in the meantime we're using these learnings to bake scenarios into TeamSpec and TeamLook.  We continue to see that these different roles desire to interact with each other using work item tracking through different mediums (some in Visual Studio and others in Office).

Onto the real reason why I started the post (see title).  Karrell Ste-Marie posted a quick review of TeamLook which makes us very happy.  It's always SO FUN to hear or read about people benefiting from our products!  Thank you Karrell for the very kind words!

"TeamLook is an excellent product that integrates with Outlook (2003/2007) and allow you to turn e-mails into TFS items (with attachments), make meetings from items, make emails from items, make outlook tasks from TFS items.

Thumbs up, this is a great product and well worth the 200$ price tag and will save your countless hours of time."

Check out the post at http://karell.blogspot.com/2007/09/team-foundation-server-and-teamlook.html.

Alright, back to work! :)