<a href='https://www.trustradius.com/static/about-trustradius-scoring#question3' target='_blank' rel='nofollow noopener noreferrer'>Customer Verified: Read more.</a>
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>Score 8.8 out of 100
Based on 270 reviews and ratings
Likelihood to Recommend
Before using Azure DevOps, the department was calculating metrics by hand. It was a very tedious process that, at times required duplicate effort. Once we added the online boards, we were able to let the cards automatically calculate dates and provide us with team metrics instantly. It is also great for being able to easily move features from one team to another. Before we added all teams in the same project, it would require us to re-enter the features. We move features around a lot so that has been a big help. I also like the board customization, not all of our teams follow the exact same Agile flow, so allowing each board to have its own columns, states, and notifications give flexibility to each team.
- Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
- Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
- Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Manager in MarketingElectrical/Electronic Manufacturing Company, 5001-10,000 employees
- Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
- Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
- Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
- With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
- If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Likelihood to Renew
Azure DevOps 10.0
Based on 3 answers
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Azure DevOps 8.9
Based on 4 answers
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Azure DevOps 8.9
Based on 9 answers
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Professional in Information TechnologyArchitecture & Planning Company, 1001-5000 employees
Azure DevOps 10.0
Based on 1 answer
Was not part of the process.
Analyst in Research & DevelopmentHospital & Health Care Company, 10,001+ employees
VSTS is great if you final source system is Microsoft based. Everything work well together and once you learned how use VSTS it isn't difficult to build more build systems. If your staff are used to the methods Microsoft uses, their time learning VSTS won't be as difficult as staff that do not know the Microsoft way of doing things. If, however, you are going to build non-Microsoft bases applications, such as Java, Ruby or even Python, Jenkins is probably a better choice.
Return on Investment
- Via acquisition, we had some Atlassian tools including Jira, bitbucket, and confluence licenses. Total cost for 25 users was close to $5000. Migrating the team to VSTS would net savings of close to $2500.
- If you're running TFS, you can save costs on: server licenses (you'll have at least 2 - one TFS, one build server). Save time on maintenance and upgrades of TFS.
Premium Consulting/Integration Services—
Entry-level set up fee?