We performed a comparison between Jira and Planisware 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."It includes by default all the necessary tools for a project manager to work and make their work more efficient."
"Jira offers tools for managing projects using Agile methodology. I think it is good to encourage the development team to use Jira, so that the organization benefits from the proper execution of projects on time. Basically, it helps our organization to execute in a better way."
"The most valuable feature of Jira is the project package for development."
"The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"We can integrate a lot of tools with the solution."
"The initial setup isn't too complicated."
"This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page."
"The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening."
"The solution is performance-oriented and easily customized accordingly to many areas, such as performance KPI."
"It stands out by automating the intricate mechanics of project execution, eliminating the need for highly technical individuals to manage and reconfigure models."
"Overall, our company has all disintegrated systems, and with Planisware, we are getting a very integrated view of my portfolio reporting, cost and load, and everything else."
"The area that could benefit from improvement in this Planisware is the project management tool. I have previously used Project Server, which is a Microsoft solution, and I found it to be more user-friendly as it included a client solution. In contrast, with this solution, the only option available is the online version, making it difficult to create activities, milestones, and other necessary components. This is in comparison to Planisware, which offers a more comprehensive solution."
"We have a variety of different modules, but it is mainly used for costs, risks, and resources."
"There are two things in particular that I enjoy. The first is the portfolio planning section. Another advantage is that it is highly customizable."
"It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray."
"Whenever you edit a story, whatever you have changed takes a bit of time to save."
"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."
"If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
"For me, the solution is too complicated as it has too many features. It would be nice if they could streamline things."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"I also wish Jira had an indicator to tell you that you are approaching the limit for the story points that can be delivered during a sprint. I don't think there is an indicator like that, but such an indicator will be very helpful because then I will be easily able to see that we are approaching the limit."
"The area that could benefit from improvement in this Planisware is the project management tool. I have previously used Project Server, which is a Microsoft solution, and I found it to be more user-friendly as it included a client solution. In contrast, with this solution, the only option available is the online version, making it difficult to create activities, milestones, and other necessary components. This is in comparison to Planisware, which offers a more comprehensive solution."
"More integration is needed with other kinds of products for better collaboration."
"They do not have anything that can assist customers with multi-year roadmap planning."
"The learning curve is steep and there could be more avenues for opening up learning materials to a broader audience, enabling individuals to gain practical experience with the tool."
"Its stability should be improved. Its stability is the main issue, but we sometimes also have issues with calculations."
"The solution's user experience and user interface need improvement because they are not that great and intuitive."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 263 reviews while Planisware is ranked 6th in Project Portfolio Management with 10 reviews. Jira is rated 8.2, while Planisware 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 Planisware writes "A comprehensive project and portfolio management with robust scalability and dedicated long-tenured support team". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Planview AgilePlace, whereas Planisware is most compared with Microsoft Project Server, Smartsheet, Planview PPM Pro, SAP Portfolio and Project Management and Asana. See our Jira vs. Planisware 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.
