ADO - an all encompassing tool.
June 06, 2023
ADO - an all encompassing tool.
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Azure DevOps Services
We use ADO for a wide range of things. We create work items in there, essentially being a unique number that we can associate with a project. We also use ADO to create features, user stories, acceptance criteria, and test cases in ADO. The linking system in ADO allows good visibility across these.
- The use of the scrum-like board, which can be customized to your liking.
- Excellent linking and visibility across items in ADO e.g. user stories, features, test cases, tasks, etc.
- Storing Test Cases.
- I did mention it has good visibility in terms of linking, but sometimes items do get lost, so if there was a better way to manage that, that would be great.
- The wiki is not the prettiest thing to look at, so it could have refinements there.
- It could improve the search slightly better.
- Generating work item numbers and assigning accountability.
- Storage of test cases.
- Easy to see linking between tasks, user stories, acceptance criteria etc.
- Has made it easier to manage resources and projects in general.
- Great visibility of what's going on with the work.
- Easy to learn how to use.
ADO has better linking than Confluence and is adaptable for a specific need, whereas Confluence might be a bit more rigid, but it's also sort of along the same lines as to what can be done with both tools. ADO also had an ease of use to it and can do a bunch of stuff with it, e.g., store test cases, create user stories, deployments, etc.
Do you think Azure DevOps Services delivers good value for the price?
Yes
Are you happy with Azure DevOps Services's feature set?
Yes
Did Azure DevOps Services live up to sales and marketing promises?
Yes
Did implementation of Azure DevOps Services go as expected?
Yes
Would you buy Azure DevOps Services again?
Yes