An example would be that now we have scheduled releases. We have scheduled builds that happen every Thursday that get rolled out to our development testers. In the past, before TFS, the developers themselves used to initiate that, and it was done randomly. So, being on a schedule is much better. 

It basically enforces our rules. Because everything is more controlled, source code cannot be checked in unless it builds correctly. It basically forces the developers to adapt to the agile methodology that we use, which is small chunks of work at a time. 

We work with life science companies, and they need traceability. Because we have the capability of being able to provide the traceability that they require, it helps us with laying out what they need for their validation efforts.

It doesn't improve the way our organization functions, but it supports the way we work. Instead of having separate Excel or other work item lists, we can just utilize the work items provided by TFS for record-keeping and monitoring the progress.

As I mentioned, it supports multiple code repositories. You can also build CI/CDs out of it. You can instruct TFS to build your .jar, .war, and .ear files and deploy them to to certain environments based on your configuration. So you don’t have explicitly maintain another code repository and CI/CD tools for your continuous integration/build purpose. This also automatically reduces DevOp burden and the number of people maintaining that DevOp work.

The solution gives us support for Agile processes, including usage of board and burndown charts. It provides us with an estimation process to move to formal and test coverage for more visibility and accountability.

It is a big improvement because before we were using PBCS.

TFS sits at the core of our entire software delivery strategy. Implemented and used properly, it provides a centralized place to store all source code and build information for the entire organization. We always know which version of the code is deployed to which environment and are always in a position to support the production code line. Custom automation surrounding TFS (via the API) has increased the number of code deployments we are able to perform 1000-fold in the past 5 years.

This product brings a lot of discipline and consistency in the way that our developers use their tools. 

Allowed project teams to communicate, collaborate and track tasks, stories, test cases, issues, and defects at a single location (using one tool).

It has improved a lot over the years with newer versions, Build is one such area which has been significantly simplified, making it very easy for the users to use than the previous XAML and pre TFS 2010 build infrastructure.

Also, the introduction of Release Management has made TFS a complete ALM tool.

The solution helps us store multiple software versions as it evolves and develops.

Better team collaboration and Issue tracking.

TFS was the first system of its type to be implemented in the organization, which helped in managing requirements and multiple teams effectively under a SAFe Agile environment.

TFS SCRUM adoption in our organization was very smooth.

Another very good feature of TFS is the build server. With it, I can quickly and easily generate binaries for testing and production environments.

Test automation capabilities enhanced the testing processes in the software delivery, which allowed us to create more quality software in a shorter time. The capability to deliver rapidly with ever changing technology demands could be easily supported with the work process enhancements we have done based on TFS's capabilities.

This really helps in planning our Regression and Functional tests as we create plan and test cases in it. It is easy for higher officials to get an overview of the testing part. Once the team is familiar with it, it’s really easy to work with.

We've reduced production deployment rollbacks 100%.

• We have set up a centralized TFS server.
• All the delivery projects are clients for this TFS.
• They are using it for code repository, ALMs, and for DevOps implementation.

We have set up a centralized TFS server.

All delivery projects are clients for this TFS.

They are using it for code-repository, ALM, and for DevOps implementation.

TFS increased productivity and reduced our times to market by 60%.

Any improvements would have come on the development side as the organization already had a more mature test management application.

Our organization used to use Excel sheets to control the projects. We didn't have any indicator, workflows or rastreability.

I can point to two basic improvements:

1. The project management. Before TFS, we used Microsoft Project and Excel to manage project tasks and release dates (only the Project Manager could do this). Since we adopted Scrum as a part of software development, we needed an agile tool to perform this task. TFS it is a great tool to manage Agile projects because the whole team is kept up to date with TFS burn down charts, release dates and so on, so we eliminated the need for Project.
2. We can use TFS to perform Continuous Integration, making build operations each night. This increases quality process and prevents code regressions.

TFS replaced a number of separate source control, work item and build solutions that were stretched to their limits, since adopting TFS we have been able to scale the development department without any limits from our tooling.

TFS has aided our agile transformation by providing digital Kanban boards that have enabled teams to be more productive when working remotely from one another.

As i'm an Software Quality Engineer It's a helpful product because you can provide project analysis from scratch and create a requirements document for maintenance. Also, it creates a strong relation between developers and testers that allows communication between them through analysis, design, implementation and testing, tracking bugs, bugs report, sitting severity and priority and discuss each issue with developer acc. to requirement document.

The TFS is not just a source code repository, but a real and complete ALM solution. Among other things, we use it as a ticketing tool. It is a building mechanism, which is really polished and easy to use.

We implemented the scrum process in our company, and we used TFS as the main tool to manage that process.

We upgraded to TFS 2017, which has a lot of features for SCRUM process that can be managed from a web browser.

It helps us to manage our Scrum process, as well as continuous integration, but not much more than the previous product we used (JIRA).

We are able to manage the work more effectively. Everyone has a current status at any given point of time.

This product has allowed us to continually maintain our code repository.

With TFS online, now everything is in the cloud, it is tidy and easy to compare and restore, especially my unfinished work, where I use the shelving changes feature. It's very useful.

• It's easy to implement agile methodology, updated and uniform code on work spaces.
• Work items allows easier tracking for risks, bug and issues, and tasks.

We transitioned into an agile software development shop around 2010. Using TFS allowed us to document our requirements as Features and User Stories on a Product Backlog, which allows all team members to access them at the same time. They can see updates and changes to them in real-time. It also supports our iteration-based development approach effectively, by allowing us to group features, and user stories into iterations, as well as forecast upcoming user stories into future iterations.

• Reduced cost of software implementation and testing processes by automation
• Streamlined the software development process so that we could deliver high quality software in short time to the market

We have had to recall a prior “production-ready” version to provide as a temporary solution.

• Agile project management
• Enterprise level development
• Testing of large enterprise applications

The current dashboard has limited report charts, We need more in reporting as charts are not enough to represent project full stat.

Addition to that, configuring reporting service require a SQL report server, which is anextra cost and need allot of effort to build

It has made the management of test artifacts more effective, thus leading to the improvement in the quality of our products from a testing/quality perspective.

When we applied the CMMI standards in our SDLC we used TFS to force some policies to control the project documentation and source controlling, and to manage the relationship between concerned parties.

I have spent less time merging code from developers.

Being able to easily create new bugs during the execution of a testcase in MS Test, then resume testing is a time-saving feature.

This solution enables us to link all items usefully, in the way we use Agile.

TFS has allowed our development team to function better as a group, by keeping code organized, and making it easier to prevent people from stepping on each other's code.

It brings in collaboration between our teams.

It has sped up the build and deployment process. We can now deploy the same application version to each environment in a repeatable and automated fashion.

It helps with the structure of the tickets. It can be modified and configured for different flows.

Developers are able to download code at any point in time. Helped in DevOps responsibilities.

We have streamlined the Scrum process with TFS and the product maturity has increased a lot. The agility features which will help us to understand the project maturity and help us to grow with incremental model for every sprint.

1. Cross platform support is great.
2. Developing build definitions from within a web browser is fantastic.
3. Installing build agents from a command line makes maintenance easier to manage.

RBAC management is too complicated for SCM and IT to manage, Windows Explorer integration of Power Tools is not reliable, Workspace synchronization is not reliable, does not support keyword expansion, does not support offline history and cannot even determine the current workspace version without being connected to TFS server, shelf sets cannot be versioned, shelf sets cannot be merged, and merges do not carry associated work items.  These are just the issues with version control.