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 user interface is simple."
"We have the best community to support any problems that we have."
"All departments can work with the same platform."
"The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"We use Jira for project management and tracking."
"The feature that I have found most valuable is that it is a quite powerful user tracking system."
"I found it super useful, as it is customizable for different teams and users."
"The features on offer are great. It has everything we need."
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool."
"The solution’s integrated product portfolio has transformed our organization’s delivery because people are a lot more accountable. When you have no accountability, then people don't always deliver the way that you want them to. Once you get accountability, they know that somebody is watching and the way that they manage their work changes quite a bit."
"The most valuable features are the control and visibility that you have for portfolio management in terms of projects and capacity planning for resources along with strategies and outcomes, etc. It's so easy to access information for sharing analytics and reporting."
"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."
"The resource capacity planning is the most valuable feature because you can evaluate your team's capacity by team and what projects they're working on and you can forecast easily by team."
"The biggest impact has been getting all these global groups into one space so we can even have intelligent conversations about what are we trying to accomplish. Before, it was just different regions doing whatever. Now, we're all talking the same language, and that's good."
"We are able to see where everyone in the team is in terms of hours, where there is capacity, and where we can actually add them, e.g., other projects that they're not currently staffed to."
"The resource management and assignment features are valuable. The timesheet management is also valuable because that is a requirement for us. So, the ability to see timesheet forecasting and timesheet actual submission from resources has been very useful and valuable to us."
"The history with Jira is that it is a bit complex for many users."
"In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray."
"Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas."
"In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."
"I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports."
"Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it."
"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."
"The only area that I can see currently needing improvement is just the modernization of the look and feel of it."
"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."
"Their off-shore support is something new that they're laying out and the team just needed some development in terms of skill and experience."
"I think that the user interface needs some getting used to. It's not immediately intuitive. That's potentially room for improvement. I think also that an organization needs to have good support from some senior management to get something like Planview established."
"I would like to see more documentation pieces. Right now, they do have the content repository. I would like to see more out-of-the-box features with document repository capabilities."
"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."
"We had issues with the data rephrasing."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 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, Planview ProjectPlace and Wrike. 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.
