putting VS projects/solutions in a TFS team project
-
I'm a little confused about the TFS team project hierarchy. From what I have read just about everything for your group (projects/applications/etc) should be contained in one TFS team project? Can anyone concur with that statement? I, for some reason, thought that a single team project in TFS was mapped to one VS project/solution, but I think I misunderstood the hierarchy. I know it can but it seems like complications will arrise when you have to work on two team projects in the same scrum iteration. The work items don't translate over from one project to another.
-
I'm a little confused about the TFS team project hierarchy. From what I have read just about everything for your group (projects/applications/etc) should be contained in one TFS team project? Can anyone concur with that statement? I, for some reason, thought that a single team project in TFS was mapped to one VS project/solution, but I think I misunderstood the hierarchy. I know it can but it seems like complications will arrise when you have to work on two team projects in the same scrum iteration. The work items don't translate over from one project to another.
I don't think putting all your projects/solutions in the same Team Project would be very wise, mostly because, depending on the size and depth of them, it could become unmanageable pretty soon. In the end I think it all depends on how your team likes to organize (especially, if you are gonna use TFS as more than a glorified VSS) but I prefer to have every solution in its own Team Project
-
I don't think putting all your projects/solutions in the same Team Project would be very wise, mostly because, depending on the size and depth of them, it could become unmanageable pretty soon. In the end I think it all depends on how your team likes to organize (especially, if you are gonna use TFS as more than a glorified VSS) but I prefer to have every solution in its own Team Project
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.