Azure DevOps Services vs. Micro Focus Agile Manager (Discontinued)

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Azure DevOps Services
Score 7.8 out of 10
N/A
Azure DevOps (formerly VSTS, Microsoft Visual Studio Team System) is an agile development product that is an extension of the Microsoft Visual Studio architecture. Azure DevOps includes software development, collaboration, and reporting capabilities.
$2
per GB (first 2GB free)
Micro Focus Agile Manager (Discontinued)
Score 3.2 out of 10
N/A
Micro Focus Agile Manager is an application lifecycle management option acquired by Micro Focus from Hewlett-Packard Enterprise. It has reached End of Life. Users are encouraged to migrate to Micro Focus ALM Octane.N/A
Pricing
Azure DevOps ServicesMicro Focus Agile Manager (Discontinued)
Editions & Modules
Azure Artifacts
$2
per GB (first 2GB free)
Basic Plan
$6
per user per month (first 5 users free)
Azure Pipelines - Self-Hosted
$15
per extra parallel job (1 free parallel job with unlimited minutes)
Azure Pipelines - Microsoft Hosted
$40
per parallel job (1,800 minutes free with 1 free parallel job)
Basic + Test Plan
$52
per user per month
No answers on this topic
Offerings
Pricing Offerings
Azure DevOps ServicesMicro Focus Agile Manager (Discontinued)
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Azure DevOps ServicesMicro Focus Agile Manager (Discontinued)
User Ratings
Azure DevOps ServicesMicro Focus Agile Manager (Discontinued)
Likelihood to Recommend
8.1
(0 ratings)
7.0
(0 ratings)
Likelihood to Renew
10.0
(0 ratings)
-
(0 ratings)
Usability
6.6
(0 ratings)
-
(0 ratings)
Support Rating
8.1
(0 ratings)
-
(0 ratings)
Implementation Rating
10.0
(0 ratings)
-
(0 ratings)
User Testimonials
Azure DevOps ServicesMicro Focus Agile Manager (Discontinued)
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.
Read full review
One scenario I believe HP Agile Manager is well suited is for a team of 5 or more developers who are releasing new features or addressing defects. Another scenario where it is beneficial is for teams of QA Automation engineers, where again, the objectives are clear. A scenario where I believe it would be less appropriate is for operations-type teams where objectives are not always clear cut, and the roles must be more reactive.
Read full review
Pros
  • Flexible Requirements Hierarchy Management: AZDO makes it easy to track items such as features or epics as a flat list, or as a hierarchy in which you can track the parent-child relationship.
  • Fast Data Entry: AZDO was designed to facilitate quick data entry to capture work items quickly, while still enabling detailed capture of acceptance criteria and item properties.
  • Excel Integration: AZDO stands out for its integration with MS Excel, which enables quick updates for bulk items.
Read full review
  • Agile manager is particularly good for planning out sprints in an Agile methodology
  • The Task Board in AGM gives clear swim-lanes to indicate progress/status, or to gauge that of another team member.
  • The Dash Board gives visibility to team members capacity and the overall team burn down.
Read full review
Cons
  • Need to make the changes so that it doesn't occupy most of the CPU utilization and memory
  • Execution of Bulky SQl Queries leads to either the SQl being out of exception or the VS being unresponsive
  • Integration with Microsoft products is easy, but with non-Microsoft products it is more difficult, and you have to make a lot of configuration changes to integrate
  • With every upgrade of the Visual Studio, like from VS 2010 to VS 2013 , we need to upgrade our hardware/machine, as the VS hardware requirement also increases
  • If code is getting compiled in one visual studio, like in VS 2010, that the same code could possibly give an error when compiled in VS 2013, due to certain changes in keyword, data format, etc., with the VS upgrade
Read full review
  • Removing stories from a Sprint results in them being difficult to find later.
  • Editing story details is slightly cumbersome.
  • It's somewhat unclear how capacity fills up for stories split from prior sprints.
Read full review
Likelihood to Renew
I don't think our organization will stray from using VSTS/TFS as we are now looking to upgrade to the 2012 version. Since our business is software development and we want to meet the requirements of CMMI to deliver consistent and high quality software, this SDLC management tool is here to stay. In addition, our company uses a lot of Microsoft products, such as Office 365, Asp.net, etc, and since VSTS/TFS has proved itself invaluable to our own processes and is within the Microsoft family of products, we will continue to use VSTS/TFS for a long, long time.
Read full review
No answers on this topic
Usability
Azure DevOps is a powerful, complex cloud application. As such there are a number of things it does great and something where there is room for improvement. One of those areas would be in usability. In my opinion it relies too much on search. There is no easy way to view all projects or to group them in a logical way. You need to search for everything.
Read full review
No answers on this topic
Support Rating
When we've had issues, both Microsoft support and the user community have been very responsive. DevOps has an active developer community and frankly, you can find most of your questions already asked and answered there. Microsoft also does a better job than most software vendors I've worked with creating detailed and frequently updated documentation.
Read full review
No answers on this topic
Implementation Rating
Was not part of the process.
Read full review
No answers on this topic
Alternatives Considered
Jira is fantastic for project management and customer facing portal. It is not good for pure development (no integration with Git, pipeline management, automated testing features). If DevOps were to integrate and adopt the project features of Jira as well as the customer facing interfaces, I feel it would be a complete project management system.
Read full review
HP Agile Manager is beefy enough to work for bigger teams. In this way it matches closely to what is offered with Rally. One area it comes up short when compared to Rally is the apparent lack of a test management capability, where requirements can be entered then mapped to test cases. Agile Manager has some of the agile feel offered by Trello and Waffle but the added functionality that makes it more valuable for bigger teams.
Read full review
Return on Investment
  • Increased dev team efficiency through more streamlined development processes and task automation.
  • Improved quality of software deployments due to better source control, automated testing, and release management options available in DevOps.
  • Better collaboration between the dev team, business analysts, and agile project managers.
Read full review
  • It has allowed us to plan our Sprint work more effectively
  • It has made it more clear how to accurately estimate certain problems
  • It has given clarity over time as to the skill and work speed of team members
Read full review
ScreenShots