We are looking into how to construct an implementation of TFS that will support a multitude of projects that utilize and have dependencies on other projects within.
Let's say we have 2 projects - A & B plus we have another enterprise project for a data warehouse that spans both projects.
The goal is to be able to link, track and report on activities going on in the data warehouse that impacts either of the 2 other projects and be able to report and notify whenever there is a change that may impact either project. An example might be a change to the customer table in the warehouse that impacts both systems versus a change to the product table that only effects project A.
We could just have 1 project with all 3 projects within it broken out by area and that would work but taking it now to an enterprise scale we would eventually end up with one project for the entire company and all other projects (related or not) would be
under this one umbrella. I have read posts recently that this may be the best way to go but I wonder what best practices are when trying to solve an issue of this magnitude. Any help or thoughts appreciated. Thanks.