We performed a comparison between GitLab and Rally Software based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I like GitLab's security and SAS tools."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"This is a scalable solution. We had around 200 users working with it."
"I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools."
"The merging feature makes it easy later on for the deployment."
"GitLab offers a good interface for doing code reviews between two colleagues."
"A user friendly solution."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"Its ability to scale."
"The most valuable features are in-line editing, easy custom view setup, intuitive and helpful visuals (e.g., contextual formatting) and the collaboration features."
"The configurable Portfolio Management and parent-child relationships."
"We've actually used it for virtual PI planning. We have teams in different locations, and we actually virtually do PI planning, big-room planning, using the tools."
"The most valuable feature of this solution is the Kanban board."
"It scales very well. It improves in technology constantly and gets up to speed with the latest and greatest."
"Helps me determine how fast I can launch, go to production."
"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."
"There is room for improvement in GitLab Agents."
"I would like configuration of a YML file to be done via UI rather than a code file."
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
"Even if I say I want some improvement, they will say it is already planned in the first quarter, second quarter, or third quarter. That said, most everything is quite improved already, and they're improving even further still."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"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 stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"There's a lot of support for Scrum and Agile, but it needs something for the Kanban side."
"A lot of the features that we would be looking to add, I am learning may not be within Agile Central, but part of another CA tool set."
"We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them."
"We'd like better dashboards to make visibility better."
"I would like to see more Kanban support. As it stands, it doesn't seem to have the features or the layouts that the teams really need to be able to execute their tasks. It almost tries to force you into more of a Scrum style."
"We would like more meaningful, customizable dashboards."
"It could improve by being self-organizing: user stories, different hierarchies, and different perspectives. Not just as a single hierarchical structure, but something that can be multidimensional."
GitLab is ranked 2nd in Enterprise Agile Planning Tools with 70 reviews while Rally Software is ranked 6th in Enterprise Agile Planning Tools with 116 reviews. GitLab is rated 8.6, while Rally Software is rated 8.2. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of Rally Software writes "Good discussion and note-taking capabilities but hard to track the changes". GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and OpenText ALM Octane. See our GitLab vs. Rally Software report.
See our list of best Enterprise Agile Planning Tools vendors.
We monitor all Enterprise Agile Planning Tools 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.
