Azure DevOps Server

Formerly Team Foundation Server

We use Team Foundation Server in the Information Systems Department in our company. All developers have access to Team Foundation Server to do code versioning. We use it integrated with Visual Studio to check-in and check-out our projects' code. We also use the web interface to navigate between code versions and to manually download code when necessary.

We are currently managing a large project and we use TFS to manage bugs, code and releases. It is only being used by the technical team but others are coordinating with us to make sure their bugs make it into the system. As well, we are using data from the system to routinely give updates to management on the status of the project as well as any concerns or risks.

We use Team Foundation Server to manage manage almost all the projects and application packages. Team Foundation Server makes it easy for us to have good control of all the progress and it really helps in managing the whole release process even if a lot of developers and many teams are involved.

Team Foundation Server is used for version control of Microsoft .net applications, SSIS, SSRS. Also, TFS is used for tracking tasks, bugs and change requests.

We use Team Foundation Server as Source Control Managment System and for automated Builds and Tests. We don't use the WorkItem System of Team Foundation Server. We Used it a couple of years ago, but it was to complicated. Right now we just use Trello with a Scrum AddOn for Task and Backlog Planning. Right now only our Developers are using Team Foundation Server.

TFS is used across the organization as an Application Lifecycle Management tool. This addresses the problem of needing a central way to demonstrate the status of projects/applications.

In my organization Team Foundation Server is used to better manage all projects and application packages. Having several developers in place and having to work on multiple projects Team Foundation Server allows you to have complete control of all developments and to manage independently and with order every release and every package developed without loss of data or misalignments.

We use it for our software development team. Team size is 8. It is being used as source control for .NET applications and as a continuous integration server. It is being used on site and also by our offshore partner developer team in Mexico. It helps us track versioning and collaborate with the peace of mind that we control the code.

We used TFS in conjunction with a SharePoint upgrade to roll out Agile/Scrum. The key thing was traceability between MS products (linking). There were multiple project teams and a scrum of scrums was used. Adoption rate was decent, but it was tough to cut the cord on share folders.

Team Foundation Server (TFS) is used by the development and test teams at Peppermint Technology. It is used for management of our source code and we also take advantage of the automated build functionality. We also use it for storing all of our release user stories, tracking enhancements and bugs as well as taking advantage of the project management tools to support our agile development process.

We use Team Foundation Server as a hub for our in-house software development. It allows the development team to centralise software issues, feature requests and testing.

We are using TFS in our software division as a source control for code and DB objects. It allows us most importantly to keep a history of our code. Secondly, we can do deploys from this environment out to our many environments.

We use Team Foundation Server (TFS) to track the development and delivery of tools we implement across business units.

We use team foundation server for source control.

Team Foundation Server (TFS) is used as an Application Management Lifecycle suite by PMO, Software Development, and Information Technology. TFS ensures that software initiatives drive overall business value.

We use it across the organization. We use TFS to manage projects beginning with the Business recording requirements, rating them by Priority and approving. IT utilizes TFS for managing Projects, versioning of code, Management of Test scripts. Utilizing the tool allows us full traceability.

Team Foundation Server (TFS) is being utilized by many different departments within our organization. We personally use it to track tasks, user stories, bugs, releases, and test cases. Developers associate specific check-ins with bugs/user stories within TFS which, when pushed to our staging environments, are then assigned to QA/UAT for review. User stories and bugs are tracked as release scope for regular releases. The ability to associate releases/user stories/bugs in many different scenarios is priceless. It allows us to create different metrics/queries to measure success and potential failure, as well as to analyze what went well or what went wrong. TFS can be confusing for those new to the field or those who are older and used to other programs, but once the learning curve is achieved, the user tends to take well to the program.

Team Foundation Server was being used as the central repository for all organization application assets (Requirements, Code, and Test Suites). Each application is used by different users depending on job title and role but only within the IT departments. It addresses the issue of having multiple repositories for each kind of asset needed to develop projects and applications. The organization can now link together requirements to code pieces, stored queries to code, and test cases to code and requirements to makes sure all pieces of the project have been fulfilled before go-live.

Team Foundation Server (TFS) is being used for source control and ream project, task, bug etc., tracking.

Team Foundation Server (TFS) is being used by one of our departments. It's used for source code management and testing.

Team Foundation Server is used by our company as the primary tool for managing our software development process and managing our software code. We use an Agile Scrum process for our development and take advantage of the Team Foundation Server Agile work flow template. We do very few customizations to the template for ease of use and to keep maintenance and administration to a minimum. We use the Backlog and Board every day in our standup meetings. Our team has members in the US and abroad and Team Foundation Server helps keep everyone on the same page. We also use Team Foundation Server for our code repository. All of our source code and automated tests are stored in Team Foundation Server.

Team Foundation Server is used by the entire company across the globe. Development uses it for obvious reasons in developing new software and fixing bugs that are found and logged into Team Foundation Server by our quality assurance analysts. Support uses Team Foundation Server to log issues from clients and professional services uses it to make minor changes while in the field with clients. Sales uses it to demonstrate new features to clients and to set up environments when holding trade shows.