TFS is great for a Microsoft Shop
Overall Satisfaction with Team Foundation Server
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.
Pros
- Continuous integration when the team is using azure is really easy.
- It's fairly intuitive to use.
- Azure or IIS deployment is very easy.
Cons
- The project management/scrum piece is hard to learn.
- The Wikipedia functionality it provides isn't very useful for lack of features.
- It takes a REALLY long time to check in a large number of newly added files.
- If your file paths get too long, TFS gives you errors.
- New developers ramp up really quickly because TFS is so ubiquitous in the industry.
- Even if a new employee doesn't already know TFS, it's intuitive enough to learn without much ramp up.
- The integrated CI server functionality makes it so we can consolidate what would normally be multiple, on-prem products into one managed solution.
The JIRA integration with Bitbucket is a little nicer for sure, since they're both Atlassian products. Still, the Visual Studio and Azure integration with TFS made this a no-brainer for me.
Price-wise they are similar but you get a lot more with your TFS subscription. For the automated builds and deployment logic alone, it's worth it.
Price-wise they are similar but you get a lot more with your TFS subscription. For the automated builds and deployment logic alone, it's worth it.
Comments
Please log in to join the conversation