1. Home
  2. Application Lifecycle Management (ALM) Tools
  3. Micro Focus Agile Manager (Discontinued) Reviews
  4. User Review of Micro Focus Agile Manager (Discontinued)
Full Agile Management tool with lightweight feel
March 24, 2017

Full Agile Management tool with lightweight feel

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with HP Agile Manager

HP Agile Manager is being used in the entire IT department of the client I am currently a consultant for. Specifically in the QA Automation department, it is used to implement an Agile methodology with sprints. It allows us to plan out three week sprints with clear story objectives and capacities for each team member.
  • 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.
  • 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.
  • 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
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.
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.