ADO is a great way to power your SCRUM process for .net application development
June 05, 2023
ADO is a great way to power your SCRUM process for .net application development
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Azure DevOps Services
We use ADO to manage our entire pipeline of work. Backlog items, tasks, and bugs, code repositories and pull requests, code reviews, pipeline management, releases and CI/CD, testing, deployment, and oversight. Overall, our whole process depends on the capabilities that DevOps brings to the table and wouldn't be the same, otherwise.
Pros
- Backlog management
- Build / Release management
- Code review and pull requests
Cons
- Tracing where security rules are coming from
- wiki management
- Mass-editing values (adding tasks, etc...)
- Backlog management
- Code repositories and PR review
- Pipelines
- Faster development
- Better control over team velocity
- Better visibility of work remaining
Jira is super clunky and doesn't behave in a modern fashion. monday.com is too flexible and doesn't provide enough feature set. AWS is the most competitive, but it's hard to wrap your brain around all of the features and offerings provided by amazon. ADO does a better job of making the 'main' elements visible...
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
Comments
Please log in to join the conversation