105

HPE Agile Manager - license

Mfg. Part: M3E64AAE | CDW Part: 3863799 | UNSPSC: 43232402
Request Pricing
Close

Have leasing questions? Let us know how can we help.

Note: Leasing is available to organizations only. Leasing is not available to individuals.
800.808.4239
Mon-Fri 7am-7:30pm CT
Availability:
Ships same day if ordered before 4 PM CT
  • License
  • 1 concurrent user
  • hosted
  • electronic
View More
Product Overview
Main Features
  • License
  • 1 concurrent user
  • hosted
  • electronic
HP Agile Manager is a SaaS-based Agile management solution for organizing, planning and executing Agile projects. It is purpose-built and designed specifically to serve Agile teams. It leverages native cloud architecture for instant-on access, boasts a clean, intuitive design and offers technology innovations that remove latencies, bolster Agile practices and foster continuous improvement.

Technical Specifications
Specifications are provided by the manufacturer. Refer to the manufacturer for an explanation of the print speed and other ratings.
General
Category: Development tools
Hosted Service Type: SaaS
Installation Type: Hosted
Subcategory: Development tools - team tools

Header
Brand: HPE
Compatibility: PC
Manufacturer: HP Software
Packaged Quantity: 1
Product Line: HPE Agile Manager

Software
Distribution Media: Electronic
License Category: License
License Qty: 1 concurrent user
License Type: License

