Try our new research platform with insights from 80,000+ expert users

JIRA Portfolio vs Planview AgilePlace comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

JIRA Portfolio
Ranking in Enterprise Agile Planning Tools
4th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
57
Ranking in other categories
No ranking in other categories
Planview AgilePlace
Ranking in Enterprise Agile Planning Tools
11th
Average Rating
9.0
Number of Reviews
11
Ranking in other categories
Application Lifecycle Management (ALM) Suites (17th)
 

Mindshare comparison

As of November 2024, in the Enterprise Agile Planning Tools category, the mindshare of JIRA Portfolio is 1.2%, down from 2.6% compared to the previous year. The mindshare of Planview AgilePlace is 1.6%, down from 2.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
 

Featured Reviews

Gary Craven - PeerSpot reviewer
Powerful, flexible solution with a bit of a learning curve
The weakness of the solution is that the interface is a little nonstandard, meaning it's very flexible. It's got a lot of power and gives the user the ability to combine different projects into the portfolio and move user stories between projects and link them. What I have found in a couple of organizations that I've used it with, is that the uptake tends to be a little slow because it's got a bit of a learning curve. It can dump data out to Excel and those programs, but it also has a big ecosystem of plugins and add-ons that you can get. I guess it has some strength in that regard, but if you're going to run it on-prem, you have to have people that are pretty well-versed in the program and have the time and capabilities to handle integration and make sure they're adding those modules correctly. Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. Now they are moving into these new use cases, including systems development, business projects, business processes, and redevelopment projects, but there is a problem with the nomenclature that they use, and some of the documentation is a little techy for moving it into those more business-focused use cases. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up.
NS
Gives us visibility into projects and enables users to leave comments on different projects
We use the submit feedback button pretty often. I encourage the teams to use that if they see anything that could be improved. But we've been really happy with how fast LeanKit improves. 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 requested that there'd be some sort of timer function on each one of the tasks.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful."
"The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers."
"The product's integration capabilities work pretty well, especially considering that more tools are always needed in enterprise-sized businesses."
"Portfolio's most valuable features are that it's user-friendly and customer-centric."
"The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects."
"The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area."
"The documentation is very well done."
"The integration is very good. We've more or less integrated with everything including reporting and registering."
"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."
"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."
"Adoption across stakeholders and visibility have been the biggest success for us with LeanKit."
"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."
"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."
"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."
 

Cons

"The product's initial setup phase is complex."
"We had to use assistance for the initial setup."
"Currently lacks AWS integration."
"I think the solution can improve in graphs and the analysis part."
"The solution's look and feel could be a bit more intuitive and user friendly."
"The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA."
"If you want to generate a report for individual usage, it's difficult."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"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."
"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."
"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."
"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 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."
"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."
"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."
 

Pricing and Cost Advice

"The pricing continues to get higher."
"There are free plugins available, but most of them are at an additional cost. Additionally, other services are an extra cost."
"The pricing of the solution is expensive."
"This solution has a comparable pricing in comparison to other similar products on the market."
"We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six."
"The price could be improved."
"When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard they increased a lot, so we decided to stop using it."
"I don't believe there are any costs in addition to the standard licensing fees."
"In general, Planview's cost structure is reasonable. You get quite a lot of functionality for the license cost that you get."
"I don't know what it would be on its own. It was basically included with what we were already paying or using. So, it was a no-brainer. It wasn't like we had to sell the company on making a purchase or anything like that. There weren't any costs that came in after implementing it."
"As far as I understand, it is not an expensive application."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
17%
Manufacturing Company
11%
Government
6%
Financial Services Firm
26%
Insurance Company
12%
Manufacturing Company
11%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about JIRA Portfolio?
The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
What is your experience regarding pricing and costs for JIRA Portfolio?
When we first got the tool, it cost 3,000 euros a year for unlimited users, which was a great deal. But the prices kept going up over the years. I'm not involved with pricing anymore, but I heard t...
What needs improvement with JIRA Portfolio?
The tool needs to improve its speed and response time.
Ask a question
Earn 20 points
 

Also Known As

Portfolio for JIRA
Planview LeanKit, LeanKit
 

Learn More

Video not available
 

Overview

 

Sample Customers

Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
REA Group, Thompson Reuters
Find out what your peers are saying about JIRA Portfolio vs. Planview AgilePlace and other solutions. Updated: November 2024.
816,406 professionals have used our research since 2012.