We use Azure DevOps for the entire lifecycle of software development, starting with requirements analysis. After that, we use it to continue the process of development and deployment.
Product Owner at Day Insurance
The software covers the whole development cycle, from requirements analysis to deployment
Pros and Cons
- "Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace."
- "Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it."
What is our primary use case?
What is most valuable?
Azure DevOps is user-friendly. The UI and the UX are perfect. Their software covers the whole development cycle, from requirements analysis to deployment. In particular, it's helpful in the requirements analysis phase. You can apply your methodology or Agile framework from the beginning. After choosing the framework, like Agile or Scrum, Azure DevOps provides many features, like user stories, tasks, managing boards, and those kinds of things.
Azure DevOps is complete and meets all of your expectations. You can develop your own plugins to customize it however you want, so it's highly flexible. We develop personalized plugins or use ones that other programmers create for the Azure Marketplace.
This makes up for any possible deficiency in Azure DevOps features. If you want some capability that Azure DevOps doesn't provide, you can develop your plugin or customize any part of it. The options for customization make it worthwhile for any software development.
What needs improvement?
Microsoft could focus on refining the reporting and dashboard elements of Azure DevOps to improve it.
For how long have I used the solution?
I've been working with DevOps for about five years.
Buyer's Guide
Microsoft Azure DevOps
December 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
DevOps is totally stable. And if there are any problems, Microsoft patches them as soon as possible.
What do I think about the scalability of the solution?
When you enter into Microsoft ecosystem, you can scale any part of the product in this ecosystem. For example, you can connect Azure DevOps to Microsoft SharePoint for knowledge or document management. You can connect Azure DevOps to OneDrive for storage. You can connect it with Skype for chatting or Outlook.
How are customer service and support?
We don't use support from Microsoft. We mostly solve problems by searching for solutions on sites like GitHub and that kind of thing.
Which solution did I use previously and why did I switch?
I've used Atlassian products like Jira, Confluence, and HipChat, but I prefer Azure DevOps and the Microsoft ecosystem.
How was the initial setup?
It is effortless to set up DevOps. All Microsoft products are user-friendly and easy to install. If you run into any obstacles, you can use Microsoft library or MSDN for any further help that you need. Microsoft provides a lot of wizards that you can use to solve your problem.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Founder at Premium Consulting SAS
Can control the whole cycle, has good documentation, and is stable
Pros and Cons
- "The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS."
- "The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project."
How has it helped my organization?
We are a team of 12 consultants specializing in this solution. We have customers with approximately 200 users each, and we have been able to reduce our customers' deployment time by using Azure DevOps or TFS.
Additionally, our customers have been able to measure and improve their development process, by generating some KPI's as 'average defect fixing time', 'effort deviation', and 'velocity' among others, due to the continuous use of Azure DevOps.
What is most valuable?
The integration of the whole cycle is the main strength of the tool. If I want to control the cycle with other tools on the market, I would have to use several tools. However, this is not the case with Azure DevOps or TFS.
What needs improvement?
The ability to extend work items was more flexible than it is now. Talking version control, one of our customers had some issues because they found it very difficult to manage more than 1000 repositories for one team project.
Additionally, I would like to see more powerful dashboards that could be used instead of Power BI. Azure DevOps or TFS does not support graphics from hierarchy queries. It would be powerful to have because some customers don't have Power BI licenses.
For how long have I used the solution?
We have been working with Azure DevOps or TFS for the past 11 years.
What do I think about the stability of the solution?
It is totally stable.
How are customer service and support?
The documentation is good and thus, we have not had to contact technical support very often. However, when we have escalated an issue to technical support, they have been good.
How was the initial setup?
The initial setup can be straightforward if the consultant is knowledgeable.
What's my experience with pricing, setup cost, and licensing?
The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools.
What other advice do I have?
Azure DevOps or TFS is a very good tool for development teams. It's easy to use. However, you would need the help of a consultant who has a lot of experience with the tool. This is because the tool let's you do things in many ways, but not all of them will be the right way to do it. It would be better to invest in the services of an experienced consultant.
Overall, I would rate TFS or Azure DevOps at nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Microsoft Azure DevOps
December 2024
Learn what your peers think about Microsoft Azure DevOps. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
Agile Coach at a pharma/biotech company with 10,001+ employees
Good visualization, and transparency, but the price could be reduced
Pros and Cons
- "The most valuable feature of this solution is that it saves time."
- "Being more technology-agnostic through ease of integration would be beneficial."
What is our primary use case?
We use Microsoft Azure DevOps for CICD, and to organize it in order to visualize the ongoing work.
What is most valuable?
It allows you to save time while also providing a governance visualization of ongoing activities and transparency.
The most valuable feature of this solution is that it saves time.
What needs improvement?
The price could be reduced. It is expensive, especially when it comes to infrastructure.
The integration could be better. Being more technology-agnostic through ease of integration would be beneficial. Once you start working for Microsoft, you are frequently tied to Microsoft.
For how long have I used the solution?
I have been using Microsoft Azure DevOps for the last ten years.
What do I think about the stability of the solution?
Microsoft Azure DevOps is a stable solution.
What do I think about the scalability of the solution?
Microsoft Azure DevOps is scalable.
How are customer service and support?
I would say the technical support is fine, but I have not had any trouble with the solution.
Which solution did I use previously and why did I switch?
I have some experience using Jira.
What's my experience with pricing, setup cost, and licensing?
It is very expensive in comparison to others.
As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users.
Which other solutions did I evaluate?
I have recently researched Jira, Microsoft DevOps, TFS, and Micro Focus.
What other advice do I have?
Mostly, because of the pricing, I would rate Microsoft Azure DevOps a seven out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
IT Project Manager at a energy/utilities company with 10,001+ employees
Integrates well with other tools, and enables us to perform different functions within one tool
Pros and Cons
- "I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
- "The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all."
What is our primary use case?
It is used to manage our projects. We basically maintain what would be the equivalent of our project schedules for various projects. So, we capture or create user stories to identify elements that need to be accomplished for the delivery of a project and to track who is responsible for it and the level of effort. We aggregate that within the tool and report out to leadership about the status of when we anticipate completion.
We are using its latest version.
How has it helped my organization?
Its integration with different functions has been very helpful. Previously, we had Microsoft Project schedules, and we did our reporting by using Excel and PowerPoint presentations. We also did testing tracking in other tools, such as HP ALM. Our source code was on Teams Foundation Server. All that can now be done within DevOps, which is a huge benefit. Things that we used to do in different tools can now be done in one tool.
What is most valuable?
I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities.
I also like the integration with the other toolsets, such as Outlook and GitHub. You can do your testing and check your source code within the same tool. That's definitely something really good.
What needs improvement?
The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all.
One thing we had to customize ourselves was to create the critical path. You can't do your project dependencies within the tool. We tried using the tool for a Waterfall project, and we had to find a custom approach to do that because. There should be some functionality for the reporting and dependency tracking for the Waterfall projects.
For how long have I used the solution?
I have been working with this solution for two to three years.
What do I think about the stability of the solution?
So far, so good. It has definitely been sized appropriately for our use. We haven't had any issues with it.
What do I think about the scalability of the solution?
We've only been using it for about three years, and so far, it seems to be able to adapt to our growth. We're maturing into it. We're moving in the direction of using it more, and I feel confident that it'll scale appropriately.
We have at least a hundred people using the tool. There are different degrees of people who are using it. Some people are using it in the read mode or view mode to keep themselves informed of where things are. We have some project managers who actually use the tool, and then we have a couple of administrators. I'm one of the administrators for our program. I have a couple of vendor or partner folks who are also administrators. We also have a development team that does some customizations on the dashboard and the Power BI reports that we do. These are pretty much different roles or layers that we have.
We do grant developers access to be able to make their own updates within the tool. Typically, project managers or scrum masters do that, but we also have some team members who are on these projects and have enough understanding of how the tool works and how we're using it. They are able to do their own reporting and their own updates on their statuses.
In terms of plans to increase its usage, we're moving in that direction. Most of our projects are done in Microsoft waterfall project management schedules, but we are being encouraged to move over to more of an Agile approach on our project methodology. Our mandate is that if you're going to do anything Agile, use the DevOps tool.
How are customer service and technical support?
I have not interacted with them. We have a sort of layer for support. I have had to reach out to one of the three resources that we have. He is our true admin at the company who had to reach out to their support, but it has been seldom, at least from my experience.
Which solution did I use previously and why did I switch?
I used Jira while working with a vendor that we had here for one of our projects. They brought that tool from their practice. We were doing that because we had not yet moved to DevOps. After they rolled it out at the organization level, the mandate was to stop using Jira and switch over to Azure DevOps. There are a lot of benefits to Azure DevOps over Jira, but Jira is the one that has a lot of market share on that side.
How was the initial setup?
I wasn't involved in that, but I do know that, just like many tools, there is a learning curve that was associated with that. I have used Jira before, so I had more or less an understanding because it is very similar to Jira, but I know that for other people I work with, it was a completely new concept to use something like this.
For its maintenance, we have a small team. We have about three individuals who do the backend support. So, it is minimal. Obviously, if they have any escalations, then they do go to Microsoft, but we haven't had that happen. It was very minimal. There are plugins that are available to enhance kind of some capabilities of the tool. When we ask for that type of functionality, these three individuals have been able to implement plugins for us.
What other advice do I have?
It is an Agile tool. We were using the tool calling that we were Agile, but we were really doing things in the Waterfall methodology. It was our square peg in the round hole, and that's where I realized that we didn't have the capabilities in DevOps to use it as a Waterfall tool, which makes sense because Agile is a different approach. We've evolved since then, and now, we're doing a bit more Agile when we use the tool. So, a tool is just a tool. There has to be that thinking alignment. Otherwise, it is a square peg in a round hole, and it doesn't quite fit. Your organization and your team have to understand that. Just using the tool doesn't make you agile.
The only problem we had was when we rolled this out, we didn't realize how Waterfall we really were. So, I had to go back and have PMs create additional data elements for us to capture what we really wanted to capture to report in Waterfall. Dependencies weren't tracked, and we had to go back. It almost felt like we had to do rework, and people weren't too happy about that.
I haven't used its mobile device capabilities, but that's definitely something that I would hope to evaluate in the future.
I would rate Microsoft Azure DevOps an eight out of 10. Overall, I'm pleased with the tool, but there is definitely some room for improvement.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior .NET Engineer at Advance Storage Products
Helpful in tracking issues and works extremely well in terms of the build time, but it is complicated and should provide the ability to write your own scripts
Pros and Cons
- "The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason."
- "They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server. I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script."
What is our primary use case?
We are using it for the source-code repository, automated bill process, very limited automated testing, and tracking trouble tickets or feature requests. We are using its latest version.
What is most valuable?
The automated bill feature is most valuable. As with most software developers, I can build code on my machine, but if one of my coworkers can't build the same code on theirs, there are always issues in trying to track it down. The automated bill process makes it a lot easier to track down where the issues are and find out what bugs aren't being included for whatever reason.
What needs improvement?
They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server.
I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script.
For how long have I used the solution?
I have been using this solution for a total of four years.
What do I think about the stability of the solution?
From what we've used it for so far, I have not seen any problems.
What do I think about the scalability of the solution?
We're using perhaps 10% of what it is capable of doing. It is far more capable than what we are using right now. With further experimentation and training, I'll probably go from 10% utilization of its capabilities to about 50% or 60% in the next couple of months. We'll never use 100% of what it is capable of doing, but it should handle 95% of everything we need to do. We can always write our own plugins to handle the side things that we need.
Scalability is not really applicable with the code that we write, but the build times and things like that typically take under 15 seconds before we get our responses back. So, it works extremely well.
In terms of the number of users, there are six of us who are software developers. Some of the managers might also partially use the reporting capabilities.
How are customer service and technical support?
I haven't called them up.
Which solution did I use previously and why did I switch?
I've used JIRA and a number of different systems going back almost 20 years. We were doing our development using Microsoft tools, and it just made sense to use what they integrate with. Azure DevOps is the perfect environment because we're using Microsoft technology for other stuff. It is always going to have slight favoritism towards the other Microsoft tools.
How was the initial setup?
The basic setup works very quickly, but there are so many things and options.
What about the implementation team?
We did it ourselves, which is one of the problems. We don't know what we're doing.
What's my experience with pricing, setup cost, and licensing?
I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees.
What other advice do I have?
It is a really complicated product. All DevOps stuff is complicated. The advice that I would give to anybody doing DevOps is to have a goal in mind of what you want to do. Then the product will do what you wanted it to do.
I would rate Microsoft Azure DevOps a four out of ten because I don't know it enough to rate it.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Digital Architecture Corporate Leader at Banco Pichincha
It integrates well with other tools in the software development process, like quality testing, documentation, and agile development.
Pros and Cons
- "Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development."
- "I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes."
What is our primary use case?
We have separate DevOps processes for different teams. We're implementing agile processes, so we have cells for each product, and each cell has its own DevOps process. This means we have a DevOps process in GitHub, GitLab, and another tool. We have lots of costs and can't share experience between teams.
The idea was to unify everything in one product to ensure that we standardize DevOps practices on the same tool to have better knowledge and expertise and focus on a specific tool.
How has it helped my organization?
We had a lack of governance over DevOps processes, so we had some quality issues in the end when we released the software products. DevOps has helped to resolve those issues.
What is most valuable?
Azure DevOps' collaborative features are good, and it integrates well with other tools in the software development process, like quality testing, documentation, and agile development.
What needs improvement?
I think Azure DevOps could improve the traceability or business intelligence about the execution of DevOps processes.
For how long have I used the solution?
I've been using DevOps for three years.
What do I think about the scalability of the solution?
Azure DevOps is scalable.
How was the initial setup?
We have good people with a lot of experience in DevOps, so it's not complex for us. The most significant difficulty in adopting the tool was changing our past processes to move to the standardization model we defined with Microsoft DevOps.
What's my experience with pricing, setup cost, and licensing?
We have a yearly agreement with Microsoft to cover the different companies.
What other advice do I have?
I rate Azure DevOps nine out of 10. I would give it a perfect 10 if Microsoft offered personalized support. Sometimes we call Microsoft with requests, and it would be nice to have personalized processes with our specialized services.
We have two different approaches for products. One is to support products that we provide our customers. The other is creating a digital transformation strategy for new products. We are using DevOps in the latest products, and in the future, we are going to grow with support for products we have produced in the digital transformation. This is part of our roadmap to implement DevOps in all the processes in every technological area of our companies.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Test Advisory, Management & Implementation at a energy/utilities company with 51-200 employees
A complete package with good stability and scalability
Pros and Cons
- "In Microsoft Azure DevOps, you have a one shop to get everything."
- "If they could build up requirement traceability metrics, then it would be great."
What is our primary use case?
The purpose is for development and testing from the vendor side. Our company works as a vendor, client, and implementation partner. The vendor provides the product, and we make sure that it's implemented correctly for the client. The vendor uses it for the development and tracking of the requirement and the test cases, executions, and building storage.
My access to these tools is very limited because the DevOps pipeline and DevOps is mainly used by the engineering team of development, but the QA is also part of it. Once those people are established, then we are the extended hands or extended part of that for usage. Once they have the stories and features, they start the test cases and link on it. From that point, we just take it forward and once they have a code pull, then we would pull it and build it and deploy it into some QA enrollment.
There are around 20 people using DevOps in my company.
What is most valuable?
The best tool would be Azure DevOps. There are other tools with AWS and Google, but since Microsoft has solutions for everything, it's easier because it's all their tools. We may be using different tools in order to achieve all those things because they may not have an operating system or a pipeline, so maybe we are using some of the bill tools. In order to achieve DevOps, you may be using a set of different tools and connecting it. In Microsoft Azure DevOps, you have a one shop to get everything.
What needs improvement?
There isn't a requirement traceability matrix format. In ALM, we have a centralized repository of all the requirements in one place. But in DevOps, it works like a product requirement. In ALM we have the centralized repository of requirements where you can go and see the requirement coverage and discovery and so forth. But in DevOps, it has stories and test cases. Once that project is over, nobody is going back into that requirement. It's a good tool for development activity, tracking and getting all those metrics. If they can build up a requirement traceability matrix, then it would be great.
What do I think about the stability of the solution?
I haven't seen any issues with stability.
What do I think about the scalability of the solution?
The scalability of DevOps is good.
How are customer service and support?
We haven't had any issues with technical support. Whatever issues we've had, they were solved.
How was the initial setup?
I didn't see any complexity in the setup because everything is from Microsoft. The development tools and operation tools are coming from one shop, Microsoft, so it's easy to connect, plug in, and establish all those things. For Google Cloud or AWS, it's different because they use different tools in order to achieve what Microsoft is trying to achieve. For example, the CI/CD Pipeline.
Even in ALM or in the DevOps tool, it's initially a one-time setup.
What's my experience with pricing, setup cost, and licensing?
I don't know the pricing of DevOps. It would be much cheaper than ALM because ALM came out as a software product initially. Now they are moving into a cloud and subscription model. In that case, Microsoft is coming from Azure and the cloud and DevOps and software as a service, so it would be much cheaper, but the catch would be that they are trying to get money on all sides, like an operating system, Microsoft Office, or Microsoft Azure DevOps.
The good part is that it's a complete package, but at the same time, once you've gone with them, you don't have much leverage to split out into some other activities because everything is interconnected and entwined by that time, and it would be like a monopoly. It won't be good if you try to split out at a later point in time because everything is connected—all our Microsoft products like operating systems, OfficeSuite, MS Teams, Azure DevOps, etc.
What other advice do I have?
I would rate this solution 9 out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CTO at Southernsoft Technologies
Intuitive and easy to use with good stability
Pros and Cons
- "The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user."
- "We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up."
What is our primary use case?
I primarily use the solution on projects often. We use it for our Git repository and the CI/CD.
What is most valuable?
I love how easy the solution is to use. It’s intuitive. I don’t need to reference a manual. Everything is just very naturally laid out.
You can link your tasks and assign people. To me, it just makes sense. The user experience is excellent.
I like the Kanban tasks and their various features. It’s all very straightforward.
The one thing that really stands out to me is how you can filter and how you can do your reporting and filter the tasks and everything by user. Every time I try to do that in Jira, for example, it's a pain.
The stability of the product is quite good.
What needs improvement?
I’m not sure what needs improvement. I don't even think I'm using everything. There are still a lot of things on the testing side that I'm not using. That said, there's, there's a lot that it can do. I wouldn't even know where to get started on discussing what it needs or lacks.
We did have some brief performance issues, however, that was due to putting everything on one epic instead of breaking a project up.
For how long have I used the solution?
I’ve been using the solution for about four years now. It’s been a while.
What do I think about the stability of the solution?
For the most part, the stability is very good. There was one time there was a bit of a performance issue, however, it was just due to the fact that the project manager was overwhelmed. It slowed down and got laggy. We put everything on one story, one epic, and we realized we needed to split it up.
What do I think about the scalability of the solution?
The product can scale. With the projects that I work on I just pick up Azure DevOps. It just makes sense. Everything from the beginning, for example, how the story starts right up to how it gets deployed and everything, is well laid out and you can adjust as needed.
On the project that I'm doing right now, maybe have a team of ten. On other projects, for example, at my previous company, we had a hundred devs or so using it.
How are customer service and support?
Technical support has been very good. We used to call Microsoft and they would help us. They gave great support. We’re quite happy with their responsiveness and level of knowledge.
Which solution did I use previously and why did I switch?
I also use Jira alongside Azure DevOps. I use both of them.
I find DevOps easier to use and better laid out. I find Jira difficult and confusing.
How was the initial setup?
The initial setup is pretty straightforward.
What's my experience with pricing, setup cost, and licensing?
I can’t speak to the exact pricing. It’s not an aspect of the product I deal with.
What other advice do I have?
We’re a customer and an end-user.
I’m a big fan of DevOps. It’s a good project and I haven’t seen anything else like it.
As we’re on the cloud deployment of the solution, we’re always on the latest version.
I’d advise new users, if they are a Microsoft shop, to choose DevOps over Jira. It just makes more sense.
I’d rate the solution at a ten out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Product Categories
Application Lifecycle Management (ALM) Suites Release Automation Enterprise Agile Planning ToolsPopular Comparisons
OpenText ALM / Quality Center
OpenText ALM Octane
Rally Software
Polarion ALM
Nutanix Cloud Manager (NCM)
Jira Align
Codebeamer
Jama Connect
PTC Integrity
Digital.ai Agility
IBM Engineering Rhapsody
Planview AgilePlace
Buyer's Guide
Download our free Microsoft Azure DevOps Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What Is The Biggest Difference Between JIRA And Microsoft Azure DevOps?
- Which is better - Jira or Microsoft Azure DevOps?
- Which is better - TFS or Azure DevOps?
- What is the biggest difference between Micro Focus ALM Octane and Microsoft Azure DevOps?
- Has anyone tried integrating Azure DevOps with HP ALM?
- MS Azure DevOps vs Jira for test planning and management - which one is the better solution?
- How does Microsoft Azure DevOps compare with GitLab?
- What are your use cases for Microsoft Azure DevOps?
- When evaluating Application Lifecycle Management suites, what aspects do you think are the most important to look for?
- Looking for suggestions - we need a test management and defect tracking tool which can be integrated with an automation tool.