Think Before Implementation of Team Foundation Server (TFS)
Introduction
In an organization multiple development project or business unit are exists they need isolation in the context of security, manageability, schedule maintenance and administration backup restore etc. TFS Server can have one or more Team Project Collections. Team Project Collection can contain one or more Team Projects.
What will be the criteria to make a project Collection?
- Project has same requirement and objectives
- Autonomous User group required to isolate and increase operational security
- Team groping require which belongs to same objectives for that they share same artifacts, work items, source code base and
- Team wise physical and logical resource management require
- If you want to keep all artifact ,source and data in a single database
- An autonomous code base that can be built, branched, merged, and iterated according to the needs
http://4.bp.blogspot.com/-A0HmH7n3_us/UVAQ8DQbKaI/AAAAAAAAATA/lOtO-M2_OgY/s1600/Team+Project+Collection.jpg
What will be the benefit for making Team Project collection?
- Smoothly handle operational need i.e. Specify process, isolate user group, code grouping.
- Easy schedule maintainability and administration
What will be the criteria for making team project?
If you make many team project collection for same development project then have to face following problems:
- Work item can’t be link between multiple project
- Security and user handling same user need to create on many team collection
- Sourcing control level problem branching and merging can’t be done between multiple projects
- For reporting purpose it’s not possible to view report query on multiple project.
For reducing many team project collections you need to make Team project.