Comparing Team Foundation Server with Jira, Bamboo, and Subversion

Hey everyone,

I just sat through a demo of Team Foundation Server 2008, and it got me thinking about our current setup. We’re using Jira for project management, Subversion for version control, and we might be using Bamboo for continuous integration (I’m not 100% sure on that last one).

I’m curious to hear what you all think about these different tools. Do you prefer the all-in-one approach of TFS, or do you like having separate tools for different jobs? What are the pros and cons you’ve experienced?

I’d really appreciate hearing about your experiences, especially if you’ve used both TFS and the Jira/SVN combo. What works better for your team? Are there any specific features that make one stand out over the other?

Thanks in advance for your insights!

I’ve used both TFS and the Jira/SVN combo extensively, and each has its strengths. TFS shines in its tight integration within the Microsoft ecosystem. If your team heavily relies on Visual Studio and other Microsoft tools, TFS can streamline your workflow significantly. The all-in-one approach reduces context switching and simplifies user management.

However, the Jira/SVN/Bamboo stack offers more flexibility. Jira’s project management capabilities are top-notch, and its extensive marketplace allows for customization to fit specific needs. SVN’s branching model is simpler than Git, which some teams prefer. Bamboo’s CI/CD capabilities are robust, though the learning curve can be steep.

Ultimately, the choice depends on your team’s specific needs and existing toolchain. TFS works best for Microsoft-centric teams, while the Jira stack excels in diverse environments. Consider factors like scalability, cost, and required features when making your decision.

ive used both setups and honestly, it depends on ur team. TFS is great if ur all-in on Microsoft stuff, but jira/svn/bamboo gives more flexibility. jira’s project management is awesome, but bamboo can be a pain to set up. Consider ur existing tools and what features u really need. theres no one-size-fits-all answer here

I’ve worked with both setups, and there are definitely trade-offs to consider. In my experience, TFS excels at providing a unified environment, especially if you’re already heavily invested in the Microsoft ecosystem. The integration between version control, project management, and CI/CD is seamless, which can be a huge time-saver.

However, I’ve found that the Jira/SVN/Bamboo combo offers more flexibility and customization options. Jira’s project management capabilities are top-notch, and its extensive marketplace allows you to tailor it to your specific needs. SVN’s simplicity can be an advantage for teams that don’t need complex branching strategies.

One downside I’ve encountered with TFS is that it can feel limiting if you want to use tools outside the Microsoft ecosystem. The Jira stack, while requiring more initial setup, plays nicely with a wider range of technologies.

Ultimately, the choice depends on your team’s specific requirements, existing toolchain, and future scalability needs. Consider factors like learning curve, integration capabilities, and long-term costs when making your decision.