Likelihood to Recommend Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
Read full review For an organisation that has completely adopted SAFe structure including naming terminology, it is less appropriate and apart from that. It can suit any organisation out there, and it can solve all your problems one way or another by customising it. It is a robust and highly scalable solution to support all the business needs. It improves a lot of productivity and visibility.
Read full review Pros Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project. Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts. Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing. Read full review If you have a mix of automation & manual test suites, HPALM is the best tool to manage that. It definitely integrates very well with HP automation tools like HP Unified Functional Testing and HP LoadRunner. Automated Suites can be executed, reports can be maintained automatically. It also classifies which test suites are manual & which are automated & managers can see the progress happening in moving from manual to automated suites. In HPA ALM all the functional test suites, performance test suites, security suites can be defined, managed & tracked in one place. It is a wonderful tool for test management. Whether you want to create test cases, or import it, from execution to snapshot capturing, it supports all activities very well. The linking of defects to test runs is excellent. Any changes in mandatory fields or status of the defect triggers an e-mail and sent automatically to the user that the defect is assigned to. It also supports devops implementation by interacting with development tool sets such as Jenkins & GIT. It also bring in team collaboration by supporting collaboration tools like Slack and Hubot. This tool can integrate to any environment, any source control management tool bringing in changes and creates that trace-ability and links between source control changes to requirements to tests across the sdlc life-cycle. Read full review Cons Can add more build templates for specific technology requirements Can have more features in dashboards which can help dev teams stream line their tasks and priorities Can have raise alarm feature in case of any sort of failure in devops pipeline execution Read full review The requirements module is not as user friendly as other applications, such as Blue Bird. Managing requirements is usually done in another tool. However, having the requirements in ALM is important to ensure traceability to tests and defects. Reporting across multiple ALM repositories is not supported within the tool. Only graphs are included within ALM functionality. Due to size considerations, one or two projects is not a good solution. Alternatively, we have started leveraging the template functionality within ALM and are integrating with a third party reporting tool to work around this issue. NET (not Octane) requires a package for deployment to machines without administrative rights. Every time there is a change, a new package must be created, which increases the time to deploy. It also forces us to wait until multiple patches have been provided before updating production. Read full review Likelihood to Renew Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Read full review I like the ease to use and its reliable.
Read full review Usability Azure DevOps Server or TFS is a complete suite in itself. From Developer's machine where the code is developed to the production environment where the code is meant to run it take care of complete flow within itself. It acts as a code repository you can check-in check-out codes using GIT interface. It also acts as a Build and Automation Test tool which can help you to judge sanctity of your code. It further acts as a release manager to deploy your application to the production environment. And all these steps can also be performed without any manual intervention with the option to have approval processes. Hence its a perfect blend of all set of tools and capabilities required to bring code to production.
Read full review Because it lets me track the test cases with detailed scenarios and is clearly separated in folders. Also the defect filter helps me filter only the ones that have been assigned to a particular area of interest. The availability of reports lets me see the essentials fields which I might be missing the data on and helps me to work on these instead of having to go through everything.
Read full review Support Rating I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
Read full review It is a great tool, however, it got this rating because there is a lot of learning that takes a lot longer than other tools. There are no mobile versions of ALM even with just a project summary view. I believe ALM is well capable of integration with other analytics tools that can help business solutions prediction based on current and past project data. This is Data held in ALM but with no other use apart from human reading and project progress. ALM looks like a steady platform that I believe can handle more dynamic functionality. You could add an internal communication platform that is not a third party. Limit that communication tool to specific project members.
Read full review Implementation Rating Do research beforehand and, if possible, do a trial run before implementing into production environment.
Read full review Alternatives Considered In my opinion, DevOps covers the development process end to end way better than
Jira or
GitHub . Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. The productivity increase we realized with DevOps is worth real money!
Read full review We have other tools in our organization like Atlassian JIRA and Microsoft Team Foundation Server, which are very capable tools but very narrow in their approach and feature set and does not come even close to the some of the core capabilities of HP ALM. HP ALM is the "System of Record" in our organization. It gives visibility for an artifact throughout the delivery chain, which cut downs unnecessary bottlenecks and noise during releases.
Read full review Return on Investment It has streamlined the pipeline and project management for our agile effort. It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise. The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization. Read full review ALM/QC has allowed for quick, traceable turnaround on relatively simple tasks ALM/QC allows us to achieve our business objective of always being able to refer to a documented ticket for work being done. ALM/QC navigation is not the easiest, so this aspect of the product has caused great frustration among new users. Read full review ScreenShots