Planview Portfolios is an end-to-end project portfolio management and enterprise architecture management tool. It includes two components: Portfolio and Resource Management and Capability and Technology Management. The platform is available as a cloud-based or on-premise service.
Planview and Microsoft Project have many similar features. However, the direct contact with the Planview team for questions, tech support, and training is unprecedented and appreciated. Microsoft Project: -Weaknesses: Limited to single project management, lacks risk and time …
Planview Portfolios is the market leader in the area, the flexibility of the product and the continuous investment by Planview makes Planview Portfolios currently the best in the market. The support organisation for implementation and run of Planview Portfolios rounds off the …
We are just in the process of deploying AgilePlace and will connect with Portfolios Smartsheet, which does have the functionality we need. We are just starting to use AgilePlace. We have a business group doing a proof of concept.
Planview has been growing continuously in the last decade or so, and its acquisitions of some big players in the market have imparted much-needed confidence in the tool. The ability to integrate Planview using APIs, Snap Logic, or Planview's own tool, 'Hub,' makes it stand out …
We are currently in the process of evaluating but so far Planview seems to fit our needs the best. Portfolios was selected prior to me joining the team.
Planview Portfolios has an extremely robust data structure that supports many different use cases. Its customizability, large suite of features, and great customer service makes it a fantastic and scalable solution for many different businesses and business process …
Planview has much more potential in terms of it's products and capabilities. It can integrate more easily with many more of our other products and software. Planview reporting is much more intuitive.
Clarity is significantly more configurable and more intuitive. When implementing Clarity, you do have to be careful not to configure too much- if you do, the canned reports will not work.
I was not on the team that selected Planview Portfolios.
I like Epic when I was a scheduler because of it's user-friendliness and eye-catching layout. Planview Portfolios is better suited for the work function that I currently am in.
We find Planview Portfolios gives us a better platform to work with projects and with the use of Planview ProjectPlace can run our stand-ups and interact with the cards on the boards more readily.
We are currently using Planview AgilePlace. Also we use Tasktop Hub for integrating with other applications within the organization. We would like to use ProjectPlace which is integrated with Planview Portfolios in the future.
Planview Portfolios allows the ability to establish strategic goals, set financial targets, and then associate work so that business areas can easily see current forecasts compared to baselines. Lower-level resource management is handled nicely within Portfolios, allowing Resource Managers to pivot the assignment data quickly to do a variety of analyses. There is room for improvement in the ease of connecting Ideation to Delivery. Companion tools are available but it does not flow smoothly between applications. I would rather have Ideation embedded within Portfolios so that projects can be created/aligned more easily.
Capture potential opportunities using the Requests Module and analyze and rank these opportunities via lifecycles and promote (dispatch) approved opportunities into Projects. Information captured during the request process automatically get transferred to projects.
Robust schedule management; time reporting; resource management and financial planning and management
Risk and Issue management controlled via robust lifecycles.
Extensive reporting capabilities via SSRS and Power BI Dashboards and delivered to users via tiles in Project and Portfolio views.
this is the area I can see Planview Portfolios is very much lagging behind. If you see Atlassian, they are having a robust API information and using that we can securely access the necessary information based on the role. I think a similar kind of approach need to done in Planview Portfolios as well.
User Information and Resource information is separate. Expecting that, during the User creation, when a resource is linked, automatically all the basic fields should be populated with the values, also if a person is having an User account there is no way for that person to know that what User role that he/she is having. Also none of the reports covering that details.
Automation - It's mentioned using the UiPath some of the Automation has been done in the User creation but don't find any necessary document for better understanding.
We have been a Planview customer since 1999 and have seen it grow and mature as a tool. We have looked at other tools and have found that PV continues to meet our needs and is easy for our resources to use. They work to stay up on the project management industry and the direction it is going, keep on on current technology so that we can work more effectively, provide excellent customer support and have great pricing for what they offer. We can purchase only the modules we need versus buying a tool where we would only use a portion of the functionality.
There is a learning curve that needs to be overcome for new and occasional users. Need to clearly training users on how to filter the data with "Portfolio's"
We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
Going through proper channels of support is fine for minor to moderate issues. However, lately the critical issues that arise have been frequent and the standard support cases do not always seem to relay just how critical these issues are and we have to utilize our customer rep to help escalate. Fortunate to have that escalation method.
Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
Odoo, like this platform, has allowed us to efficiently organize our projects so that they can be prioritized by importance, to know which is the most urgent, in addition, it has also allowed us to assign work in an organized way among our collaborators, and their reports have allowed us to improve.
The positive impact is the ability to manage our projects enterprise wide.
Managing and reporting on projects and programs via portfolios makes it easy to identify troubled projects/programs that need immediate attention.
The negative is that pushing too much change too quickly is hard for us. We need to get our users focused on the basics of PM before we can adopt everything else. We need to introduce change to different companies based on their maturity level. Too much change too quickly is not always beneficial. We need to focus on core competencies.