Rally Software Review

The portfolio views and reports helped me to create, prioritize, manage and accept portfolio capabilities, features and user stories.

What is most valuable?

As a Product Owner/Product Manager on an application team, it was my job to create, prioritize, manage, and accept portfolio capabilities, features, and user stories. The portfolio views and reports were the tools I used the most to do that.

The Agile process my team follows anticipates that requirements and priorities will change from sprint to sprint. Having a real-time view of what has been accomplished, what is in progress, and our backlog, that is easily accessible to all stakeholders, (customers, executives, implementation members, and delivery leads, as well as our staff of multi-discipline Product Owners and Managers) is critical to building and creating a high quality and viable product.

My scrum masters walked through the analysis, development, and testing tasks every day with team members, using the Team Status page to ask each team member (onshore, nearshore and offshore) for status on the prior day’s work and plans for today. As a Product Owner, I monitor User Story status via a Ready To Accept app on my Dashboard for User Stories that are ready to be accepted because all the required tasks are completed.

By using the Portfolio Items page I can adjust priorities and accept completed features from a single page.

How has it helped my organization?

It is used as a source of truth on workstream, workstream progress and issue management.

What needs improvement?

  • Bulk priority change of portfolio items
  • Portfolio feature
  • Dependency reports

In our project, when a feature is completed, we mark it as completed but then don’t want to have it show at the top of the priority list and don’t want to constantly add filters to filter out completed items. So we put the completed items at the bottom of the backlog by changing the priority. There’s no way to do this except one at a time. With thousands of features, this is cumbersome.

There is no good way to get an overall view of feature dependencies except to go to one feature at a time and look at its specific dependencies. The team could have made great use of a report/dashboard of some kind (I failed at coding my own) that gave a larger view of feature inter-dependencies.

For how long have I used the solution?

We have been using the solution for two years.

What do I think about the stability of the solution?

Generally, we did not encounter any issues with stability.

What do I think about the scalability of the solution?

There was some slowness noticeable on days of heavy usage by many users (peak usage impact).

How are customer service and technical support?

I did not use the technical support.

Which solution did I use previously and why did I switch?

We did not previously use a different solution.

What other advice do I have?

Use relational database concepts to relate items together instead of continuing to use old location-based organization concepts.

**Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
More Rally Software reviews from users
...who work at a Financial Services Firm
...who compared it with Jira
Add a Comment