Introduction to Team Foundation Server :

Customer needs best practices for their business challenges.TFS can help us to solve customers’ complex business problems like reducing waste, driving down risk, and delivering on business intent. If your customer has set any of the following business goals, chances are they are looking at reducing waste:

• Eliminate rework, and reduce errors introduced and time wasted in hand-offs between functional teams.
• Automate complex and error-prone tasks.
• Standardize on process across functional teams.

Team Foundation Server is highly customizable and automatable. Work item definitions, source control policies, build scripts, process templates, and programmability interfaces all enable customers to tailor their Team Foundation installation to their need.

VS TFS 2010 meets these needs with:

• Streamlined data flow—the central repository enables in-context collaboration (work items that tie it all together)
• Automation—build automation and automated testing
• Agile, SCRUM, and CMMI process templates

Team Foundation Server 2010 is a totally integrated solution:


TFS 2010 is a totally integrated solution. You benefit from the work we did to integrate tools an processes allowing you to focus on core competencies and delivering value to the business.

Improve Flow & Reduce Waste:


1. Collaboration and Streamlined Data Flow:

• Project artifacts are stored in a central repository that facilitates in-context collaboration to reduce waste in hand-over time between tasks and streamlines the development process.


• Team members can instead focus on delivering value over transitioning information between roles.
  Seamless support for Eclipse extends these collaboration benefits to heterogeneous environments and allows you to standardize on process and tooling across teams working on different technologies.


• Work items are the glue that enable the rich collaboration. When you associate a work item with the requirement, code, test cases, test results, resources, etc., you can track and manage the entire end-to-end flow of the process and data. 


• Everyone on the team is always looking at the same data, and it is always in the context of the task that individual is working on.

2. Process Automation:

The build process is a critical part of the overall application life cycle. Customers usually have custom workflows around their build processes. The process is however very complex and error-prone. Consequences of build breaks or incomplete deliverables are usually show-stoppers and expensive to fix.   TFS 2010 offers rich automation capabilities. These capabilities let you automate complex and error-prone manual tasks. Windows workflow-based builds with powerful features like build queuing and build agent pooling enable teams to easily customize, manage, and scale out their build environments.
Powerful capabilities like the new gated check-in helps teams working in the same branch to prevent costly and time consuming build breaks by testing code in isolation before it goes into the full repository.

3. End-to-End Traceability:

Missed or partially implemented requirements are often the cause of cancelled projects. Historically it has been very difficult to easily determine things like:

• How many times requirement changed
• Which release or build contains the requirement
• How much test coverage was accomplished
• How many bugs were found, fixed and left unresolved for a specific requirement
• Who worked on a specific requirement

With TFS 2010, requirements are defined as work items and can be associated with check-ins, test cases, bugs and builds. Work items are assigned to team members and managers can easily view relationships between these project artifacts and resources. TFS provides end-to-end traceability, and lets you track progress and quality back to business goals and customer requirements.