The tool can be improved with integrations to Agile tools. We used Azure DevOps, which I dislike. Better integrations to JIRAs and perhaps open APIs for task management would be super beneficial. As a project management tool, it is perfect, but the ability to be agile with task management could improve it. There is always an opportunity for more flexibility regarding integrated reporting. The project dashboard feature worked perfectly for small to small-medium projects, but on a large scale, it was not flexible enough to handle a program-level dashboard. However, that is probably a nice-to-have rather than a need-to-have. The integrations to Agile are essential; we had to do a full build to accomplish that.
Solution Architect | Planisware Consultant at Schlumberger
Real User
Top 5
Jul 14, 2025
One drawback with Planisware is that it doesn't have good features for test management or agile; it lacks many concepts in agile such as retrospective, velocity planning, and backlog view. Some features are still missing because they have introduced these agile modules only in version seven and are still improving that product, so I see a good roadmap on those modules from Planisware's end. I find Planisware's collaboration tools to be good but not great as they still have certain restrictions. It can interact with Jira, it can interact with ADO, and you can have APIs created to interact with your internal HR systems or other systems for data flow. However, the error messages or fail scenarios don't provide good visibility of what is happening, why errors occur, or why something is not working. Regarding scenario planning, I haven't explored much on that side. We have the strategic module, strategic planning module, but we haven't explored much on the other side, so I don't have much experience or exposure to scenario planning.
One area for potential improvement in the system lies in accessibility for individuals who are not part of a subscribing company. Learning the system can be challenging for non-professionals due to its cost and the need for specialized training. 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. There is room for a improvement in the pricing.
Delivery Leader : Digital Productivity Studio at a energy/utilities company with 10,001+ employees
Real User
Top 5
Jul 24, 2023
The solution's user experience and user interface need improvement because they are not that great and intuitive. They are too dependent on scaled agile for their Agile and Epic road map module. Organizations that do not follow a scaled agile framework might follow something different, like a scrum of scrums. There is still scope for improvement in this area for the solution.
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. Additionally, the reports could be better. It is difficult to extract and build dashboards.
Practice Head - Wipro Digital - PPMS at Wipro Limited
Real User
Jul 4, 2022
They do not have anything that can assist customers with multi-year roadmap planning. A feature that allows you to capture details about what kind of roadmap you have for the next phase, three years, and then track at the CIO or management level, is one thing that is lacking, and an area they can work on it.
PMO - Senior Project Management Consultant at a consultancy with 51-200 employees
Consultant
Feb 14, 2022
Its stability should be improved. Its stability is the main issue, but we sometimes also have issues with calculations. In terms of additional features, it already has a lot of modules, so it's enough for us at this time.
Historically, some releases--even with extensive delays from initial announcement--had minor, yet troubling glitches. Planisware now has sufficient critical mass to retain additional qualified personnel for improved regression testing. Version 6.3 benefits customers from Planisware's intensified commitment to robust quality assurance. Planisware downplays customer use of Pro Web (L2) by emphasizing that substantial configuration capability is available in Intranet Server (L1). With SaaS service agreements, access to L2 for production environments is essentially forbidden for customers in order to maximize contracted uptime. On the positive side, L1 capability is becoming more extensive in V6.3, reduceing user need for L2 access. SaaS provisions that Planisware provides in relation to security are superior to what smaller organizations can afford. Planisware SaaS no longer relies upon third-party providers. Faster data response time is a user benefit. Availability of Planisware software as a service (SaaS) contributes to operational stability; your team still needs to keep the configuration responsive to evolving business needs. Each customer has responsibility for continuing to grow "know why" as well as "know how." In my experience and discussions with fellow Planisware customers for almost two decades, commitment to achieving and sustaining deep product proficiency is a key best practice. At cost Planisware certification courses can provide training for a corporate customer's advanced users (those responsible for maintaining L1 level changes). Here is a longterm issue to weigh: When only Planisware's staff makes operational and development changes to your production environment, technical capabilities on the customer side may not mature, resulting in over-dependence on the vendor. If your company is prepared to pay a premium for ongoing consulting on your organization-specific configuration from Planisware, that may be workable for your specific circumstance. That cost is above and beyond the SaaS maintenance. Planisware decision makers have not placed priority on product changes or evolution requests that are not customer facing. For example, in Pro Web, control-A highlights visible lines for copying, but in my experience, only 300 or so lines actually copy in one operation. This fragmentation is supposedly ample for developers.Waiting for Planisware resolution--copying like the Pro tool in prior versions--may take many years, if ever. Some longstanding legacy features introduced in OPX2, such as update and deletion macros, are not available in Planisware Enterprise. Future releases may "restore" macro functionality. V6 can be addressed via mobile devices; having large monitor(s) provides better data visibility.
Planisware offers powerful project, resource, and portfolio management, acclaimed for adaptability and integration capabilities, especially in complex R&D projects, data centralization, and business case prioritization.Planisware stands out with its advanced reporting tools, customizable views, and agile management. Equipped with an inbuilt BI tool, it enhances data analysis without external applications. Organizations appreciate resource capacity planning, scenario planning, and...
The tool can be improved with integrations to Agile tools. We used Azure DevOps, which I dislike. Better integrations to JIRAs and perhaps open APIs for task management would be super beneficial. As a project management tool, it is perfect, but the ability to be agile with task management could improve it. There is always an opportunity for more flexibility regarding integrated reporting. The project dashboard feature worked perfectly for small to small-medium projects, but on a large scale, it was not flexible enough to handle a program-level dashboard. However, that is probably a nice-to-have rather than a need-to-have. The integrations to Agile are essential; we had to do a full build to accomplish that.
One drawback with Planisware is that it doesn't have good features for test management or agile; it lacks many concepts in agile such as retrospective, velocity planning, and backlog view. Some features are still missing because they have introduced these agile modules only in version seven and are still improving that product, so I see a good roadmap on those modules from Planisware's end. I find Planisware's collaboration tools to be good but not great as they still have certain restrictions. It can interact with Jira, it can interact with ADO, and you can have APIs created to interact with your internal HR systems or other systems for data flow. However, the error messages or fail scenarios don't provide good visibility of what is happening, why errors occur, or why something is not working. Regarding scenario planning, I haven't explored much on that side. We have the strategic module, strategic planning module, but we haven't explored much on the other side, so I don't have much experience or exposure to scenario planning.
There were suggestions for improvements and enhancements in Planisware.
I haven't had the time to work with any other TPM tools, so I can't compare it to other tools just yet.
One area for potential improvement in the system lies in accessibility for individuals who are not part of a subscribing company. Learning the system can be challenging for non-professionals due to its cost and the need for specialized training. 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. There is room for a improvement in the pricing.
The solution's user experience and user interface need improvement because they are not that great and intuitive. They are too dependent on scaled agile for their Agile and Epic road map module. Organizations that do not follow a scaled agile framework might follow something different, like a scrum of scrums. There is still scope for improvement in this area for the solution.
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. Additionally, the reports could be better. It is difficult to extract and build dashboards.
They do not have anything that can assist customers with multi-year roadmap planning. A feature that allows you to capture details about what kind of roadmap you have for the next phase, three years, and then track at the CIO or management level, is one thing that is lacking, and an area they can work on it.
Its stability should be improved. Its stability is the main issue, but we sometimes also have issues with calculations. In terms of additional features, it already has a lot of modules, so it's enough for us at this time.
More integration is needed with other kinds of products for better collaboration.
Historically, some releases--even with extensive delays from initial announcement--had minor, yet troubling glitches. Planisware now has sufficient critical mass to retain additional qualified personnel for improved regression testing. Version 6.3 benefits customers from Planisware's intensified commitment to robust quality assurance. Planisware downplays customer use of Pro Web (L2) by emphasizing that substantial configuration capability is available in Intranet Server (L1). With SaaS service agreements, access to L2 for production environments is essentially forbidden for customers in order to maximize contracted uptime. On the positive side, L1 capability is becoming more extensive in V6.3, reduceing user need for L2 access. SaaS provisions that Planisware provides in relation to security are superior to what smaller organizations can afford. Planisware SaaS no longer relies upon third-party providers. Faster data response time is a user benefit. Availability of Planisware software as a service (SaaS) contributes to operational stability; your team still needs to keep the configuration responsive to evolving business needs. Each customer has responsibility for continuing to grow "know why" as well as "know how." In my experience and discussions with fellow Planisware customers for almost two decades, commitment to achieving and sustaining deep product proficiency is a key best practice. At cost Planisware certification courses can provide training for a corporate customer's advanced users (those responsible for maintaining L1 level changes). Here is a longterm issue to weigh: When only Planisware's staff makes operational and development changes to your production environment, technical capabilities on the customer side may not mature, resulting in over-dependence on the vendor. If your company is prepared to pay a premium for ongoing consulting on your organization-specific configuration from Planisware, that may be workable for your specific circumstance. That cost is above and beyond the SaaS maintenance. Planisware decision makers have not placed priority on product changes or evolution requests that are not customer facing. For example, in Pro Web, control-A highlights visible lines for copying, but in my experience, only 300 or so lines actually copy in one operation. This fragmentation is supposedly ample for developers.Waiting for Planisware resolution--copying like the Pro tool in prior versions--may take many years, if ever. Some longstanding legacy features introduced in OPX2, such as update and deletion macros, are not available in Planisware Enterprise. Future releases may "restore" macro functionality. V6 can be addressed via mobile devices; having large monitor(s) provides better data visibility.