Product Reviews
Rated 3.5 out of 5 by 4reviewers.
Rated 4 out of 5 by One of the key features that we looked for when we were looking at Agile tools was the dashboard. Valuable Features:One of the key features that we looked for when we were looking at Agile tools was the dashboard - all of the metrics that you can get on-demand, pulling from ALM Quality Center. Test runs and all of that kind of stuff. Also the way the user stories can be in some kind of architecture, so themes, features, user stories, linking those from one to another to another, being able to link two different entities to one story card that might be dependent on another one being complete, you can link those two.With insurance software, there's always that sort of core capability you have to have done before you can start doing your extra writer work, extra coverages, that kind of stuff. Until you have that core base done, our backend system wouldn't be able to accept this policy if that wasn't there first, etc. We kind of manage the front-end work the same way.Improvements to My Organization:Before Agile Manager we had a tool that came with the development tool that we're using. It's a componentized development tool that we bought from a company and it was very much not developed, so there were two fields (name and description) and then you had a single drop down for the story card statuses, either, "to do, running, done." I understand why they were trying to keep it sort of lean with the Agile mindset, but working in insurance, and working across any given project, you might have six, seven, eight, or nine teams involved with different connection points.There's a lot of information that gets tracked, and you want to be able to capture that with comments, or tasks, to make sure everybody is doing their part. UX has their design done before it's handed over, wireframes have been signed up by the business, requirements are complete. Any business rules spreadsheets have been attached, so if there's any like state-specific tables that we have to deal with in this state it comes in a little bit different, and that state it's the normal flow.There's more information that we wanted to capture and we needed to capture to be able to do the stories effectively. We're wasting a lot of time on the old tool, capturing, putting out on a SharePoint site, running that down, going and talking to somebody else about, "Hey, did you guys see this part yet?" In Agile Manager you can capture that all on the story card.Room for Improvement:This one kind of caught us by surprise, and all our evaluations from it doing demos to the team that was going to be using it. The original version that we got, I'm not sure the version number, didn't have the story card print functionality. The project manager was a little overboard. She had said if she had done this, we would have picked a different tool. I think that's a little bit much.You can export all the stories to Excel. We created a little mail merge in Microsoft Office. We had a solution in 30 minutes on how to print story cards. That did kind of surprise me, something as simple as just printing story cards out of there. I believe it's in there now, but we have the on-prem version, so it's in the SaaS version, but the on-prem they're not going to do another build for that until I think version 2.0, or 3.0, the next major build. That was the one thing that surprised me a little bit that something as easy as a print feature would be not in an initial build.Deployment Issues:We use the CI tool that they recommended and it's one that isn't natively supported by ALM. I think they're looking at changing the CI tool that they're using. We were basically being consulted from Mandex, so they were just kind of going with everything that they were recommending. I think now we're getting a little bit more mature with their tool, so we're sort of customizing to what we need.Stability Issues:It's been stable for us.Scalability Issues:It's been really easy. First project we got 30 licenses. I think we're using about 24 to 26 of them. That team is basically rolling into the next project. Going to pretty much stay the same. Kind of take a few of the people to start another team, so we've got 30 more licenses, we're up to 60.Implementation Team:I think it was nearly flawless. There was a couple of server setup things that we needed help with. I was basically working off the requirements dock / setup dock from HP. Our server setup guy had a couple of questions that I think were answered. If I remember correctly, it might have actually been something with our firewall that was causing the issue. Which is funny that it's on-prem. I can't remember what the actual issue was. We set it up a little over a year ago. Other than that it was up and running within a week or so.Other Solutions Considered:We also looked at Mandex who I think are based in Sweden, and have an office in Boston. It's a componentized development tool using reusable widgets that you basically wire up and do some CSS styling stuff on. We didn't really evaluate a tool coming into this project and then we found out really quick that we needed something better than what they gave us. I think originally the project manager, the sponsor, whoever does the sort the setup for it thought it was going to just be good enough, we would be able to sort of use SharePoint how we always have on our waterfall projects.It was probably only four or five sprints in on a project that I think went about 25 sprints. We found that it just isn't going to work. We started evaluating two tools, actually at that point one was Rally that we already had in-house for a claims project that was going on, and then Agile Manager, and I ended up going with Agile Manager.With all of the different features, it's really user-friendly and syncs with Quality Center ALM, which is our testing tool. That's already the standard for our test scripting and defect management. Everything has to be done in Quality Center.With the claims team route on Rally, we had to make a custom sync tool that breaks a lot. It's just been a headache actually bringing that in. They're now looking at coming over to Agile Manager, syncing everything over from that first project, because there's only one previous project. Agile is new to our industry, and we've been slow to adopt everything so they're looking to bring in their artifacts to Agile Manager as well.Other Advice:There's a lot of like YouTube videos out there for easy training, even before you're in the tool to kind of get used to it. There's a lot in there, it's a really powerful tool, so we had some people get a little bit overwhelmed when they first started using. I'd recommend taking a step back, just kind of watching somebody else use it before you dive in.Disclaimer: I am a real user, and this review is based on my own experience and opinions. July 10, 2016
Rated 2 out of 5 by They are playing a catch-up game right now, they need to catch up real quick. Valuable Features:Gives us the ability to bring in the dev community as part of the testing community. I can relate to the user stories, the business requirements, whatever we are building within Agile Manager. Connecting it to the HP ADM suite that we have, and plugging it in to get Jenkins or any of these other tool sets. You can pretty much tie in in from your requirements all the way through your entire application lifecycle management. We are able to achieve that using this solution.Room for Improvement:They are playing a catch-up game right now, they need to catch up real quick. By the time they catch up the competition has moved on. They are chasing a moving target.Stability Issues:There is definitely a maturity curve that Agile Manager needs to go through with. It's still not there, and it definitely needs to grow.Scalability Issues:We use a size-based solution so it's scalable for us.Technical Support:I've not had to contact tech support.Initial Setup:It's pretty straightforward as long as you know how the tool is designed to work and the architecture behind how you need to implement it for your environment.Disclaimer: I am a real user, and this review is based on my own experience and opinions. June 26, 2016
Rated 4 out of 5 by It's able to adapt to existing processes. Valuable Features:The ability to adapt - have the product adapted to the processes that are already in place at a customer. We don't want them to have to reinvent the wheel in order to use the product.Room for Improvement:I think the biggest issues that I've seen, and this is a personal view of mine, is that most of the HPE products have a common look and feel to them. I'd really like to see it be a little more customizable to a use and user standpoint. For example. I happen to be colors blind, so I'd like to see more vivid colors on the UI, and things like that. It would make it a little more flexible from the customer standpoint.Use of Solution:I was formally an HP employee, so I've used the HP products in the past. I also was a former Mercury Interactive employee who was acquired by HP.Scalability Issues:It's been extremely scalable as far as the testing that we've done with our customers. They've all been really satisfied with the scalability of the HPE products.Initial Setup:I've worked with Agile Manager for about two years now and they've always been very receptive along the way. The nice thing about Agile Manager is when you use the product is has a "What's New" page so you can see whenever something new comes out. There it is, right in front of you.Other Advice:It really doesn't need to be as flexible as some other solutions because it's right out of the box, it's relatively easy to use. You open up, you create a test in ten minutes and then you're able to run it.Disclaimer: My company has a business relationship with this vendor other than being a customer:We're partners. June 26, 2016
Rated 4 out of 5 by We use the hierarchy Theme/Feature/Stories for a top-down approach. Valuable Features:We use the hierarchy Theme/Feature/Stories for a top-down approach. The widgets/dashboards are essential to easily setup the reporting and by putting an image on the data, it helps people to understand the issues or to see the potential impacts of their actions.Improvements to My Organization:The forecast was initially made since it was the only points we had. Obviously at the beginning of a project, all the stories were not created, therefore we were forced to make some extrapolations. By using the feature points, the projection in the future is much easier.Room for Improvement:As a consequence of the above statements, we would like to have an estimate of the possible end date when all the features will be done given a velocity. This means that we need to have some graphs/widgets which can be used over several releases.Use of Solution:We've used it for one year.Deployment Issues:The deployment was very easy as soon as I had the documentation. At the beginning, you need to learn the vocabulary used by AGM and make the links with your own previous habits. Same names may have a different meaning in different tools or approaches. As soon as I understood them, I taught the other people in the company by highlighting what was similar with our previous tool to what was different and warn them on tricky shortcuts (another approach with different meaning or use from the one we were familiar with).Stability Issues:The product is very stable and we greatly appreciate that.Scalability Issues:We were able to scale it, but my company has a bad habit. A project is open for a very long time and it piles up a lot of releases. I have to archive some, but I don't know what the result will be. If I don't do it, the response time will be degraded when the data becomes too important.Customer Service:Commercially speaking, the customer service was a total nightmare at the very beginning. I hope that I will not have to face such an issue when we have to renew.Technical Support:The technical support is good. Sometimes we need to exchange several times to be understood, but this is perfectly understandable. English is not our native language.Previous Solutions:Yes, we used a smaller and less sophisticated tool. It became too small and not sophisticate enough! We especially needed to introduce a new level in the breakdown structure (the backlog was flat only composed of stories).Implementation Team:We implemented it by our own and I think that it is a luck regarding the bad experience I had with the vendors.ROI:I cannot precisely give an estimated but everything gets done smoothly. Easier to change, to try something to see the impact, to move from a team to another one, or from a release to another one.Other Solutions Considered:Yes, we made a criteria matrix to eliminate some and ranked a few of them. Version One was the major competitor.Other Advice:I would recommend to assimilate the concepts to choose the appropriate breakdown: which themes, which applications, etc. Depending on how you want to group your items, you may want to divide your project accordingly. For instance, if you allow a feature to be assigned to different applications, the total amount of FP is no longer possible.Disclaimer: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. February 1, 2016
  • 2016-10-30 T09:08:08.156-05:00
  • bvseo_lps, prod_bvrr, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasreviews, tv_4, tr_4
  • loc_en_US, sid_3863799, prod, sort_default
1-4 of 4
 
Adding to Cart...
12/10/2016 2:32:57 PM
^ Back to Top

Maximum 300 characters
An account manager will email you within one business day to confirm your request.

Your Quote has been submitted

What Happens Next? A confirmation email is on its way. Within one business day, you will be contacted by an Account Manager to finalize your quote.

Error!

Something went wrong.

Please try again later.

License Selector

    The license selector is not currently available. Please try again later.