We are a small team responsible for a number of rather heterogeneous software applications, ranging from small VB desktop apps to complex web sites with many tens of thousands of source files. These applications have different requirements in terms of building and deploying, and their own unique directory structures for source and build/output files. From a strictly version control perspective, this looks to me like a clear case for multiple team projects.
On the other hand, we are a single small team. We need to manage our work as a single integrated backlog and a single sprint at a time. Any team member can work on work items for multiple different applications during the course of a single sprint/iteration. From a strictly process perspective, this looks like a clear case for a single team project.
Any suggestions for how to best reconcile this dilemma in TFS, since TFS seems to approach source control structure and process structure as two faces of a single entity?