Anonymous UserManufacturing Manager, Capital COE at a manufacturing company
Gizem MercanCloud Architect at a manufacturing company
Kleber AChief Operating Officer at a tech 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 dashboard and interface make it easy to use."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"Everything is easy to configure and easy to work with."
"A user friendly solution."
"It speeds up our development, it's faster, safer, and more convenient."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"GitLab offers a good interface for doing code reviews between two colleagues."
"This product is always evolving, and they listen to the customers."
"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."
"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."
"GitLab doesn't have AWS integration. It would be better to have integration with other container management environments beyond Kubernetes. It has very good integration with Kubernetes, but it doesn't have good integration with, for example, AWS, ETS, etc."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"The only thing our company is really waiting on in terms of features is the development of metrics."
"Reporting could be improved."
"I would like to see better integration with project management tools such as Jira."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"It would be really good if they integrated more features in application security."
"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."
"In general, Planview's cost structure is reasonable. You get quite a lot of functionality for the license cost that you get."
"I think that we pay approximately $100 USD per month."
"The price is okay."
"It seems reasonable. Our IT team manages the licenses."
"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."
"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."
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.
GitLab is a single application with features for the whole software development and operations (DevOps) lifecycle.
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:
GitLab is ranked 3rd in Release Automation with 11 reviews while Microsoft Azure DevOps is ranked 1st in Release Automation with 40 reviews. GitLab is rated 8.4, while Microsoft Azure DevOps is rated 8.0. The top reviewer of GitLab writes "Provides or mandates quantitative code into the Master". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". GitLab is most compared with Tekton, TeamCity, Bamboo, Sonatype Nexus Lifecycle and Black Duck, whereas Microsoft Azure DevOps is most compared with Jira, TFS, Ansible, UrbanCode Deploy and Micro Focus ALM Quality Center. See our GitLab vs. Microsoft Azure DevOps report.
We monitor all Release Automation 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.