Rally Software Manufacturing Reviews & Insights

Score6.8 out of 10

122 Reviews and Ratings

Community insights

TrustRadius Insights for Rally Software are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Powerful Agile DevOps Planning and Tracking: Many reviewers have found Rally to be a powerful tool for agile DevOps planning and tracking. It provides rapid visibility of progress or problems across a large number of teams, allowing users to effectively manage and prioritize tasks.

Portfolio View for Clear Visibility: Reviewers appreciate the portfolio view feature of Rally, as it allows product management to have clear visibility across all their product features. This feature helps in effectively managing and prioritizing tasks by providing a comprehensive overview of the project's progress.

Strong Feedback Metrics for Task Tracking: Users have mentioned that Rally provides strong feedback metrics for both teams and individuals. This feature helps in tracking the status of tasks and ensuring that commitments are being met, contributing to efficient task management.

Rally Software Reviews

2 Reviews

ManufacturingAutomotive1Furniture1

Best-suited to large organizations

Rating: 6 out of 10

Incentivized

August 1, 2019

Use Cases and Deployment Scope

Rally is being used across my entire organization. Initiatives are codified as Epics and Features in Rally, and the company collects metrics on the progress of these initiatives. The metrics are also used within teams to track velocity and performance over time.

Pros

Organizes work into well-defined structures
Allows useful metrics to be collected
Is very customizable depending on what each team member wants to see
Has a wealth of features and can be used in many ways, depending on the organization's needs and desires

Cons

The user interface is slightly "clunky"
It is easy to overwrite others' changes if you haven't refreshed your page in a while, since updates do not happen automatically
For my team's needs, there are way too many features and fields and it can be confusing to dig through that to find the subset we use

Likelihood to Recommend

I would imagine that Rally is fantastic from the perspective of someone overseeing a large organization. Having everyone on the same feature-rich tool means that every team can customize it (to a degree) for their needs while still providing useful metrics upward. However, for small organizations or single teams, it is probably overkill.

Verified User

Contributor in Information Technology (Automotive company, 10,001+ employees)

Vetted Review

2 years of experience

More than adequate, but disappointing and getting more so over time.

Rating: 4 out of 10

Incentivized

June 8, 2017

Use Cases and Deployment Scope

It's used in tech engineering to manage agile development on several teams developing integrated software, firmware and hardware products.

Pros

Handle the complexities of multiple teams.
Visual indicators for individual story states.
Adaptable as your teams go through the learning curve in Agility.

Cons

Portfolio management... poor graphical presentation of portfolio (as compared to Aha! for example).
Release management... the model and implementation are not cohesive, require many manual steps to maintain release plan integrity, seems to support SAFe at the expense of other, more Agile, practices.
Visualization, in general... minimal capability for user-defined charting (unless you want to do SDK programming), and most canned charts offered are with an old internal SDK that doesn't support new features
My big gripe is that in the two years we've had the product, an unbelievably SMALL amount of work appears to have been done. Glaring gaps and inconsistencies (conceptual and practical) continue to go unaddressed, while apparently great effort is being spent on new features having marginal utility.
Based on this experience I have concerns for the ability of CA to bring the product up to modern standards and to restore its conceptual integrity after years of piecemeal incremental improvement. For a large development team, they don't seem to be delivering much new value.

Likelihood to Recommend

Standard Scrum from story grooming to delivery is good. Allocating features to releases is not good because in order to visualize you also have to assign stories to releases. Release management in general uses a narrow and often inscrutable conceptual model, so we have avoided it. We use milestones instead but they have only limited support.

Bob Lieberman

Agile Coach for Technology Development in Engineering at Steelcase (Furniture, 10,001+ employees)

Vetted Review

2 years of experience

View profile