Anonymous UserManufacturing Manager, Capital COE at a manufacturing company
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"We use the board and card hierarchies in terms of sprints so that we can see if we have cross-functional teams that are working on the same projects together, especially when projects have dependencies. The parent-child relationship within cards is really nice so that we can see what kind of dependencies there are when we're trying to get projects finished."
"My team specifically uses our board for all of our Remedy tickets that come in. We had a card for every ticket that we get, and we're able to add the link to that specific ticket there.If I'm out of office, for example, and someone else needs to work a ticket or someone is being contacted to work on a ticket, I don't have to sign on it. Someone else can easily access that ticket because I put the link in there. It's nice. It has a lot of great functionality in there."
"Using the tool seems to save time versus trying to do things in a regular manner. It is highly collaborative; everybody can see things in one place. It is a highly functional, but pretty simple tool. That is hard to find: A tool that has a lot of functions, but is also simple."
"The user interface is very friendly."
"It's graphical representation and tools are easy to use."
"All of the features related to release management are very good."
"My first impression of DevOps, after using Jira, is that it has a much better, more intuitive, and more user-friendly interface."
"Technical support has been excellent. On that side, Microsoft is very good. The customer support of Microsoft has really improved this past year. On the cloud side also we are very satisfied because it offers very good support."
"Azure enables us to create a staging environment through to a production environment in an easier way and then get the code and run that."
"I like the entire tool because it is a one-stop-solution for DevOps."
"The solution is easy to implement and easy to use."
"We have been using it because it gives certain abilities in the automotive industry, such as auditing or keeping track of information."
"We found the requirement management and the version control features to be the most useful for our client."
"Complete traceability as per process requirements."
"The tool is quite structured and has a good command set."
"The most valuable feature is traceability starting from the requirements until the end of a project."
"It's a good tool to manage software versions, update the status, and manage tasks."
"I do not know what it can do in the area of scrum. Maybe it has that functionality. I have never tried to set it up. You think of LeanKit from the perspective of Kanban. I don't know if there is a template for scrum, a scaled agile framework, or any of those scaling frameworks."
"Being able to track actual time on cards or sprints, instead of using just the planned start and stop date, would also be useful. I would like to see something like JIRA has with actual sprint starts and stops."
"The ability to report on customizable fields and third-party extensions needs improvement. I'd like to see more of those being able to be used. I don't know how that works for Planview, but just getting a little bit more added there would be nice."
"The integration with the Enterprise One product is probably an area for improvement. It's not really broken. It's just that it is such a handy tool and a great way to visually manage things. There is a very limited hookup/integration between Enterprise One, which is the master Planview tool, and LeanKit. While they are looking at this on their roadmap, it definitely needs to happen. There is a lot of opportunity there."
"I would like to see more customization available to the administrator."
"Non-functional testing such as security testing, log testing, and performance testing can be improved with a better visualization."
"Better integration with the Linux operating system would be an improvement for this solution."
"I would like to see better interoperability with the agile scaling frameworks."
"They do very frequent releases, there's a complete change in UI kind of stuff. Sometimes it feels like they change it too often."
"The solution could work to improve their reporting."
"There are certain areas in Azure DevOps that are better in other products."
"One thing I would note is that it's hard to know what is included or not in the product. Especially when you begin to try and compare it to other solutions. When you go to a site like VersionOne, they tell you Azure DevOps doesn't have this or that, and when you go to Microsoft, it says VersionOne doesn't have this or that. They could do a better job of laying out exactly what is on offer so customers know going in exactly what they'll get."
"To be honest, the third controller system is kind of old. There are lots of transactional changes that have not been implemented in PTC. If you have a larger project, for example, whenever you give bits and need to change 10,000 files you can just commit them. But here the work style is a little more file based, so you'll have to take care of almost all the files individually. It's not a single commit like you do here, but rather you have to allocate time for each component or file that you want to check in or commit. That's a very big issue."
"It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer."
"There are not enough reports. People would like to see something similar to what is available in JIRA."
"I would like to see better integration from the architectural side."
"We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all."
"It's not easy to plan on this solution and it's not user-friendly. The interface should be more like a web interface. It's not easy to use."
"In general, Planview's cost structure is reasonable. You get quite a lot of functionality for the license cost that you get."
"It's a good tool, quite rich, it has a lot of features, and quite a lot of analytical capabilities which are built on top of it so that you can see how your projects are going and all that stuff. It's a good tool."
"There is a licensing fee of $6/user per month."
"The price is cheaper than Jira and some of the other competing tools."
"It is the least expensive product in this class."
"I find that the pricing is good, and it is competitive with the other vendors in the market."
"Microsoft Azure DevOps is free for up to five users and allows you to track a maximum of three projects."
"It is a subscription model and I only pay for what I use."
"The price of this solution is fair."
Earn 20 points
Planview LeanKit enables engineering teams across all levels of the organization with a visual work delivery tool to apply Lean management principles to their work, helping them work smarter and deliver faster.
Azure DevOps Services is a cloud service for collaborating on code development. It provides an integrated set of features that you access through your web browser or IDE client, including the following:
Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 40 reviews while PTC Integrity is ranked 12th in Application Lifecycle Management (ALM) Suites with 6 reviews. Microsoft Azure DevOps is rated 8.0, while PTC Integrity is rated 6.6. The top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". On the other hand, the top reviewer of PTC Integrity writes "Good item management and version control but does not have good performance ". Microsoft Azure DevOps is most compared with Jira, TFS, GitLab, Ansible and UrbanCode Deploy, whereas PTC Integrity is most compared with Jira, Polarion ALM, codeBeamer ALM, IBM Rational ALM and Atlassian ALM. See our Microsoft Azure DevOps vs. PTC Integrity report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.