TFS and Team Projects
So, at the work, I am currently our teams TFS administrator and “guru” (for want of a better term – I’m sure I don’t know that much about it!!).
We’re in a state of flux at the moment, with a range of projects spread across (now) 3 CM repositories – Clearcase (mostly VB6 code) several VSS databases (the two I have access to are both well over 2GB in size) and now TFS Version Control.
TFS has been chosen as the “way forward” for our .net competency worldwide, and according to ET, our global TFS Guru (and a TFS MVP), EDS have the largest TFS user base in the world…so with more and more of our devs needing to use it, I’m going all out to try to figure out what the best way to organise Team Projects is.
I’m struggling a bit with the granularity of Team Projects – I can do one of two things: Firstly, we could do a Team Project per dev project, but as some of our dev projects consist of a team of 1 whole person, that seems a bit like overkill! The other option is to do a Team Project per client/customer. The problem with that however is that we’ll get work items (in particular) that belong to one dev project showing up in the reports, queries, etc for the other dev projects in that Team Project.
I’m hoping that Areas are going to be the answer to this….if anyone has any other ideas, by all means, please post comments. I’ll also post a followup to this post once I’ve tried it out…
