Azure DevOps Services Reviews and Ratings

Use Cases and Deployment Scope

We use Azure DevOps to coordinate our implementation of development changes and technical processes (configurations / setups) for Business Central. First we create a master document listing all the modifications / extensions from a functional standpoint (master), then have individual tasks with tech design and hours assigned. Each time code with Git is sync'd and merged between one or more developers for the monolith extension app, it is tracked with the task assigned. Finally, as each task is worked through the status is updated and sync'd with the time keeping system (F&O) with PowerAutomate. This gives insight into the progress vs. hours consumed vs. original estimate in real time.

Likelihood to Recommend

DevOps is much more user friendly than Git itself. There is a more GUI-centric interface, tighter integration with the Azure / Entra architecture. For those of use in the Microsoft-sphere, it really is excellent for code-centric project management. I rate this as an 8 because it does not seem quite as well suited for fully functional / non-code project aspects in implementation. Nor does it have customer / end-user portal / front end for easy reporting and insight.

Use Cases and Deployment Scope

Azure DevOps Services for me is a one stop solution for managing my project work. With managing what i emphasize on if regular creation and maintenance of user stories on how and where is project headed to, bugs maintenance, team retrospective, source control management for codes and last but not the least continuous integration and deponent of my code to production

Likelihood to Recommend

It can be best suited for projects that jave extensive relying on Microsoft projects and it can seamlessly Integrate with Microsoft active directory.

Another work scenario suited best could be if the project is agile development, Azure DevOps Services gives a lot of tools and it's services that could proce efficient for agile projects such as boards, retrospectives etc.

Use Cases and Deployment Scope

We use Azure DevOps Services to track our digital project from starting to finish. We need a platform to track all the epics, features, user stories, defects and other relevant task for general agile practice. We also need the platform to be integrate with our repository and pipeline so that we could automate the deployment.

Likelihood to Recommend

It is suitable for organization looking to automate their software deployment and want a good integration for developer.

Not so well to track items from business' lens as the functionality is heavily IT driven.

Use Cases and Deployment Scope

We use Azure DevOps for all our digital projects. It helps with organizing features and work with the development team. We have an overview of the sprints and it helps knowing where we are and where we are going.

Likelihood to Recommend

It's really great for organizing digital projects.

I like that you have an historic of everything in the work items.

I think it is less appropriate for business analysis. A white board like Miro is best suited in these cases.

Use Cases and Deployment Scope

We are following SAFe practices by using Azure DevOps starting from PI planning to retrospective. We are using all features starting from Work items, Dashboards, Repo, CI/CD pipelines etc..

Likelihood to Recommend

For small enterprises to big, it applies to all for efficient and effective product management with full traceability in built.

Use Cases and Deployment Scope

The application has provided the most suitable agile tools for managing projects in the organization. It tracks closely the task development infrastructure to enhance best implementation practices. My team has been depending on this platform for the last one year and the results have come out with positive ROI. Azure DevOps Services helps each department in performance modelling.

Likelihood to Recommend

Our main projects have been developed under the excellent operations of this product. Deployment and testing of new applications has been great step ahead since we deployed this tool. Integration with other Azure services has been successful with top-notch results that have promoted faster production growth. It is easy to learn how this product operates even when you are fresher.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

ADO is well suited for the visibility of day-to-day tasks and responsibilities as well as things such as Features, user stories, etc. Off the top of my head, I can't think of any scenario where it might not be well suited, as you can customize ADO to your liking to a degree.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

Definitely great for developing .net applications and keeping track of a backlog in a SCRUM environment. I think managing a backlog and the associated schedule are also very strong.

I would think that managing an application with a non-microsoft environment would be less appropriate (ie: a node.js back-end application with a react front end, for instance...)

Use Cases and Deployment Scope

We use Azure DevOps as our continuous deployment solution. Essentially, anytime we merge code into staging or master, we use Azure DevOps to automatically build and deploy.

Likelihood to Recommend

Anytime you're deploying to Azure it's the way to go. It works great for CI/CD.

Use Cases and Deployment Scope

Earlier, we used the traditional whiteboard method to track our 2-week sprint activities, but now with Azure, we have so much evolved as it is a cloud service, and everyone can update their tasks on the board from anywhere. Azure Is used for Sprint planning, Test, and Defect management, As it offers a complete solution from task creation until defect closure.

Likelihood to Recommend

Azure DevOps was a one-stop solution for sprint planning, Test planning Pipeline integration as we have dev, test, and sandbox env and wanted to have the latest/clean code in all env. It was also helpful in creating dashboards showing daily progress by developing charts, burn-down graphs, defect tracking, and follow-ups.