Rally Software Room for Improvement

LH
Dev Ops Engineer at a insurance company with 5,001-10,000 employees

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.

So, I would like to see a tag system with prefixes like KBI for knowledge-based information or JC for Java Core to search and find relevant items easily.

It would be so much easier to search for everything related to KBI or the actual feature itself. I could even search within my group using a shared scrum team name, like "Snoopy's Developers," and then find everything related to JC or Java code. 

Another pain point for us is managing our limited number of licenses with contractors coming and going. It's a constant struggle to figure out who's still active. We have to run reports to find people who haven't used Rally for x months, like logged in or whatever. 

As an admin, wouldn't it be great if we could have an automated report emailed to someone, say another admin, highlighting users who haven't logged in for, like 12 months? That way, we could easily go in and deactivate or revoke the licenses. If someone hasn't logged in for eight months, why not have Rally automatically disable them?

So, easier license tracking would definitely be beneficial.

Those are my two main wish-list items. With the Description field, it can work for them; it's free. But they have to be diligent enough to remember to tag things there. 

And even then, it's not always clear during stand-ups unless you specifically look at it. Someone is working on "admin" or "accessories" or whatever that "digital transformation" tag is. That kind of thing helps track progress at a glance.

View full review »
Shawn Carlson - PeerSpot reviewer
Agile Delivery Transformation at Transparent Change

Rally Software is highly complex, and it takes some effort to get everything tied together. But once you do, it's a satisfying experience, and the result looks beautiful. Azure, ServiceNow, and Jira do not have all the features that Rally Software provides in one place, making it an exceptional tool for project management.

It was either Optum or Rally Software that had a significant number of connections and workflows that were challenging to comprehend. As a result, the visualization was lacking, which was frustrating. One feature of Jira that I admire is the ability to view the workflows for user stories, for instance, by going into the user story settings for my team. You can see where the story is heading and what the workflows are. Unfortunately, Rally Software does not offer this visual representation, although it does have all the connections. However, to utilize it correctly, you must be aware of how to set it up correctly, and Rally Software could do a better job of splitting up workflows.

View full review »
Luca La Via - PeerSpot reviewer
Software Engineering Manager at Biesse

The big problem with Rally Software is migration. If I were to migrate from Microsoft Azure DevOps to Rally Software, it would require more effort because in Microsoft Azure DevOps, every time you create a project, you have Git for each project you create. My current company has the pipeline and virtual machine for compiling code in the project, so if I migrate that, it would mean that I have to put in extra effort to evaluate the pipeline in Rally Software, so that's a big problem for me.

In Rally Software, the connection with GitLab and GitHub needs improvement because every time I evaluate Rally Software, there's an issue. When I have a lot of team members and push the code in Git, I track the requirement and the code. Rally Software needs to improve in that area because I'm a person who understands the requirement. However, I still have to evaluate the code, virtual machine, and pipeline despite my knowledge. I don't have this problem with Microsoft Azure DevOps, only with Rally Software, so this is an area for improvement.

In future releases of Rally Software, I want it to have GitHub and GitLab connectors. If it has existing connectors, then the connectors should be better.

View full review »
Buyer's Guide
Rally Software
March 2024
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.
VK
Agile and DevOps Coach at Infosys

Rally has the ability to improve the features. We would like to see progress made against the features, probably in the form of a dashboard, where when teams complete stories, the features upload, and the stories are completed, and the feature about them gets updated with the progress. This is available in Jira but not in Rally.

That's something I would like to see because the management wants to see how far we have come with the epics and the features. They want a dashboard that would allow Rally to provide a picture to the leadership of the progress made on the epics and features.

There should also be an automation feature. When the last story in the feature is finished, the feature's status should be automatically updated.

The user interface can be improved. I still don't think the UI is as impressive as Azure DevOps or Jira.

The performance can still be improved.

Rally Software should develop an OKR framework that will allow OKRs to be recorded in Rally. That would be a win-win situation because there would be changes for Rally Software because there are other tools that are attempting to provide, the OKR option, and the tool to this Rally integration is difficult. Rally will be more successful if they can enable the OKR capturing or recording process.

We want Rally to generate OKRs, to allow teams to record the OKRs, and then the OKRs can be mapped to the epics and there is organizational alignment. The organization can execute those objectives using the team's backlog.

View full review »
SD
Sr Engineering Manager - Design Engineering at Baker Hughes

I don't have any specific suggestions for improvement regarding the solution because we are currently satisfied with all aspects. Our usage requirements are relatively straightforward, and we haven't encountered any significant challenges or complexities. Therefore, I don't have any valuable suggestions to provide at this time.

I hear from some people that it could be customized, but they don't have details on how. Customization is possibly a desirable feature, and I don't know if it is available in the system. Customization features may not be exposed or unavailable, so people may be looking for them. So, customization is an area people have told me is more desirable.

View full review »
HeloisaClaro - PeerSpot reviewer
Process and Agility Consultant at V.tal

We'd like to be able to export information about the users, like rules. It's not easy to identify the teams, users, and rules. We'd like better dashboards to make visibility better. They are a bit complex right now. 

It is not integrated with the PPM. It's very difficult to make an integration with both.

View full review »
Buyer's Guide
Rally Software
March 2024
Learn what your peers think about Rally Software. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
763,955 professionals have used our research since 2012.