We performed a comparison between Jira and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Project Portfolio Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view."
"It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
"I have found Jira to be stable."
"Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on."
"It's easy to deploy."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"We're still in an early stage. Things will change as we use it more. I did program reports that are important and that will provide us with value."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"The most valuable feature of this solution is reporting."
"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."
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool."
"The portfolio and technology management are well built."
"We can easily see which functions are overcapacity. Before, we did not have visibility into that."
"The most valuable features are the resource management, the time sheet entry and usage, and the financial planning. With our projects, we primarily focus on resource assignments, as far as determining the actual forecast and actuals of our projects. A lot of it is based off of the resources utilized on those projects. The time based helps us capture the actuals. The amount of time people are spending on working on their project tasks. Because they've built this into the schedule, so we can build the forecast. With financial planning, we're able to look back on what our variance is and if there is anything between the scheduled forecasted hours, dollars against the actual hours, and the costs that they utilize."
"We'd like to see Jira have more integration with a development ID."
"It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"The solution could improve by having its own tool for quality lifecycle management."
"The hierarchy for Jira tickets is too flat."
"Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people."
"Jira could be easier to use, especially for administrative tasks. It's quite complex, so it's important to understand it well. While the reporting and dashboards are good, there's room for improvement in some areas where extra features would be helpful."
"I think some of the administrative aspects of it could be a little easier, especially when it comes to designing reports. The reporting coming out of it could be a little bit better."
"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."
"Our challenge will be this tool is complex. It is not necessarily easy to start and learn from the beginning. How do you get people who are not professionals to adopt it, use it, and not be mean about it?"
"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."
"Visualization and reporting areas could use improvements by having canned reports."
"One big issue we have been having during our annual planning is that only the creator of a portfolio can edit it. This means that only the creator of a portfolio can edit which projects are included or excluded in it."
"The solution is stable. However, it's so robust, there's so much data, that it has the tendency to lag."
"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."
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 258 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. Jira is rated 8.2, while Planview Portfolios is rated 8.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 Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, SAP Portfolio and Project Management and Adobe Workfront. See our Jira vs. Planview Portfolios report.
See our list of best Project Portfolio Management vendors and best Project Management Software vendors.
We monitor all Project Portfolio Management 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.
