TFS Reviews

The scrum template to manage our development process, as well as the continuous build and release functionality.

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

Agile metrics/reporting (if you compare it to JIRA's functionality), as well as more/better customizable widgets to create richer dashboards.

I would really like to be able to see things such as cycle and lead times for issues, as well as be able to see the cumulative flow diagram on a dashboard.

We use the on-premise version of TFS, and I see that the cycle and lead time widgets are only available on the Team Services version.

I must admit that I don't like the fact that the on-premise versions are always behind the Team Services version. Do you maybe have an indication of when we can expect to have these widgets available in the on-premise version?

We have been using TFS 2017 for three weeks now. However, we have been on the previous versions (2013 & 2015) for three years.

No.

No.

We have had no need for any technical support so far. Should we require technical support, I don't know if it will be readily available in South Africa.

Yes, we used JIRA. Since we have to pay for Visual Studio, licenses for coding purposes (and these licenses included TFS) it did not make sense to continue paying for JIRA, even though I really liked the JIRA solution.

We got an external consultant to help us with the initial setup so it was pretty straight forward. Since then I was able to make all the required changes.

Pricing and licensing model is still quite complex, as are all of Microsoft's products.

We did not evaluate other options, but like I mentioned, we were using the Atlassian suite of products.

Make sure that you understand Microsoft's licensing model and that you select the process templates that are most suitable to you when setting up the product for the first time. Different process templates have different reports that you can view.

Reports for user stories statuses, hours logged, burn down charts, etc.

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

Help on the site should be improved.

A year and half.

Not as of now.

No.

Have not reached out to technical support.

We used HP QC, then we moved to TFS because of the client's affinity towards TFS.

Straightforward.

Pricing is better compared to other leading tools.

No.

This tool is good for agile projects, and it has all features which QC provides.

We use the source code repository technology of TFS, we have Git repository in TFS, and also, have TFVC.

Git was introduced starting from TFS 2013. This allowed our team the flexibility on the source control preference.

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

The product is mature. We use it as our primary on-premise source control for both Git and TFVC allowing the flexibility for different delivery team to use different source control that best suits them.

We have just recently upgraded to this version of TFS, but have been using Microsoft Team Foundation Server for the last six years.

If your plan on using on-premise, we would recommend you would resource your hardware/VM requirements appropriately to host Team Foundation Server.

There were no scalability issues.

The product is mature, as we’ve upgraded our on-premise Team Foundation we’ve never had to engage technical support, as the upgrade process was seamless barring some minor issues here and there.

There was no issue with the setup or upgrade path as both are well documented.

There is now cloud offering of the Team Foundation Server known as Team Foundation Services for smaller companies/individuals to use, starting out with the free version for five users. I would recommend people review their requirements based on the size and resources; review them with the different offering that is now available from Microsoft.

As the variant of this product was already in use, we followed the upgrade path as we are Microsoft Gold Partners.

Now, there is the cloud offering of Team Foundation Server which is known as Visual Studio Team Services which would suit those who do not want to maintain the on-premise version and is free for up to five users.

The version control itself (version history, branching and merging), shelving change and build server.

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.

I can't see any major improvements for now. Maybe the comparing tool is too simple, but I'm using an alternative, so I have no problem at all.

We've used it for five years, basically for source control. I used work items once for a very short time, so I can't consider it as "used".

No issues encountered.

No issues encountered.

No issues encountered.

I've not had to use it.

I had to use TFS because it was there in the companies where I worked, but I also used CVS and Git. I think that TFS is easier because it is already integrated with Visual Studio, if you are using Visual Studio.

I've never setup a TFS server.

if TFS was completely free (not limited to five members for online), I would suggest using it, but the price for extra members is too expensive in my opinion and is worth it only if you are using Visual Studio, otherwise other solutions can do basically the same (talking only about source control).

• Source control
• Work items
• Team build

• 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.

As of now, TFS delivers what we need on the project/business.

I've used it for seven years.

No issues encountered.

No issues encountered.

No issues encountered.

Customer Service:

I haven't needed their help yet.

Technical Support:

I haven't needed their help yet.

For source control, I've used SVN Tortoise before. TFS is more useful, organized and user-friendly.

Straightforward. Usually no issues being encountered when setting up.

We used a vendor team from Microsoft.

• Product backlog
• Work items (Features, User Stories, Bugs, 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.

I've been using it for five years.

No issues encountered.

No issues encountered.

No issues encountered.

Previously we primarily used a waterfall software development methodology, so our move to TFS coincided with a reorganization we went through into an agile shop.

From a project/requirements perspective, transitioning into TFS was fairly straightforward. Instead of creating requirements documents for upcoming projects, functionality was documented as Features and User Stories in TFS. There was a learning curve for the organization as a whole who didn’t have much agile experience to be able to document and read requirements as user stories.

• Agile project management
• Requirements management
• Team management
• Source code management
• Testing software
• Deployment and test automation

• 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

I've been using it for five to six years.

Sometimes, but Microsoft support was always awesome.

No issues encountered.

No issues encountered.

Customer Service:

It's superb.

Technical Support:

It's superb.

It is simple and well documented.

We did it in-house.

Just go for it. It is amazing.

TFS is a very Easy to use product,, Scalable and Configurable. It is very well integrated into a native development environment , with massive reporting services. TFS helps not only to manage R&D groups but to easily create , change and implement work processes rapidly. TFS provides end to end Application Life Cycle management capabilities ,

It is windows only product

We chose TFS because it was the native choice for .Net development. Although in the bank there are other ALM products (separated for bugs, demands, deployments), we insisted on using a complete one solution for our new development projects, and as for now, TFS is doing its way to become a mainstream product for .Net based develoment projects.