Planview Enterprise One Overview

Planview Enterprise One is the #1 ranked solution in our list of top Project Portfolio Management tools. It is most often compared to Planview PPM Pro: Planview Enterprise One vs Planview PPM Pro

What is Planview Enterprise One?
Planview Enterprise, Planview's performance management platform, combines project and portfolio management software with adaptive best practices. By integrating the business process management of strategies, services, and projects within a single, Web-based solution, Planview empowers organizations to achieve greater levels of control over their ever-changing environment by dynamically managing money, resources, and capacities.

Planview Enterprise One is also known as Troux.

Planview Enterprise One Buyer's Guide

Download the Planview Enterprise One Buyer's Guide including reviews and more. Updated: January 2021

Planview Enterprise One Customers
Zurich Insurance Group, Zumbotel Group, Carphone Warehouse
Planview Enterprise One Video

Pricing Advice

What users are saying about Planview Enterprise One pricing:
  • "I think all in we are at $33,000 a year and that includes Projectplace and Planview. We used to have the integration to JIRA, but we don't pay for that anymore."
  • "We have unlimited licenses for all of our functionalities. Since we went global, we went with that model."

Planview Enterprise One Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Roderic Person
Planview Administrator and Robotic Process Engineer at a financial services firm with 10,001+ employees
Real User
Top 20
Sep 24, 2020
Provides end-to-end work management for the full spectrum of types of work in one tool

What is our primary use case?

We use it for contractor and associate contracting which reflects directly to project resource, "our spend". We do a calculation based on the vendor that the contractor is through, as well as each associate has a per hour rate that is applied to the project to attract the spend applied to that project from the resources. We also track the number of hours spent per application. Every application in our bank has the application code that we tied back to Planview so that we can track and see how much time is spent within the application, either with upgrades, maintenance or break-fix type of… more »

Pros and Cons

  • "Another good thing is that we can create custom reports, which is great. If I created a custom report, a tile that tells me how many people have logged in today. We currently have a little under 2000 users, and that's only users, we actually have integrations, that we created a custom form that sends hours directly to Planview. They're not using Planview directly, but they're sending their hours to Planview through an API."
  • "The content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created."

What other advice do I have?

The biggest lesson learned would be regarding making sure to have Planview do the training. When we did our training for our organization, we did a train the trainer where Planview came in and trained just a few people in our organization and then they went out and trained their people. But it's like a game where you tell one thing to a person that you pass it down the line and it gets changed by the time it reaches the very end. If you have the budget for it, have Planview perform the training because I think that would increase adoption a lot easier. We had a lot of people who came from…
Keith Kennedy
Project Administrator at Texas Mutual Insurance Company
Real User
Top 20
Sep 24, 2020
Shows us what all of our strategies are, what programs we have under those strategies, what work is happening, and what the current status of that work is

What is our primary use case?

We've been using Enterprise One for a long time and we mainly used it largely for a lot of traditional waterfall, project management, resource management, and things like that. We were just about ready to pull the plug on them but we had a renewed effort in using it. Over the last months or so we've re-engineered it a little so that we can hopefully get a little bit more of the agile use out of it. Being able to balance the old traditional resource management, costing, and stuff like that, with the new agile way of doing things as they were. We do have integration between Enterprise One and… more »

Pros and Cons

  • "When it comes to managing project plans, Enterprise One is awesome at enabling us to see what stage work is at. I've always thought it was awesome because it's good whether we're doing a traditional WBS or we're linking in epics into projects that are supporting the programs and the strategies, I've always thought it was an excellent tool."
  • "I think some of the administrative aspects of it could be a little easier, especially when it comes to designing reports. The reporting coming out of it could be a little bit better."

What other advice do I have?

The biggest lesson I've learned is that there's a lot to it. There's a lot of information, and the big thing is trying to interpret what the information is telling us. I can look at one report one day, and the same report another day and get a different picture. It's just really understanding, especially week to week, what the numbers mean. My advice would be to be ready to work hard, understand your needs, understand your requirements, and understand what information you want to get out of Enterprise One. So that, in working with Planview on a solution, they can tell you what information you…
Learn what your peers think about Planview Enterprise One. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
456,495 professionals have used our research since 2012.
JaymeCalabrese
Director, Office of Process and Project Management at Electronic Arts Inc.
Real User
Top 20
Nov 7, 2019
Organizes work, provides visibility and accountability

