We performed a comparison between AgileCraft and Rally Software based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."The linking of PI Objectives with different features was one of the cool things. It had features, epics, and stories out of the box."
"It helps me evaluate teams' historical performance using velocity charts."
"It documents stories in a way where we do not have to be heavy on front-end requirements, front-end documentation, and front-end workflows."
"Helps me plan an estimate of how soon or how far out we'll be able to deliver something."
"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."
"My teams uses it for their daily agile management. They describe their user stories and track the progress of their projects."
"It has allowed the quality assurance team to keep all information in sync with the application requirements and user stories for our general development."
"The most valuable feature of this solution is the Kanban board."
"It's a good platform to keep track of all the user stories across all projects. So rather than having one off Excel spreadsheets with all of the requirements, it is a good place to have all of that."
"It should just have the integration with Jira. We haven't looked at it since Atlassian bought the product."
"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."
"I think there needs to be some simplification. The team-level side can be challenging and complicated."
"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 stronger CA can get on dependency mapping the better. That's the biggest hiccup. As you're setting up your features, they should make it easier to flag the dependencies, either across features or across projects. Then you're more set up for success."
"It's a bit cumbersome to manage the Project Picker. As we sunset teams or projects close out - but we still have test cases tied to those teams or projects that are being used in other spaces - we have this monstrous list in the Project Picker that becomes really difficult to manage and find, and we can't clean that up ourselves. It would be nice if it was easier to do that and not lose your history."
"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."
"It requires better scalability for the implementation of the whole suite. We do not use it in that fashion, and visibility is sometimes a problem."
"There are few customisation options. For instance, the workflow for story cards cannot be changed out of the box from the standard (Defined, In-Progress, Completed and Accepted)."
Earn 20 points
AgileCraft is ranked 18th in Application Lifecycle Management (ALM) Suites while Rally Software is ranked 8th in Application Lifecycle Management (ALM) Suites with 116 reviews. AgileCraft is rated 7.0, while Rally Software is rated 8.2. The top reviewer of AgileCraft writes "Linking of PI Objectives with different features was cool, but it didn't have integration with Jira". 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". AgileCraft is most compared with Jira, Jira Align and Broadcom Clarity , whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and OpenText ALM / Quality Center.
See our list of best Application Lifecycle Management (ALM) Suites vendors and best Enterprise Agile Planning Tools vendors.
We monitor all Application Lifecycle Management (ALM) Suites 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.
