We performed a comparison between JIRA Portfolio 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."The documentation is very well done."
"Portfolio's most valuable features are that it's user-friendly and customer-centric."
"I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely."
"Version management is the most valuable feature of JIRA Portfolio."
"The most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability."
"The customized workflows we can define are very valuable. JIRA's private projects is very useful as well. There are also a lot of plugins that they provide."
"It is very stable. It has been on the market a long time."
"The reporting, and being able to roll that up across the verticals, was an important selling point for us."
"It's very user-friendly."
"We can work better and at a higher quality, than we were able to before."
"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."
"Ease of use - I don't even know when a new release is coming and I don't need to because it's so easy to use what's new."
"The configurable Portfolio Management and parent-child relationships."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"The interface JIRA Portfolio could improve."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"The solution's look and feel could be a bit more intuitive and user friendly."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client."
"Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support."
"Converting a task into an epic is very troublesome."
"An improvement would be if Portfolio were integrated with Office 365."
"One problem I see is that if there is a dependent user story - for example, if my team is working on one thing and there is a dependent user story from another team - we can have a dependency created but we don't know if there is a change of status from the other team. That is something which is very important for Agile Central to look into so that if the other team makes any changes we will be notified as well."
"I think there needs to be some simplification. The team-level side can be challenging and complicated."
"I'd like the ability to customize reports without having to incur Professional Services, or having to write my own code GitHub and then implement that as a custom report. That's untenable. It's not sustainable."
"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."
"I'd like to be able to color code timeboxes, so I have an easy visual way to track the success of sprints."
"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."
"I think there is a missing link with the development activity. Some developers are pushing in new versions of the code, but you cannot make the link from the user story to a specific application version."
"I wish there was a view, like the Kanban view, where you could see the parent, and see all the children visually, so you could drag and drop where you want it to go. Something like that might help."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 46 reviews while Rally Software is ranked 7th in Enterprise Agile Planning Tools with 116 reviews. JIRA Portfolio is rated 8.0, while Rally Software is rated 8.2. The top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". On the other hand, the top reviewer of Rally Software writes "A solution that enables users to accurately estimate the time required for building large software projects". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Adobe Workfront, Microsoft Project Server and Microsoft Azure DevOps, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and OpenText ALM / Quality Center. See our JIRA Portfolio 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.