index > Team Foundation Server - General > How to break up projects?

How to break up projects?

Are there any comprehensive books or papers on TFS? I'm looking for some insight into what you need to take into consideration when creating projects under TFS. We currently have over 50 solutions in our organization, and hundreds of "projects" in those solutions.

Should I be creating a TFS project for each solution we have? I haven't found any documentation which describes what a TFS project is supposed to represent. As a matter of fact, I haven't seen any particularly good real enterprise examples.

For example, it would be great if MS gave their TFS structure. They probably use it the most, so I'm sure they've run into all of the different issues.

To give a little insight into the issues I've been pondering I'll give a little overview of our organization. Most of our solutions interact with each other in some way or form. Developers work on particular solutions, but are often working on several at a time. I was considering the one solution one TFS project idea, but I'd like to know that that developers and architects that are working on more than one TFS project will be able to organize themselves well.

I've considered setting up a single TFS project for the entire organization, but I'm not sure that is correct. What is a TFS project supposed to represent?

bpeikes

A team project corresponds to a way of doing development - an instantiation of a methodology.

If all of your teams use the same set of rules to govern their work, then putting all of the solutions in a single team project is appropriate.

If, on the other hand, you have some groups that follow a rigorous methodology (e.g. RUP) while others follow a more agile methodology (e.g. MSF), then it would be appropriate to put these development groups in different team projects.

A Team Project defines a container for:

Work Items and Work Item Types. It's inconvenient (at best) to work with work items from different team projects.
A collection of reports
The top-level folder of a source-control hierarchy. You CAN merge/move/branch files and folders between team projects just as you would within a single project.
A Sharepoint portal site. The portal site serves the entire team project.

HTH

-cd [VC++ MVP] Mark the best replies as answers!

Carl Daniel

reply 2