We performed a comparison between Planview AgilePlace and Rally Software based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"Every feature is valuable. LeanKit is a Kanban-based tool where you have a visual interface that you can use to create various cards and to create boards to house those cards. You can create a board for managing project work. You can create a board to do PI planning. It is pretty close to the agile way of doing business."
"My team specifically uses our board for all of our Remedy tickets that come in. We had a card for every ticket that we get, and we're able to add the link to that specific ticket there.If I'm out of office, for example, and someone else needs to work a ticket or someone is being contacted to work on a ticket, I don't have to sign on it. Someone else can easily access that ticket because I put the link in there. It's nice. It has a lot of great functionality in there."
"I would say it's highly scalable. LeanKit can scale across the enterprise easily. Every business could probably find a use case for leveraging LeanKit."
"Using the tool seems to save time versus trying to do things in a regular manner. It is highly collaborative; everybody can see things in one place. It is a highly functional, but pretty simple tool. That is hard to find: A tool that has a lot of functions, but is also simple."
"We use the board and card hierarchies in terms of sprints so that we can see if we have cross-functional teams that are working on the same projects together, especially when projects have dependencies. The parent-child relationship within cards is really nice so that we can see what kind of dependencies there are when we're trying to get projects finished."
"The transparency that it brings is valuable. I like to look at things from all angles, and sometimes, flip chart paper on a wall and sticky notes are better than something on a screen, but the way they've made it accessible from all points for anyone within an organization is great. As a project management guy, sometimes, you have to force people into new environments where they have to see what you're talking about. Any screen is a barrier, and people got to get into the screen. How do you know they do? You don't necessarily know, but you are getting around that barrier with a countermeasure of making it accessible to as many as possible. So, everyone can jump in there and see everything. It is fully transparent, and I like that. This is one thing that helps."
"The transparency it allows us to provide, both from the team level all the way through the executive level within the company and the work that we are doing."
"It allows us to work in a more dynamic fashion and track more of the development lifecycle."
"Its ability to scale."
"The reporting, and being able to roll that up across the verticals, was an important selling point for us."
"The Defect feature. In one view you can see all your defects and you can push them into the different releases."
"When we went into Scaled Agile Framework, we could not have done it without the use of Agile Central. It allows us to scale our Scrum teams, and it also enables us when we do our remote big room plannings."
"It helps me evaluate teams' historical performance using velocity charts."
"It scales very well. It improves in technology constantly and gets up to speed with the latest and greatest."
"Being able to track actual time on cards or sprints, instead of using just the planned start and stop date, would also be useful. I would like to see something like JIRA has with actual sprint starts and stops."
"The biggest improvement would be the API and data connections and making the data more accessible or quicker to access. One of our team members has brought up actual-time tracking on a card as a potential improvement. They had an interest in knowing how long a specific card had been worked on by a specific user or somebody that was assigned to that card. But there's not really a way for them to start and stop a time that they were actually working on it, except for if we created a different lane and they dragged it into the lane and then stopped using it in the lane."
"The ability to report on customizable fields and third-party extensions needs improvement. I'd like to see more of those being able to be used. I don't know how that works for Planview, but just getting a little bit more added there would be nice."
"It is a pretty good product. It is really hard to think of things that I'd want to be improved. Sometimes, we use it for project management lessons learned. So, we have three columns, such as Could be Improved, Keep Doing, and Works Really Well. It would be helpful if there was a template set up for something like that because we code different cards based on the category. For example, if something belongs to the Could be Improved category, we may have those cards as yellow, but then I have to change the color of them and put a header. It is not as smooth, but it still works fine. To be honest, I don't have a lot of complaints about it."
"We are a 750-employee company, so we got lucky that our board approved the kind of funding we needed for the solution. But, LeanKit probably needs to reduce its pricing."
"Our overall impression of Leankit has been very positive, however, our experience with the JIRA integration into our Leankit boards was much harder than we anticipated and that could be improved by simplifying it somehow."
"Within the current features, if they can give some ability to show more icons on the card, it would be helpful. It would help us in showing more data on the cards."
"There's room for improvement with the Instant Coffee feature. There are other businesses that have been interested in leveraging a virtual whiteboard or sticky note capability and how Instant Coffee was developed has not met the mark."
"More customization capabilities would be helpful. Providing a little bit more structure around how the system should be set up in terms of the hierarchy structure might be helpful as well."
"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."
"In terms of improvement, perhaps some more metrics. If they could add some additional, that would be cool."
"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."
"We did submit an enhancement request. I think a lot of teams that do very large scale products have the same issue. They just do not realize it would help them."
"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."
"In Rally Software, the connection with GitLab and GitHub needs improvement."
"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."
Earn 20 points
Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites while Rally Software is ranked 7th in Application Lifecycle Management (ALM) Suites with 116 reviews. Planview AgilePlace is rated 9.0, while Rally Software is rated 8.2. The top reviewer of Planview AgilePlace writes "Gives us visibility into projects and enables users to leave comments on different projects". On the other hand, the top reviewer of Rally Software writes "Good discussion and note-taking capabilities but hard to track the changes". Planview AgilePlace is most compared with Jira, Microsoft Azure DevOps and Jira Align, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and ServiceNow Strategic Portfolio Management. See our Planview AgilePlace vs. Rally Software report.
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.