We performed a comparison between JIRA Portfolio and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work."
"The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone."
"JIRA Portfolio has many wonderful features."
"The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good."
"Its stability is very reliable."
"The graphics and the resolution of the work are very good."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"Managing product development and managing inter-team communications are also valuable features."
"Whenever we have issues, there is always someone ready to help us. Their people are knowledgeable and responsive. They get to tickets quickly. Just three or four weeks ago, we were having issues with getting data into Planview. We submitted a ticket and the turnaround was probably 45 minutes to get a response."
"We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio."
"The solution view into resource capacity and availability helps us to manage work."
"I like that it's an enterprise environment. I can look across everything that's going on and have a sense of what is going on within the organization."
"Enterprise One has enabled us to eliminate Excel. We don't track financials anymore in an Excel format, which the company was doing before. Even now, being a new portfolio manager four months in, I'm able to just pick up my project. I'm able to see where I am right now. That improvised it to be more automated. The only missing part is the integration between tools. I'm not able to see my full schedule, but I know what are my important milestones are like watching the financials and all that stuff."
"We use time reporting. We convert time reporting into financial costs and do contractor and capacity planning for our resources. We track our work. So, that's the module we use extensively. As a matter of fact, we have upwards of 300 open projects at this given moment. It is pretty close to 300 open activities that are working."
"The integration stuff from tool to tool, like Projectplace to Planview, to manage projects is the most valuable feature. It keeps all our tasks up-to-date. It closely follows up with everything, which is really cool."
"We can easily see which functions are overcapacity. Before, we did not have visibility into that."
"The integration needs to be done with different tools."
"When using a scrum board, it only shows the current or open sprint. However, we also need to see past and future sprints, which is important for planning the next sprint. To solve this, we tried using a Kanban board instead, but since we follow the Scrum methodology, it's not the ideal solution."
"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. 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."
"Converting a task into an epic is very troublesome."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"The interface JIRA Portfolio could improve."
"Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved."
"The solution’s pricing could be reduced."
"The reporting capability and access to the fields for our system administrators to have access to the data without having to pay Enterprise One to get the data that's needed to create custom reports for management to create reports need improvement."
"One of the reasons why we've upgraded so many times is because of performance standards. We've just run into issues where we've had performance problems. Maybe they are not upgrading, but they're adding more horsepower. Then, we do go upgrade and lose that horsepower, which is frustrating from my perspective as an admin to lose that horsepower. Hopefully, that'll change."
"It is not an end-user-friendly product, and that's really the biggest thing. The hardest or the biggest hurdle I've ever had to face was adoption. I did the installation of the HP product in 2011. The company used it from 2011 to 2015, and the adoption was very high. When I was given the Planview product, adoption was very low. It wasn't as extensively used. We actually had people who wanted to go back to HP PPM because the interface of Planview was so broken, and it still is to some degree. So, it is not user-friendly. It doesn't flow the way a project manager thinks. What we did with HP PPM was a lot more manual programming. It wasn't as nice in terms of the interface, and it wasn't as pretty, but you could design it and build it so that everything flows with the way you worked, but Planview doesn't quite do that. There are a lot of screens. You have to jump back and forth. There are so many different places you have to go to just to do some basic tasks. That's the biggest thing that has really hindered adoption."
"The scheduling's kind of clunky in terms of its ability for us to see what stage work is at. They could have done better with that. It can be difficult to use."
"Its support to legacy paying customers is something PlanView is not handling well. We were unable to implement due to lack of professional support by PlanView. "
"The solution out-of-the-box that we established was insufficient. We had to purchase and set up OData. I don't believe that it's a great solution out-of-the-box but eventually you can get there."
"When you think of planning at a PI level, roadmap planning, or release planning, I think they should make a little more headway into how agile delivery works, tying it back into the financials and the planning to Planview. I think it would be good."
"The reporting is absolutely shocking. It's not good reporting and requires improvement."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 55 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. JIRA Portfolio is rated 8.2, while Planview Portfolios is rated 8.0. The top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". On the other hand, the top reviewer of Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Azure DevOps, Microsoft Project Server and Smartsheet, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, Planview ProjectPlace and Planisware. See our JIRA Portfolio vs. Planview Portfolios report.
We monitor all Enterprise Agile Planning Tools 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.
