Team Foundation Server 2010 Project Structure With Small Teams

At my company, we have a very small (<5) team. We build internal web applications of which we support about a dozen and expect to add more.

We are setting up TFS 2010 and wonder what the best structure is? We don't work concurrently on a project, so I think we don't need branching. But do we create all our solutions under one Team Project or create a new Team Project for each web application?

We also have a few class libraries shared in all the web applications. How do we manag开发者_运维知识库e this? I've Googled all day on it and just gotten more and more confused.

I've looked at the guidance but it all seems pointed towards more complicated scenarios with bigger teams working concurrently.

Looking forward to any help, Richard

I think you will find branching useful even if you have a development team of one!

Being able to try out significant code changes and being able to merge them back to the main (trunk) code is great.

In terms of shared class library projects, you can actually add them to more than one solution at any given time.

Of course changes will only happen in that project, and therefore every solution that uses them will be affected. Therefore you should set up 'continuous integration' on your build server in order to check that other solutions are not adversely effected.