What is our primary use case?

We have a smaller organization than some of the other organizations. We have 10 project managers. We manage it for the customer experience division for electronic arts. Therefore, we do only projects wrapped around how to improve our customer experience. Anybody who plays our games, we want to manage those projects to make life better for our customers.

Pros and Cons

  • "The solution’s integrated product portfolio has transformed our organization’s delivery because people are a lot more accountable. When you have no accountability, then people don't always deliver the way that you want them to. Once you get accountability, they know that somebody is watching and the way that they manage their work changes quite a bit."
  • "Our challenge will be this tool is complex. It is not necessarily easy to start and learn from the beginning. How do you get people who are not professionals to adopt it, use it, and not be mean about it?"

What other advice do I have?

The tool is a nine out of 10. Mostly, because I don't give anything a ten. There is always areas of improvement. We have had a lot of pushback when people started up in Planview. I think we're past the cultural part of it. I don't know what makes it difficult. I think it's more difficult than other tools that people have used. I hear over and over that it's not intuitive. Some of it is counterintuitive to the other tools that they've used. Once they get going on it, they're better. The word within our user community is that features are great, but the user interface seems to be very difficult…
Kelly Brummond
Enterprise Portfolio Manager at Wellmark
Real User
Top 20
Sep 27, 2020
A lot of of the value is around the project metrics, strategic planning, and programs and then tying that into outcomes

What is our primary use case?

We have historically used it for resource management and project, so, work management. They're maturing different pieces of the resource management and the work management to leverage some of that. Other use cases that we've started with would be planning, strategies and outcomes. We have it initially built out from a beginning use case and continuing to mature that as we roll out some change in the organization of moving to a strategically managed portfolio, not just a tech portfolio.

Pros and Cons

  • "A lot of of the value is around the project metrics so far but as I get more plugged into the strategic management, it's strategic planning and programs and then tying that into outcomes. I work with executive leadership and that's really what they're looking for, to say, "Okay, what outcomes do we want to achieve and how are we going to get there, plan that out, sequence that out, and then get the work to do that? And then track the work back to where we're headed with our outcomes.""
  • "We've been using it for a while, so it's about maturity. It's about being able to build out things in Agile groups and teams and some of that. Then really trying to drive into the direction of Lean Portfolio Management and more Agile program management, I think is where we're heading."

What other advice do I have?

A big lesson for the organization was not to so prescriptively narrow their opportunities. The way they had it configured prior to me coming on, they had shut themselves off from being able to implement feature capabilities because they had driven out so many restrictive requirements that some of the things couldn't be leveraged. We've been understanding what the capabilities are and where we would like to be, and having a different conversation with Planview when we partnered with them and their global consulting services, to understand what that roadmap looks like, so that we could be guided…
reviewer1208529
Sr PPM Administrator with 5,001-10,000 employees
Real User
Oct 29, 2019
Provides the ability to see your resources and what they're working on in one place

What is our primary use case?

Our company has a PMO, which they use to intake their projects. They use the request module and do a process for the steering committee before its turned into a project. Once they turn it into a project, the project managers take it over and work the WBS all the way through to the end of the project. The product is deployed on the Planview cloud.

Pros and Cons

  • "With the lifecycles, it helps us step through our processes easier. We'll take a process and create it in Visio, then we'll go and implemented in Planview. Anytime that we have to do a new process, this is what we use. We just step it through the lifecycles and the configure screens are very easy to use. The fields that you need are easy to use."
  • "I would suggest for the request module that they open up the fields and columns so it's like we are doing our work in the work module. You can't do that with today. We also have to make sure that the fields can go both ways with the request and work modules. Including fields in the column sets would be helpful, because today they only use attributes."

What other advice do I have?

We do not use the solution’s Lean/Agile delivery tools yet. That's one reason why we were looking at this heavily at the conference. They seem to be really focused on that, which is good. A lot of companies that I talked to seemed to be struggling with it, so it's good to see that Planview is trying to move into that direction, taking everything with it. Today, Planview does not help connect funding and strategic outcomes with work execution because we only have one PMO which is using finances. I don't think that they're doing a capital budget yet, to say, "These are the projects that we're…
reviewer1208565
Project Manager at a computer software company with 501-1,000 employees
Real User
Nov 3, 2019
Validates the work that we're doing and the funding that we need

