If you keep each VS solution in one team project in TFS how do you handle situations where you have to work on two solutions with the same scrum iteration? Because you have different backlogs for each solution you would need to have two different sprints and that doesn't seem very efficient. right? You can't tie in work items from different team projects together and have them run under the same sprint/iteration. According to the TFS 2010 book by Wrox, one soltution they suggest is to put all applications into a single team project and seperate them by "areas" and "iteration". Isn't this a better solution then creating one team project for each and every solution given TFS limits team projects to something like 250 before performance degradation.

chuckdawit wrote: Keep in mind our WPF application isn't the only application that uses these 3 libraries, we have other solutions that use these libraries. I think this here is what defines it. If these projects are used by more than just one solution, it is usually a good idea to keep them independent. As for your TFS question, I think the other option you are missing is creating 1 independent Team Project for all these libraries so as for them to remain completely independent from the projects that are using them. As always the devil is in the details and it will depend, among other things, in how these libraries are connected to one another.