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 have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"The most valuable feature of GitLab is the automatic merging of code."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"I like GitLab's security and SAS tools."
"GitLab's best features are continuous integration and fast deployment."
"CI/CD is valuable for me."
"This product is always evolving, and they listen to the customers."
"We use the roadmap features, and we're getting better at using dates to use the roadmap so that we can see if we're on target for work."
"It's very user-friendly."
"The main ways that I used it when I was in it day to day was keeping up with the burn rate within the teams. Also, to track at the feature level too, as far as how we were doing with actually being able to deliver that feature."
"When it comes to the valuable features of Rally Software, it excels at burn-down charts, burn-up charts, and road mapping once it's set up. I particularly appreciated the new feature for releases and road mapping, which worked exceptionally well."
"CA Agile Central helps the entire organization run like one powerful team."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"What I like most about Rally Software, in terms of using it for the agile process, is that it's clear, useful, and user-friendly. I also like that it has every field you can use for the Scrum process."
"Gives me a dashboard where I can see what things are not being worked on, what things are blocked."
"It can be free for commercial use."
"I would like configuration of a YML file to be done via UI rather than a code file."
"We would like to have easier tutorials. Their tutorials are too technical for a user to understand. They should be more detailed but less technical."
"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."
"The integration could be slightly better."
"The tool should include a feature that helps to edit the code directly."
"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."
"I would like to have some features to support peer review."
"CA Agile Central does not have a workflow tool included."
"I think the interface could be a little bit more visual and less wordy. Right now, it seems like it's just a lot of text on the page. In other ticketing systems where it's more visual, you can see more of a flow. But in this one it's more just a list of tasks. I would like to see that a little bit better, especially considering it has so many great organizational features, like child tasks, different artifacts. It would be great to see it presented more appropriately."
"It is hard to track the changes. For example, we're in sprint 25, and then we have 26, 27, 28, and 29. Throughout that whole time, we're developing pipelines in Azure, moving to GitHub, creating pipelines, and working with teams. But sometimes, we need to revisit specific decisions made in previous sprints, like pipeline details. Maybe it's in our Azure Wiki, GitHub, or Teams, but it's not always consistent. I wish I could search for all tasks or stories related to that particular effort without needing to know everyone's individual stories or features."
"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 would like more meaningful, customizable dashboards."
"What I don't like about it is that it is really hard to find old work to reference information and use the reporting section of the application in terms of trying to analyze trends. If I am trying to find out which interfaces took this long and I want to compare and measure improvement from one quarter to another quarter, the reporting mechanism within Rally is very troublesome. They have an Excel plugin that you're supposed to use, but you literally have to pull the raw data out before you can do the analysis. You can't do it within Rally, and if you can, it is a secret, and I don't know how to do it. It should have better, easier, and user-friendly reporting without having to use the Excel add-in. It is very clunky. There is a lot of data in there, but it is not organized in such a way that makes it intuitive. You really have to kind of look for where do you put your documentation or dates. Some customization is available, but it is not plug-and-play like Jira. When I switched from TFS to Jira, I just went and started using Jira, whereas with Rally, you kind of have to really get in and figure out what you need to do before you set stuff up, or you're going to get yourself stuck. You can just start using Jira and be successful."
"The navigation within the tool sometimes is a little tricky for me. I'm sure with more use, more practice, I'll become accustomed to it, but some of the things just aren't intuitive."
"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 Digital.ai Agility. 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.
