We performed a comparison between Jira and Planview AgilePlace 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.
"Work management software that has the flexibility to be configured for any company. It's stable, scalable, and offers responsive support."
"Integrates with other components."
"What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best in class solutions, but it's so well integrated. You will not have many problems with integration."
"The ability to design your own workflows is a great feature."
"We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users."
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"The burndown charts help track projects."
"It makes work visible, so everybody knows where everything is. It uses Kanban, and that makes work visible."
"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."
"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."
"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."
"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."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"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."
"The work items structure is not hierarchical and that needs to be changed. It's too flat."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place."
"If you're not a technical person, it might not be very user-friendly."
"Users can be confused about how to use this tool as it's very complex."
"Not very intuitive for project admins."
"It is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira."
"From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement."
"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."
"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."
"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."
"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."
"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."
"They have a feature called Instant Coffee. It was in the beta phase. They released it from beta, and now, it is a legit thing. We were in the pilot here. I liked the idea of Instant Coffee, and I like how it is integrated, to some degree, with LeanKit, but I have two big rocks to throw at them on this. The first one is that Instant Coffee does not save your work very well in terms of saving it in formats that you can then go back and edit as Visio would. It leads to the next point, which is, we're not really clear on what they're trying to do with Instant Coffee. I feel that they're trying not to reinvent Visio, Miro, and other software programs out there that do mapping, visual diagrams, etc. Miro is fantastic in that regard. I gather they're not trying to reinvent Miro, but it sure would be nice if it had more aspects of Miro in it, such as being able to draw arrows and write on them on the top."
"The integration with the Enterprise One product is probably an area for improvement. It's not really broken. It's just that it is such a handy tool and a great way to visually manage things. There is a very limited hookup/integration between Enterprise One, which is the master Planview tool, and LeanKit. While they are looking at this on their roadmap, it definitely needs to happen. There is a lot of opportunity there."
Earn 20 points
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews while Planview AgilePlace is ranked 17th in Application Lifecycle Management (ALM) Suites. Jira is rated 8.2, while Planview AgilePlace is rated 9.0. The top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". On the other hand, the top reviewer of Planview AgilePlace writes "Gives us visibility into projects and enables users to leave comments on different projects". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and IBM Engineering Workflow Management, whereas Planview AgilePlace is most compared with Microsoft Azure DevOps, Jira Align, Rally Software and JIRA Portfolio.
See our list of best Application Lifecycle Management (ALM) Suites 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.
