We performed a comparison between Planview AgilePlace 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."It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"The "Blocking" feature has helped our scrum masters track impediments and share them at the program level to stakeholders with accountability and detail so that they understand and the action items which can be noted easily."
"People found the ability to set up different lanes and the ability to see where they're within the progress most valuable. They can use different colored cards or sticky notes, and then they can separate out which cards belong to a department or the initiative they're working on. They can filter who's working on it, and I've got good feedback about that."
"LeanKit is amazing when it comes to getting answers about a given card's status. That's one of the biggest takeaways that we've had. The status is right there on the board. Everybody can see it. You just click on it and it gives you everything that you need to know, especially the comments feature because it gives us a timeline of updates. We use that a lot where we write a comment on the card and then we can see and track progress as we move it across the board."
"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."
"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."
"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."
"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."
"It helps with getting the alignment between strategy and execution for the product teams, all the way down to the delivery teams."
"It is very stable. It has been on the market a long time."
"The effect of these kind of tools drives the way you organize things. It helps you shape the way you flow."
"It's very user-friendly."
"If teams are tracking correctly and entering their information correctly, it's really easy to see where you're at, within your release, and whether you're on track or not."
"We use the roadmap features, and we're getting better at using dates to use the roadmap so that we can see if we're on target for work."
"With this product, searching for historical information or the evolution of the requirement, detecting conflict between projects has helped a lot."
"The most valuable feature is actually creating a field within there for architectural review. So when teams are struggling or have questions on the architecture or strategy that they take, they can actually flag that particular story, release, or project. Those can then be reviewed by the architecture team and the teams actually get additional information on how to course-correct, build on the architecture that we're trying to build throughout the organization, and get over road blocks much quicker."
"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."
"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."
"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."
"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."
"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."
"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."
"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."
"I do not know what it can do in the area of scrum. Maybe it has that functionality. I have never tried to set it up. You think of LeanKit from the perspective of Kanban. I don't know if there is a template for scrum, a scaled agile framework, or any of those scaling frameworks."
"I'd like to be able to color code timeboxes, so I have an easy visual way to track the success of sprints."
"As it is right now, it does not support automation of the quality assurance process. It just supports manual testing."
"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."
"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."
"We want Rally to generate OKRs, to allow teams to record the OKRs, and then the OKRs can be mapped to the epics and there is organizational alignment."
"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."
"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."
"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."
Earn 20 points
Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites while Rally Software is ranked 8th 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 "A solution that enables users to accurately estimate the time required for building large software projects". Planview AgilePlace is most compared with Jira, Microsoft Azure DevOps, Jira Align and JIRA Portfolio, whereas Rally Software is most compared with Microsoft Azure DevOps, Jira, TFS, Jira Align and Asana.
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.