What is our primary use case?

The primary use case is project costing, resource forecasting, and financial reporting of projects. It is implemented only in departments that touch what we call our project portfolio. So, the people in IT who do the coding, programming, developing products for customers, and the maintenance on our systems, they're all in the solution reporting time. However, our payroll and human resources do business as usual. They run the company and business, keeping the lights on, but they are not part of our time reporting community.

Pros and Cons

  • "Planview has helped connect funding and strategic outcomes with work execution. That is the key use that we have for it. We use it to validate the work that we're doing and the funding that we need. The difference between the previous version and current version for us would be the ICPM and the way it gives us different scenarios. We can go in and build that out."
  • "We have required more time from our resource managers to spend time in the tool. The adoption has been slower than we would have hoped. So, I would think from a rollout perspective, if Planview could help us with material which gets non-Planview users or previously light Planview users to become more heavy users of the system, then this would help us with the rollout."

What other advice do I have?

I am happy with Planview. I would give it an endorsement. We're trying to move in a more lean, agile direction. Everything we use right now for that is JIRA, Excel spreadsheet, and Microsoft Project based. We used Projectplace during the rollout. I really liked it and would like to keep using it. We don't currently use it, as we are not currently customers of it. I think it was their tool to use when they were rolling us up and because we were participating in that project with them, so we got access to it that way. I find value in both products: Enterprise One and Projectplace. I didn't see…
reviewer1421355
System Administrator at a financial services firm with 1,001-5,000 employees
Real User
Sep 23, 2020
Improves the visibility of the resource capacity and the team's capacity to take on new work

What is our primary use case?

Our primary use cases are for portfolio planning, forecasting, budgeting, and obviously reporting. The project managers input for projects, input resources for proper forecasting, and for budgeting. It's the same with our resource managers to monitor their teams' capacity and then also for finance purposes for our annual budget planning. We don't use the solution a lot for the project planning itself. As far as tasks and milestones, we don't use some of the features to see what stage a project is at. We really just use it to input the project. We actually use outside applications to manage a… more »

Pros and Cons

  • "The resource capacity planning is the most valuable feature because you can evaluate your team's capacity by team and what projects they're working on and you can forecast easily by team."
  • "The reporting capability and access to the fields for our system administrators to have access to the data without having to pay Enterprise One to get the data that's needed to create custom reports for management to create reports need improvement."

What other advice do I have?

My advice would be to be more engaged between the system administrators and the consultants during the configuration stages. Also, for Planview to be more transparent about what the system administrators can and cannot do as far as reporting. And then also make sure that there is time for a training plan and a very well-thought-out training plan based on each phase of a project and user role as they are interacting with that project. The lessons I've learned is the need to ask more questions about how the application works as far as configuring the system and learning more of the limitations…
reviewer1425102
Senior Manager at a financial services firm with 10,001+ employees
Real User
Sep 27, 2020
Offers the ability to track a project with relevant milestones but the upgrade process is complex

What is our primary use case?

Enterprise One is a centralized area to allow project portfolio and planning managers to track, schedule, organize, and begin the billing process for projects. That's it in a nutshell. Our company as a whole is using both cloud and on-prem right now. For project management, we have business sponsors, we have businesses, and we have IT. IT has chargeable projects and we account for all of the application work that's happening and that's done on-prem. The business side has recently started moving over to Planview on the cloud. So currently we're on-prem. Potentially we could end up being on the… more »

Pros and Cons

  • "We use expenditures quite a bit. We put in forecast expenditures and then we actualize them below the line in the little box in the bottom tray. Being able to track the project with relevant milestones is also valuable. Milestones are valuable because it helps us to keep the project on track. The expenditures are valuable because we need to be able to understand expenses that are beyond the regular resources in the projects."
  • "Being the IT development manager who implements the upgrades for Planview, I would love to see more thorough testing of expenditures and more thorough testing in general. When we do an upgrade, we have to do quite a bit of testing because we can affect the bottom line."

What other advice do I have?

I would rate Enterprise One a seven out of ten. I give it this rating because of the quality when I do the upgrades. There are just so many things and I feel like it's a commercial off-the-shelf piece of software. I feel like I shouldn't have to have my team testing out-of-the-box functionality.
See 38 more Planview Enterprise One Reviews