There are many different individuals perform various types of administrative function using Team Foundation Server. Each of them looks at Team Foundation Server in a different way to solve their problems, or make their daily work lives a little easier.
Everyone knows the enterprise IT administrator. He is the guy (or gal) who keeps the corporate infrastructure up and running. He watches and fixes problems with the network, makes sure e-mail is always working, and fixes problems with user accounts. He is concerned about the servers on his network, especially to ensure they are functioning properly. His daily concerns are for the reliability, availability, and performance of both his network and the servers on it.
He doesn't expect too much from Team Foundation Server. He just wants an application that works easily within the current security and software requirements of his organization. He also wants it to easily integrate into his existing disaster recovery procedures, so as not to create extra headaches for himself. That's not too much to ask, is it?
Team Foundation Server meets these expectations. It supports multiple deployment types, from a single server installation to multiple servers that will scale easily to meet demand. The servers can be members of an Active Directory domain, or a simple workgroup. Because most information concerning Team Foundation Server is stored in a database, integrating TFS into disaster recovery plans can be as simple as adding another database backup to the procedures.
The Group IT administrator is usually a member of the development team. This person provides support to other members of the team. You know, the one everybody turns to for help, whether it is a programming question or a network issue. He is also the one who makes sure all the hardware and software systems used by the development team are in working order. He tries to keep everything running smoothly for the team members, so they can focus on their work.
He wants, from Team Foundation Server, an application with minimal administrative overhead. It also needs to provide good performance for the team. Additionally, he would love to have some sort of security control independent of the enterprise IT administrator. This would allow him to make the security changes necessary for people to do their jobs quickly and easily.
Team Foundation Server meets these expectations. Team Foundation provides excellent performance with a minimum of administrative maintenance. You can install multiple Team Foundation application servers, as needed. You can use the Team Foundation proxy server to speed up access to the version control system. Team Foundation Server also has its own built-in security model, giving the group IT administrator all the security powers needed for Team Foundation Server. For more on this security model, see Chapter 4.
Everyone knows what the developer is responsible for, right? Everything! Just kidding (kind of). A member of the development team could be responsible for any aspect of the application. This includes designing an application, actually writing code, managing the nightly builds, or maintaining existing systems. Team members usually wear multiple hats and provide assistance on some or all the previous responsibilities mentioned.
What team members expect from Team Foundation Server is an application that deploys easily and quickly, has low administrative overhead, ties into their tool of choice, and enables them to complete their work in a more efficient manner.
Team Foundation Server meets these expectations. Team Foundation Server ties into Visual Studio 2005, Microsoft Word, Microsoft Excel, and Microsoft Project, allowing team members to use their tool of choice to complete their work. The functions of Team Foundation Server, including Work Item Tracking and Version Control, provide new and easy-to-use functionality, which will increase the efficiency and productivity of team members.