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.

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.

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.

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.

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 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.

There were suggestions for improvements and enhancements in Planisware.

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.

Historically, some releases--even with extensive delays from initial announcement--had minor, yet troubling glitches. Planisware Enterprise has been addressing this shortcoming with more frequent releases that include helpful improvements. 7.0.0 release was January 2021; 7.0.1 March 2021; 7.0.2 July 2021; 7.0.3 December 2021; 7.0.4 March 2022. 7.1 became available in September 2023. Documentation has become much more thorough and clearly illustrated. Release notes for 7.0.4 has 133 pages. In my experience, small irritations I reported in E7 have been fixed in several days.

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."

Investing in local capabilities on your customer side is vital--both for technical configuration and functional administrators. Over-dependence on the vendor can be needlessly expensive.

Discussions with fellow Planisware customers conclude that commitment to achieving and sustaining product proficiency across versions 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).

One function I have requested for P6 and continuing through E7 is a comprehensive, detailed listing of attributes across modules--somewhat similar to attribute display in OPX2 versions (pre-P5). Some few attributes (e.g., Z-order) are difficult to document completely. Pull-down list of hundreds of attributes is insufficient.

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.