Try our new research platform with insights from 80,000+ expert users

Planview Portfolios vs Serverless comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Planview Portfolios
Ranking in Enterprise Architecture Management
11th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
63
Ranking in other categories
Project Portfolio Management (7th)
Serverless
Ranking in Enterprise Architecture Management
15th
Average Rating
7.6
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Enterprise Architecture Management category, the mindshare of Planview Portfolios is 2.3%, up from 0.9% compared to the previous year. The mindshare of Serverless is 0.1%. It is calculated based on PeerSpot user engagement data.
Enterprise Architecture Management Market Share Distribution
ProductMarket Share (%)
Planview Portfolios2.3%
Serverless0.1%
Other97.6%
Enterprise Architecture Management
 

Featured Reviews

it_user1684173 - PeerSpot reviewer
PM Systems Analyst at a insurance company with 5,001-10,000 employees
Increases our on-time completion rate and helps in managing the demand and capacity, and we get excellent service in terms of feature requests and support
We've been encouraging our users to manage their schedules directly in the Work and Assignments module. So far, it has been good, but we've been in conversation with the vendor product team to improve the performance of the Work and Assignments module. Right now, it is a bit slower. We don't use the Progression feature. We will use it at some point in time. Until then, we want to have a way to set time to help decide what's in the past, present, and future. It is one of the things we've been discussing with Planview. It provides flexibility for configuring assignments, but one of the things about which we've been talking to Planview is related to certain resources that are associated with a project. When the project extends, their demand also equally goes up. There are also resources where if a particular task has to crash, it may need additional effort. So, it is between the fixed effort versus fixed duration. Planview is more duration-based. For example, if you crash a task, the system rightly thinks that you're crashing the task, and you need to finish the work by doing overtime or working additional hours. If you are taking 30 hours to finish a task in three weeks, and for whatever reason, you have to crash the task into two weeks, 30 hours need to be fulfilled within those two weeks. If the task moves to four weeks, instead of three weeks, you still have 30 hours that get distributed among four weeks, so you will be able to finish the task. That makes sense for those resources that are associated with the task, but there are certain resources, such as a project manager or project administrator, for whom when a project extends, the demand also equally goes up. So, if somebody is assigned 50% for a project, and assuming that the project is moving out by a month or two or three months, the effort shouldn't go down. Currently, the allocation goes down, and our resource managers have to go and update the effort back up to 50% or whatever the demand is. We are interacting with Planview to provide a solution. Right now, we have to go and update the additional demand because of the change in the project.
TC
Sr. IT Engineer at Best Western
Server management headaches have disappeared and deployment of APIs is now fully automated
My advice to others looking into using Serverless is that you don't need to worry about the server maintenance, the servers, and where you host the servers. All these headaches go away. Definitely it's good to use. All the headaches that we have been doing for all these years can be gotten rid of, definitely. This has been a great initiative taken by AWS. Previously, we thought that we cannot host our applications without any server, but AWS proves us wrong by creating a Serverless application, the option to deploy our applications without any server. This is a really great initiative done by AWS. I rate this solution an eight out of ten.
report
Use our free recommendation engine to learn which Enterprise Architecture Management solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
15%
Financial Services Firm
9%
Healthcare Company
8%
Insurance Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise59
No data available
 

Questions from the Community

What do you like most about Planview Portfolios?
Planview Management integrates seamlessly with other tools and systems used within the organization, such as enterprise resource planning (ERP) software, customer relationship management (CRM) syst...
What needs improvement with Planview Portfolios?
Enhancements are needed in: Advanced reporting and analytics: While Planview Management provides robust reporting and analytics capabilities, further enhancements could include more advanced data v...
What is your primary use case for Planview Portfolios?
We use Planview Management to assess the current project portfolio, evaluate resource availability, and prioritize projects based on strategic objectives, ROI, and risk factors. Planview Management...
What is your experience regarding pricing and costs for Serverless?
My experience with pricing, setup cost, and licensing is that some of these are done by my solutions architect and I will not have enough information about that in my current role as a product mana...
What needs improvement with Serverless?
I struggled with wanting to put breakpoints throughout the code and then use the debugger. At the time, I was not able to step through the code with breakpoints, so if Serverless had that support, ...
What is your primary use case for Serverless?
Our main use case for Serverless is to build Serverless APIs, and the complete back-end is built with Serverless. A specific example of an API or back-end workflow built using Serverless is a parts...
 

Also Known As

Planview Enterprise One, Troux
No data available
 

Overview

 

Sample Customers

UPS, NatWest, Ingram Micro, Canadian Tire, Viessmann, Volvo, NASCO, UNESCO
Information Not Available
Find out what your peers are saying about Planview Portfolios vs. Serverless and other solutions. Updated: January 2026.
881,082 professionals have used our research since 2012.