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.

I do not have experience with Planisware's advanced reporting capabilities as we use other tools.

In my opinion, Planisware could be improved, particularly in the reporting area.

The reports should be improved because all companies now need reporting, and with tools such as Grafana or Tableau, Planisware needs to add interfaces for data lakes since all companies require this.

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.

Planisware’s technical support process can be quite challenging, as it often takes significant time and effort to reach the right point of contact for issue resolution.

We have occasionally experienced system crashes and performance slowdowns, which can impact productivity during peak usage periods.

However, with the upcoming releases introducing interface enhancements, we expect improved usability and stability. At this stage, I don’t have any specific changes to suggest until those updates are fully rolled out.

I appreciated the way the project has been managed in Planisware, though the communication is missing. If I compare Planisware with Asana, I appreciate the templates in Planisware. It has brief information about the project, and assigning that project is also good. But internal chatting and internal assigning work was not seen in Planisware, which I could see in Asana more.

I appreciated the dashboard in Planisware that I used to maintain, but it can be more organized. Though I can maintain the dashboard, I would prefer a more personalized view; if it is my project, I should see only my project dashboard, which was missing. I was getting many notifications which were also there. I am unsure whether it is me who does not know how to organize my dashboard or if it's common for everyone.

I utilized the resource management feature in Planisware, and it was good. When I used to take out the entire month Excel sheet of resource management timekeeping, what they entered and what we receive in an Excel sheet has a conflict. I have raised this concern. When we take out an entire month PDF, it shows different information. I don't know how this error was occurring.

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 not employed in client-customer organizations to advance their practical hands-on experience with Planisware Enterprise. 

Functional administrators would benefit from more tailored versions of current superuser technical access, which is essentially everything in an environment's configuration. Functional administrators need to ongoing adjustments to enterprise content without forcing updates in names, roles, labels, to flow to a technical superuser. 

Agile methodology has matured and become widespread to warrant "out of the box" rapid acccess rather than depending upon local administrators to tailor traditional project management structures.

The UI and UX of Planisware are not that advanced, similar to SAP. Additionally, there are some bugs and open ends in the system, and it's an expensive tool.

I haven't had the time to work with any other TPM tools, so I can't compare it to other tools just yet.

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.

There were suggestions for improvements and enhancements in Planisware.

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 biggest con for Planisware is that if you are not a Planisware partner, you don't have access to their functions, making it difficult for beginners and new team members. There's also a concern with the on-premises version related to server boot-up times, which can be lengthy.

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.

7.0.4 already improved documents management to centralize communications among project users and stakeholders. Because the documents are included in each Planisware environment/configuration, messaging and documents associated with projects are easier to access than being spread through normal corporate email. Planisware stores project related documents and messages in a single database. Snapshots (backups) at a given point in time are easy to make and restore to alternate environments, even on an automated nightly basis.

Program and project roadmaps integrate well with PowerPoint. Slide elements are editable and dynamically linked (if so specified) to detail projects. Capability to drill down into project specifics is mature, native functionality.

Strategic Portfolio module offers an OKR page (objectives and key results) to connect specific company strategy with defined measurable actions.

Knowledge findability and sharing concerning advanced Planisware implementation, deployment, and problem resolution receive modest peripheral attention and low priority from Planisware for pre-client (customer) access. Once your organization commits to an implementation contract for Planisware Enterprise, pathways for answers become more abundant.

Planisware helpfully distributes incremental updates about three times annually. Extent of the client base and collective user expectations push priority improvements into new versions and resolve rare technical glitches rapidly. What any single user or small client may earnestly request for increasing productivity may take years for development to start—unless one pays rather dearly for underwriting special services from Planisware’s offshore support group.

Neglect of formerly active users
Planisware has been a profitable business and attends well to paying clients. Individual users, particularly those who suddenly lack affiliation with a paying client between jobs have been bottom priority in my experience. Service tickets don’t apply for this category of formerly active users.

Recognizing expansive growth in the worldwide Planisware user community, Planisware should address this continuing education defect.

I recommend that Planisware provides formerly active users privilege of connectivity with Planisware “playground” environments that are periodically refreshed with a current release version. This new option would cultivate “hands on” proficiency in the overall Planisware user community.

More integration is needed with other kinds of products for better collaboration.

I would like to see improvements in the following modules:

• Resource
• Project
• Portfolio
• Timecard

Reporting out of PLW has been a definite weakness. But the recent PEX module is addressing that issue quite nicely, even if the product is still being improved.