Overview
Product Information on Azure DevOps
What is Azure DevOps?
Azure DevOps Pricing
Overall experience with Azure DevOps
“Integrated Azure DevOps Workflow Connects Boards, Repos, and Test Plans Seamlessly”
“Azure DevOps Offers Strong Features but Suffers From Inconsistent UI and API”
About Company
Company Description
Microsoft enables digital transformation for the era of an intelligent cloud and an intelligent edge. Its mission is to empower every person and every organization on the planet to achieve more. Microsoft is dedicated to advancing human and organizational achievement. Microsoft Security helps protect people and data against cyberthreats to give peace of mind.
Company Details
Do You Manage Peer Insights at Microsoft?
Access Vendor Portal to update and manage your profile.
Key Insights
A Snapshot of What Matters - Based on Validated User Reviews
Top Azure DevOps Alternatives
Peer Discussions
What Your Peers Are Saying About Azure DevOps
Azure DevOps Reviews and Ratings
- Software Engineer50M-1B USDSoftwareReview Source
Integrated Azure DevOps Workflow Connects Boards, Repos, and Test Plans Seamlessly
Honestly, having everything under one roof in Azure DevOps has been a massive change for our team. Managed to get all our dev and test code into Azure DevOps Git repos and it just makes version control so much smoother since it is all linked. We use the Sprint Boards daily to track our progress from the dev side over to the test side and it is great because I can see exactly which user story a bug belongs to without jumping between tools. Managing the PBIs and features in the same place where we write our test plans just makes the lifecycle feel very connected. The way Azure Test Plans and Pipelines talk to each other is easily the best part for me. Since our test plans are right there, we can trigger our pipelines and see the results update our test suites automatically. It is so much better than the old way of manually updating the spread sheets or the test cases or trying to sync up different platforms. I can create a bug directly from a failed test run in the pipeline and it automatically links the logs and the specific PBI we were testing. It gives our team a single source of truth which has really helped with our sprint planning and making sure we don't miss any edge cases. It's also not perfect all the time because when you have so much data in one place the interface can get a little overwhelming. Sometimes, it feels like there is a big of a lag when I am trying to load a large backlog or a complex test plan with hundreds of cases. Also, permission management is still a bit of a headache, just like it was with the agents, because there are so many levels of access across boards and repos. But overall, I would never go back to using separate tools for everything. Having the requirements and the test code in one place just makes us way more efficient, especially when we’re trying to hit those tight sprint deadlines.



