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.
N/A
ServiceNow IT Service Management
Score 8.6 out of 10
N/A
Built on the ServiceNow Now Platform, the IT Service Management bundle provides an agent workspace with knowledge management, and modules supporting issue tracking and problem resolution, change, release and configuration management.
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 …
Verified User
Professional
Chose Planview Portfolios
In our organization we selected Planview Portfolios for the capabilities it offered.
Planview is extremely customizable and user friendly. I feel their tool is intuitive to use and their customer support team is very engaged and helpful when called upon. We selected Planview based on overall cost and longevity in the PPM space. All the other tools we …
Senior Analyst, End to End Enterprise Architecture - Corporate Functions
Chose Planview Portfolios
Comparing ServiceNow ITBM and Planview is difficult, as they are really different offerings. ServiceNow offers a great platform to management applications from a pragmatic and tactical vantage, keeping it close to those operational teams who need it. Planview takes it up a …
We made the tool selection back in 2002. Most competitors are now gone or purchased by someone else. At that time they were one of the few companies who had a somewhat mature and configurable budget module. We were also coming out of an Access environment, so we were …
Troux has the most complete and up-to-date feature set, which also includes the ADM cycle of Togaf. It's designed for Strategic and Tactical IT planning and managing IT portfolios. In certain cases other products only cover one aspect while Troux covers all the aspects in a …
ServiceNow leads the industry for a reason, they are simply the best in the space. The tool is modern, hosted, updated regularly, and has over 1000 out of the box connectors for other popular products. The tool really does it all and provides a ton of functionality to end users …
Planview Portfolios is well suited to provide a single, central, view of the truth. There is clear expansion capabilities to integrate it as a true Enterprise toolset with existing organisation wide (not just delivery) - you can pick and choose what you need to implement and that list gets longer. The ability to quickly gain an understanding of resources within the overall portfolio and some really clever tools regarding capacity and demand modelling. I think the only challenge we have encountered is modelling our Business as Usual activity to a level of detail - this is due to other tools being very embedded not just in the organisation but across a lot of industries.
In our organization, we are using ServiceNow extensively. Change Management, Incident Management, Problem Management, Time tracking are few modules which we use extensively. This sort of model will work for any product or service based companies as the product is built on ITIL framework. So this product will be suited for small or large scale companies to better organize and add controls and track SLA's for technology or business process.
When I have a number of requests to make, for example a request to add a dozen or so user accounts to more than one group account in Active Directory , I can put all the needed information into the initial form, add it to my "shopping cart" and all of that information remains on the screen for the next item for which I only need to edit a few items (like the AD group name in this example), and keep adding them to the shopping cart until I have them all. When I "Check Out" each of those items is generated as a separate task under the one request. It simplifies and expedites the creation and tracking of these kinds of requests.
I can easily and quickly see what tickets are currently assigned to me in order to prioritize them and remain aware of my workload.
Numerous fields for CIs can be used when trying to find the entry for a particular item. For example, IP Address, server name, raw text, classification, and so on.
To help with making sense out of related tasks, when a task is assigned to me and I need to open another task for a different team to work in order to complete my task, I can open a sub-task from my ticket so that the relationship between the two can be pulled up later into reports. For example, I may have a task to build a new vm, and need to open tasks for networking, security accounts, software installation and so on. By opening sub-tasks from my assignment, the time spent by all parties concerned is tied together for more meaningful cost accounting.
It is hard to find areas for improvement, the tool is very powerful. That said, building the CMDB still involves some manual interaction which was not how it was presented in demos.
The CMDB data is almost too deep and detailed. When you build the relationship map it can be so large that it is overwhelming. You can limit this, but the default maps are massive if you are discovering lots of device classes.
The product is expensive. Since they are the leader in the industry and the product has tons of features, they definitely charge for it!
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.
To be completely honest setting up a new ticketing system can be a pain in the ass. Once you have it setup and customized the way you want it, you don't want to switch unless you're unhappy with the product. Unless future releases and updates really muck the system up, I wouldn't change.
The toolset is provisioned as a SaaS solution making it very easy to scale up / down as our user bases increase/decrease. There are some features around the planning capability that could be improved to enable ease of access to our PMs e.g. dependency management (while powerful) dependency management doesn't allow you to add constraints in the same field - you have to click to a separate area
The dashboard is so confusing, [there are] many clicks to open a task and search by a ticket. The Enterprise customisation [we did] has finished to kill the software and creates a really bad experience on a daily basis. [It is] So slow, and so many clicks to process a ticket. Works only on IE so, that [should] make you realize that [it] is a bad idea.
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.
There are occasions when the system is a bit sluggish. However, it may not always be on the Planview side. We are investing in better tools to monitor our network performance, which will help us diagnose issues more effectively in the future.
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.
I would give it this rating because we have had no major issues with the support for ServiceNow after we implemented it at our organization. They seem to respond promptly and efficiently if we ever do need to open a support case with them about an issue we are having.
To type in what should be a text box, you have to click an empty cell, a tiny text box pop up opens with a check box and an X. You the. Type in the text box and have to click the check mark. If you have a bunch of fields to fill out, doing this is very annoying. Absolutely know thought went in to this. I'm sure somebody in marketing thought it was a good idea. It wasn't.
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
Without exception, every client I have worked with has been very happy with their resulting product. While this is partly due to my work, I must point out that the platform is the winning decision, not the implementer.
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.
We used to use Jira to handle service tickets but it's way too robust for something this straightforward. Due to the nature of Jira, you needed to already have a lot of documentation and knowledge about who should be assigned the ticket, so the lift of creating a ticket was time consuming.
We are constantly growing and expanding. It is challenging to accommodate different user needs, but the system does provide means of doing that as we desire.
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.
Overall ServiceNow has a positive impact on getting the SLA of tickets down in supporting our customers.
One negative impact has been the amount of time to get the product to produce an ROI, it's almost too big to fail and too big to replace. You almost become committed to the product. Good or bad.
Another negative impact would be if you track metrics of employees and time tracking, there is a lot of scenarios where engineers will track time on tickets but not get credit for closing them as the assignee function of tickets can only be tied to one user and credits only the engineer who closes the ticket.
Another positive impact would be the level of security for permissions and scaling the workloads is robust and you will get out of the system what your team is willing to put in.
