Martin Woodward, one of our newest Team System MVPs, was recently asking me about how we manage work within our team and if I'd be willing to share our TFS work item types to give a real world example. Our dogfood usage of TFS is one of my favorite topics and I'm interested in sharing with you our experiences both good and bad in this space. I don't for a moment argue that we have the ideal implementation of TFS. We're frequently trying new things, some work well and others don't. Plus we're part of a larger team (Developer Division) and as a result, there are constraints and requirements placed on us that don't map super well to how we'd like to run our Team System team. Probably sounds familiar to many of you.
Looking at our dogfood server, we currently have the following work item types in use for the Orcas project:
I'm excited that we're always finding new ways to utilize Team System to manage Team System. It drives goodness into the product as we solve the problems we find as we push the system in new directions. There are a number of additional ways that I'd like to push the system including tracking our minor releases (such as TFS PowerToys) and feature dependencies. As we do this, I'll be sure to share with you.
I'd be happy to further explore and describe any of these work item types as people find valuable. Let me know what you want to learn more about and I'll see what I can do to share what we've got.