Team Foundation Server has been a reliable tool for projects across organizations. On One hand wherein it might be thought as a Configuration Management Tool, It actually is a complete Application life cycle Management(ALM) tool. With the advent of Visual Studio Online, It is now possible to have free instance of TFS in the Cloud. However, working with TFS has its own architecture and hence the tips and tricks.
Project Collection can better understood as Account or Department. For. eg. one Line of Business in an Organization is Banking. We would create Project Collection called Banking and underneath it all the Projects of banking would be created. The basis need of Project Collection is to isolate the data among different project collections.
Projects vary according to the Lifecycle of the projects. Thereby, TFS provides us with three different Process templates viz.
1. CMMI Template
2. Agile Template
3. Scrum Template
These templates can be adopted on the basis of the Lifecycle and Model of the Project.
In case the Project Lifecycle is based on CMMI which can be thought similar to Waterfall Model, then the Process template for CMMI is used.
Agile methodology for Sprints is Supported by the Agile Template. This is best suited for development projects.
Agile Methodology for Kanban is supported by Scrum Template. This is best suited for maintenance projects.
Thus this was a jist of the Project Collection and projects and process templates in TFS.
TFS has an architecture that Underneath the installation of TFS, there are project collections. Under one Project Collection, there can be Several projects and under the project we have the teams working together.
Project Collection can better understood as Account or Department. For. eg. one Line of Business in an Organization is Banking. We would create Project Collection called Banking and underneath it all the Projects of banking would be created. The basis need of Project Collection is to isolate the data among different project collections.
Projects vary according to the Lifecycle of the projects. Thereby, TFS provides us with three different Process templates viz.
1. CMMI Template
2. Agile Template
3. Scrum Template
These templates can be adopted on the basis of the Lifecycle and Model of the Project.
In case the Project Lifecycle is based on CMMI which can be thought similar to Waterfall Model, then the Process template for CMMI is used.
Agile methodology for Sprints is Supported by the Agile Template. This is best suited for development projects.
Agile Methodology for Kanban is supported by Scrum Template. This is best suited for maintenance projects.
Thus this was a jist of the Project Collection and projects and process templates in TFS.
No comments:
Post a Comment