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 most valuable feature of the JIRA Portfolio is for managing teams of 10 or more. It can track the program level and portfolio. There are plenty of beneficial features, such as the hierarchy-level view, customization, and structure plugin."
"The solution is very stable."
"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 developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"The integration is very good. We've more or less integrated with everything including reporting and registering."
"The solution includes good and fast notifications for other project team members."
"The solution has good reporting and is very user-friendly."
"Managing product development and managing inter-team communications are also valuable features."
"When it comes to managing project plans, Enterprise One is awesome at enabling us to see what stage work is at. I've always thought it was awesome because it's good whether we're doing a traditional WBS or we're linking in epics into projects that are supporting the programs and the strategies, I've always thought it was an excellent tool."
"I like that the data that we store is available for everybody. We're not trying to hide anything. Being an administrator, I know a lot about the tool. It is very easy to show somebody how to use the tool and get used to it. Hopefully that user doesn't come back and ask the same question twice is really what it is about. It's a very intuitive product as well. For what we use the tool for today, it's easy to learn and pick up."
"In my opinion, the financial planning feature is the most valuable feature of Planview Enterprise One."
"Another good thing is that we can create custom reports, which is great. If I created a custom report, a tile that tells me how many people have logged in today. We currently have a little under 2000 users, and that's only users, we actually have integrations, that we created a custom form that sends hours directly to Planview. They're not using Planview directly, but they're sending their hours to Planview through an API."
"The most valuable feature of this solution is reporting."
"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."
"It gives us the vast ability to churn out-of-the-box reports and have an overview about approach rates and resource utilization."
"It has helped improve governance, mostly. People want to know where their money's going. Projects sponsors need to know what we're spending money on and what our burn rate is. Planview can give that to you straightaway."
"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."
"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."
"n the next version I would like to see better reporting and safer plugins, as well as easier scalability."
"The solution’s pricing could be reduced."
"In the next release, Portfolio should include more metrics and develop their portfolio planning."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"The HR aspect of the solution could be improved."
"An improvement would be if Portfolio were integrated with Office 365."
"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."
"Configuring the UI in the content management system is too elaborate and too time-consuming."
"The lack of templates harden the initial learning curve."
"We don't use the Progression feature. We will use it at some point in time. Until then, we want to have a way to set time to help decide what's in the past, present, and future. It is one of the things we've been discussing with Planview."
"Visualization and reporting areas could use improvements by having canned reports."
"Its ability to create summary reports across multiple projects is very limited. In terms of the out-of-the-box reporting for summary reports, the reporting that we typically leverage is around forecasting for resources, timesheets, and actuals, and just looking at what is the capacity. There is no real summary of what work is being done and how work is being accomplished. So, what we typically do is that we get a copy of the data files from Enterprise One daily, and then we have a team that manages the data mod outside of Enterprise One. They use data from Enterprise One as well as other additional sources to provide the reporting that we share with the management. So, we leverage a lot of Enterprise One data for reporting, but we don't use the reporting capabilities within Enterprise One. So, reporting can be improved, and they could help us make more customized reporting. I know it is very configurable out of the box, but we have to leverage an outside data mod that pulls in a lot of data from Enterprise One. So, the reporting function, and being able to customize reports, is the area that could be very beneficial."
"I think the capabilities are there, but it seems difficult for me to even create a report as I am not a Planview technical expert. It is not particularly intuitive. It slows us down in reporting the big picture to management."
"There are some issues with how long it takes to load the data to Planview, It just depends on what your setup is. If there was a way Planview could maybe make the loading faster, in case you do have a lot of things going on with your setup."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 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 Project Server, Adobe Workfront and Microsoft Project, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, SAP Portfolio and Project Management and Basecamp. 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.
