Planview Portfolios Reviews

We currently use it for all of our technical projects. We use work and resource management for our technical portfolios.

The biggest impact for using Planview currently would be to understand the true costs of projects. We are trying to get to a point where not only do we take into account technical costs, but what the business cost is. Trying to integrate our business right now into Planview is helping us identify the true cost of the investments that we make so we can try and understand their value.

The tool does have the potential to impact our organizational delivery. As we continue to integrate our entire business with our technical teams into Planview, I definitely see it changing how we deliver projects in the future.

Currently, it provides insight to leaders that they don't otherwise have access to get. As far as delivery leaders from technical teams and determining their resource capacity and constraints, they don't have another way of figuring this information out right now unless they were to do it manually on their own, which would be very time consuming.

The most valuable feature is resource management. You get to work with a lot of resource leaders for capacity planning. Although, we don't use capacity planning to its full potential, we would like to go there as well as financial management for the projects.

All of the features that we get out of Planview, it just helps us to provide information back to our senior leadership and have those conversations to get insight. When we have that information, we get insight from them on what it is that they are looking for and what they need. Then we can transform that information from the tool and get them what they need. All the information is helpful for me to be able to provide the data that they need. We want to help them make the right decisions that they need.

I would like to be able to copy and paste from Excel into work and assignments along with roles and hours, as opposed to having to type it out one by one.

It's very stable. It's a great tool that is evolving. It provides more information and opportunities for us to expand what we offer to our customers. 

We do use the technical support. We always have a good experience. We have dedicated people who we can work with to submit tickets. The responses to tickets are always in a timely manner.

We did the upgrades with the help of Planview. It was a really good experience. 

It wasn't just me. An entire team from Planview worked with my company, so this helped us get all the information so we could make each upgrade. We've done multiple upgrades so we could make each upgrade be as seamless as possible. So, the support that we got from Planview was nice.

We have seen some return on our investment within Planview. As we transform here to turning on more of the features, reworking what we've done, all the customizations, and trying to just start fresh, I think that we'll see an even bigger return once we can take advantage of the features that Planview offers that we aren't currently using right now.

This is information that we can leverage from PlanView once we transform how we use it today. The information that we can leverage that will, in turn, provide a return on decisions that we make, how we deliver work, and maybe delivering it faster. Then, we would see a reduction in costs for some of those projects as well as having our leadership setup to make better, more informed decisions than what they currently can do from the data that we provide. I believe that once we started leveraging all the tools that Planview can offer from what we have in Enterprise One now, we'll have more information for our leaders.

My advice would be do to planning. Ask a lot of questions and do a lot of planning out first what the goal of the organization are. Then, from what their goals are, utilize the tool to try and meet those goals.

I am an everyday user of the tool. When you don't have everyday users, or users who go into the same task over and over, it probably is not as flexible for them. For myself, I do find it very flexible.

I would rate the tool a solid eight (out of 10). I wouldn't give it a 10. Part of it probably is that we haven't activated all of the capabilities that Planview has. The other part of it is that I work in the tool everyday. So, some of the things that we would like to do as an organization may very well be available to us. We just haven't utilized them yet. Once we go through this assessment process and sit down with Planview next week to go over what we can do, it may change the team. This is where we are in our current state for everything that we want to do.

We are in the process of having Planview help connect funding and strategic outcomes with work execution. We are just building a roadmap for this.

Our strategies have evolved from other factors, but not necessarily from the tool.

We do not use the solution's Lean/Agile delivery tools nor do we use Projectplace.

We've been using this product for prioritizing work across our Organization and also demand and capacity planning. 

Work that gets added to Planview captures all the key information like t-shirt sizing, key stakeholder names, financial information, and, most important of all, resource allocations and role requirements - all in one tool.

It becomes really easy for the Project Managers to keep an eye on the progress of their Projects, and on the other hand, for the resource managers, it's really easy for them to identify what's in flight for their resources and what's in the pipeline, also do we have enough capacity to fulfill that demand.

Really happy with how Planview keeps transforming its capabilities to meet customer needs.

We are able to take up the right work and invest in the highest value ideas.

The challenge was that we were doing a lot of work without identifying what work has the highest returns. With Planview, we have that visibility across IT, and all the work that gets entered into Planview is surveyed and prioritized to make sure that we start with the highest valued investments. 

Not only that, we have visibility of all the resources as to where they are spending their time and how they can be utilized to better meet the vision and business strategies of the organization.

The best aspects include:

Work Management. Work that gets added to Planview captures all the key information, including t-shirt sizing, key stakeholder names, financial information, and most important of all, Resource allocations and role requirements - all in one tool.

Resource Management. We have visibility of all the resources as to where they are spending their time and how they can be utilized better to meet the vision and business strategies of the organization.

Leankit. The kanban board has really helped us be more agile and we can keep track of everything that is ongoing.

The solution needs to be better at accepting new ideas for upcoming releases. At times, we've requested Planview to add new features to the tool. But they have it go through an enhancement idea process, and we find it a long process. Your idea goes through only if the same idea is proposed by other organizations.

Email notifications for resource allocations/requests/requirements/reserves are something that could be added. A lot of the time, we get questions from resource managers. We would like to get an email notification when a resource request is made.

We've used the solution for nine years.

The product is stable and reliable, with 24-hour support around the globe.

Planview does a great job in scaling the solution with its in-house experts.

We got it implemented through vendor support and are really happy with the support.

The setup cost is mostly the same as competitors. That said, you get a lot of value and return on investment with just one tool.

We also looked into ServiceNow ITBM.

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 JIRA and we're trying to pull over as much of that information as we can from JIRA so that the people, the frontline folk, are doing their day-to-day work in JIRA and we have more of the product owners, project managers, program managers doing the high-level planning work in Enterprise One.

In terms of the most valuable features, the strategy view is something we never really did in the past. It 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. It's all at varying degrees, whether percentage complete, effort complete, hours expended, those types of things. From an overall corporate perspective, so far I've seen a high-level strategy program view into the data.

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. We do want to try to capitalize a little bit more on some automation. Percent complete is the high-level metric that we're really trying to drive to. So if we have a large effort, we can see how far along in the process we are based on a high-level plan that we think is going to run from August to December, we can see where we are in the process. We can't have a plan unless we work it. And so we're struggling with that just a little bit, but from an overall status of things, I think it's great.

The Enterprise One view into resource capacity and availability does not help us to manage work because we don't know how to work it. It absolutely cuold and that is one of the things in our current use case that we're really struggling with because the pure Agile folks say, "You don't plan. You don't estimate. You just do." And management, managers, VPs, and above are saying, "Okay, what is our capacity to make all this work?" So we're struggling with that just a little bit. I think once we settle on something that Planview does give us a view into what our capacity is and how much work can we really take on.

Its ability to create summary reports across multiple projects is pretty good. Planview has invested a lot of years and a lot of money in creating a lot of out-of-the-box reports. It's just us trying to learn them again and really trying to find out what's available. We've been providing reports and information to our upper management, and our CIO said, "That's too much information." We're trying to find that balance between a one-page summary of everything going on versus providing all the details that might be needed. So overall, Planview is very good at providing whatever level of information we want.

In terms of sharing the big picture with management, this feature has really helped because there are certain strategy reports or certain work reports that do provide a one-page overview of everything. It's just that management is trying to decide what information they want to see. Then, in turn, can we from an administration perspective, modify the report enough to be able to provide that information.

It provides end-to-end work management for the full spectrum of types of work in one tool. Admittedly, when we're looking at all the different products that Planview provides, whether it be LeanKit, PPM Pro, or whatever, they do bend toward a certain type of methodology. Obviously, Enterprise One has been very traditional work and resource management focused, but I think over the years that we've been with Planview, and especially with the introduction of the Enterprise One model, they're really trying to make it to where you can have different types of projects. Whether they be traditional waterfall, Agile, Lean, SAFe, etc. Planview Enterprise One does a good job at all of that. It may not give you the capabilities of everything that you want, but that's why they've introduced these integrations with other tools like Azure DevOps, JIRA, Micro Focus, and those types of things. So that you can get that overall big picture of what's going on.

Another example of how it's been able to improve the way your organization functions is that we can now look at the strategy view to say, "Okay, what do we all have?" Because you've got this group doing something, another group doing something, and another group doing something, but overall what is everything we're doing? And as we mature in the use of the tool, not only from how much work we have out there, what can what our capacity is to do everything. But looking at the ICP portion, the investment and capacity planning portion of it to say, "Okay, we think it's going to cost us this much to do this work," but "Oh, by the way, we need to shift something around." What does that mean from mainly from the way we use it, from a capacity perspective? Because we're completely internal. We don't draw revenue directly from the internal work we do. But hopefully, we can get the benefit perspective where something may be big work, small benefits, whereas something else is small work, big benefits, and we can see where we need to re-adjust our priorities there. Overall, I think it'll help.

We're not doing direct assignments but if we were, I think it is a very flexible tool. Probably the only thing that I really struggle with is doing allocations at a certain level. And you have to do it at what they call the lowest leaf level. That's probably the only drawback I see. I'd like to be able to see allocations happen at a higher level and to where we're dealing with Epics. 

In fact, I had a scenario this morning come up where we had an Epic that was created. Some allocations were put on the Epic, and when somebody tried to put a story or a task up underneath that Epic and we couldn't. And so that's the only feedback on the whole resource assignments, how I'd like to stay flexible enough to where I can go at a higher level to where I don't have to do that. A developer is going to be working on this story and we're allocating X number of hours to that particular story. I'd like to know that, I know Jane and Joe are working on a project or this work. And I think over a course of two, three sprints, months, whatever, I think they're going to be working about 75% of the time. So it is flexible, but it's not flexible.

There are pros that we're seeing from being able to draw down and see the resource demands and costs at a consolidated level. I'm a product owner and when I look at an overall endeavor and I know that I've got five Epics and 10 stories across that, from an investment perspective or a cost/benefit perspective, they say, "Okay, Epics are like features. Which feature is going to cost me more to provide?" And then hopefully I've got an idea in my brain if I'm a product owner of "Alright, this Epic is going to give us more value than then another Epic and Epic A is only going to take five story points, whereas Epic B, isn't going to give as much value is going to take us 30 story points or something like that." 

I've personally been using Planview for going on 17 years now, and I think they have made some great improvements in it. I've used it both as a Resource Manager and Project Manager, and now I've been using it from an admin perspective for quite a while. 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.

There are some small things that are troublesome to me as far as assigning resources, setting people up, trying to configure resource structures, and stuff like that. But those are just small nibs. I think overall from a usability perspective, it's really good. It's huge. Planview's the Microsoft of project planning and PPM. There's a lot to it and people just need to take the time to learn it.

I have been using Enterprise One for about 25 years. We use the latest version, Enterprise One, PPM release. We're on the continuous cloud.

I think the stability is great. Planview had some issues about, three or four weeks ago. But I think they've gotten over that, as far as the technical stability. It has pretty good functional stability. I think it's really good there. There's just a lot of stuff we don't know. Everybody working from home has had a big stress on internet service providers and big companies like ours are using a VPN solution. And so if I'm on VPN and I get on, try to get into Planview, there are some issues there, but overall, I think it's pretty good.

From a number of users perspective, it's how many licenses you purchased from the amount of data. I'm not worried about that since we don't have it on-premise we could probably go as big as they want it to it's just until Planview says, "Hey, their cut back" or something like that.

We are looking at expanding the ICP usage specifically. I know that's integral into it and we're trying to go a little bit more enterprise maybe. That's specific to Enterprise One, but a little bit from a cross-tool perspective, we are looking at the capability and technology management offering for our enterprise architecture group. I think we're going to start looking at LeanKit.

Technical support is very good if they know what's going on. The reason I say that is because we have introduced a Tasktop as the integration between JIRA and Planview. And so the support model is we have to go through Planview to get all of our support. I have found it a little difficult to get answers based on some recent questions that I've had with regards to the Tasktop Integration Tool. That's my only complaint, but I think it's fairly new, I know task integration with Tasktop is a little bit more than a year old.

I think the whole integrations team is fairly young and, they've got a lot of different tools that they have to support, but maybe the support model for Tasktop and the integrations could be a little bit better.

The initial setup is complex but it's huge. There's a lot to configure and there's a lot to consider and when we reengaged with Planview to get us to reset back up, we spent from March to June and beyond getting things configured. I look at trying to set up Microsoft Outlook or Microsoft teams. There's a lot to it. Is it impossible? Absolutely not. But would it change my mind on going with Planview? Absolutely not.

In terms of strategy, we were trying to re-initiate and figure out how we can mix the traditional sense of what we've used Planview for in the old waterfall method, timesheets, and all that. How we can blend it into this new, Agile methodology they were using. And we still have some teams that are very Kanban-oriented work comes in where it goes out, that type of thing. So that was our strategy to how can we mold all this together and be able to get the necessary information out of the tool that we want for upper management. We have a reset goal yet.

If it was up to management, we'd have it yesterday. We're getting back into some traditional project status things like what's the current health of the project, what's the current red, yellow, green status? We're trying to financially cost things out through the financial planning details and stuff like that. Our goal at least for projects data thing is hopefully by the end of this month with hopefully some more customized reporting, hopefully by the end of October.

We brought together a good cross-functional team between our PMO, which we have five people that write five or six people on the PMO. We brought in some scrum masters and product owners. In our core team we have about 10 employees working on it from a day to day maintenance perspective. There's one that would be me from a data maintenance perspective. It's falling mainly currently on the PMO members, which is to get to three contractors. There are seven or eight of us on the PMO.

In terms of how many people use this solution, we have all of our contractors entering timesheets, so we can do timesheet reconciliation, which is about 50 or 60. The number of people that are in it week to week are around 30 or so. That's going to increase as we're trying to move our project status thing back into the program manager, product owner space as well. 

We have time reporters, team member roles, program manager roles, mostly most of the users that we have set up are in the program manager role for being able to see statuses and updates statuses, we have about 10 people that are in what's called the requester role or more the executive I just need to be able to see the information. I don't need to be in the weeds entering data or anything like that. 

In the past, we have seen ROI. Again, we're still trying to figure out who, where, what, why and how. And so, I think the ROI calculation may come about a year from now.

It's kind of expensive, but I don't write the check. As long as the bosses will pay, we'll write the check. That's fine. Pricing isn't really part of my concern, per se. And again, not knowing what other solutions are out there and how they compare from a licensing perspective, I couldn't give you opinion either way.

There's the SaaS cost and there was a cost for the Tasktop Integration as well, but that's to be expected. We use JIRA and anytime we want to bolt on something new, we need to spend some money to make it happen. I don't think it's unreasonable.

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 will need to put into Planview, or the Enterprise One application to get that information. That's something I think that we didn't do very well. We thought we knew what we wanted, but then we'd get a month down the road, and we'd say, "Okay, I'm not getting this information." Planview was right to say, "You didn't ask for that information." So again, it totally goes against Agile methodologies, but you've got to really set a good base of what you want, so that you don't have to continually shift, on a week to week basis. Thankfully Planview has been very gracious to us and has reacted to our needs and our changes in requirements. 

I'd rate Planview an eight out of ten. It's a really good tool, very powerful, and very robust but very complex.

We not only use Planview for resource allocation but also for tracking financials towards the projects that we have set up. We also have financials and resource allocation and we also use the project planning piece of it.

We use Planview quite a bit to articulate and tell the story around where we're at, whether a project's at risk, whether it is on track, whether or not we need to either extend the timeline or add additional resources.

I just took it over about four or five months ago, as part of my responsibilities. But from what I can tell it's pretty robust in terms of flexibility.

It maps back to our SDLC process pretty well. I'm able to see the stage of where things are at. We also use Azure DevOps for all of our requirements and our coding. 

The work is in Azure DevOps but the planning aspect of that work, the financials, and the resource allocation are done through Planview. I'm trying to figure out how to connect the dots. Meaning, if I have a project where I've burned through 50% of my financials, and I've done all my resource allocation inside of Azure DevOps, I'm able to visualize and see the data that says, "Hey, I'm 50% through the development work of the project. I have this work that I currently have in flight, and I have this much planned for the remaining amount of time, which represents the remaining 50%." And then I want to see how that then maps to Planview. Because Planview could say, "Hey, you know what, we burned through 80% of our money." How do I then use the data coming out of Azure DevOps to then either go ask for more money and more funding or to do something to make decisions?

Resource capacity helps me to ensure that I have the individuals needed to complete the work. We basically go in at a high level. We know we have a project and we know we might need around 500 hours of a cloud engineer. And so we'll go out, we'll make the request, and the allocation is done for it. Then you have a person that's allocated for those 500 hours. The only thing I don't have is when they've burned through those 500 hours, I understand that they're burning it against the project, but I don't know how to tick and tie that to the features that they burning it against. 

It provides end-to-end work management for the full spectrum of the types of work. From a project view, I'm able to see where things are at by the financials, the allocation of resources, as well as the lifecycle of the project.

It also provides a variety of types of resources assignments for assigning work to people. It's pretty flexible. We could set up a variety of different rules within Planview across organizations. Each team sometimes has different roles that they need to pull in for the project or for the team. And so having the flexibility of adding roles is good.

Another thing that it has helped us with is our burn rate of dollars, more than anything else. We're able to look at things and say, "If we're coming towards the end of this year, we know our burn rates higher than it should be." And we can look at certain projects and say, "Let's remove certain work streams that we don't want to work on."

As more and more organizations are adopting agile as a framework of how to deliver work, they should build in some flexibility within Planview of connecting the work to the teams.

For example, right now the old waterfall methodology of planning was to say "Hey, I need an allocation of a resource." Normally with other tools I've seen, it's if I need an allocation of 18, I know Planview has that. We, unfortunately, made some modifications, we didn't go that route, we're on fast forward. That is an example where I think Planview has done that. 

When you think of planning at a PI level, roadmap planning, or release planning, I think they should make a little more headway into how agile delivery works, tying it back into the financials and the planning to Planview. I think it would be good.

We have been using Enterprise One for four to five years. 

The stability is good. I have not seen a lag time and we haven't been down when I've had to use it.

The scalability is good. We have 20 to 25 project managers that use Planview, a couple of team leaders, and then we do our time cards in Planview, so really the entire organization uses it, at least in IT, so it's probably around 400 to 600 people.

I would like to see us use it more. When we use Planview I would like to use it at senior level leadership planning where we can see forecasted spend, my allocation for the budget, my resources, and all of those things. I want to be able to tie that to detail work that's in Azure DevOps.

The initial setup went smoothly. It was straightforward. I don't think we had a whole lot of tickets.

We do a lot of upgrades. It's usually overnight and it doesn't take long. We had a major reconfiguration about two months ago and it went pretty smoothly.

From our side, I think we had about four or five analysts involved.

For the management, we have two people that help support and manage Planview.

We only worked with Planview, not third-party integrators. 

It's pretty easy to use. It's not that difficult.

I would rate Enterprise One a seven out of ten. 

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 cloud as well.

We have all the projects in Planview on-premise from an IT perspective. We know if we wanted to find out about a project, scheduling, or who was working on what, we'd be able to find that out with Planview. Planview highlights the human resource hierarchy within it in our on-prem solution so we know who's working on what projects.

Enterprise One provides a variety of types of resource assignments for assigning work to people.

It also allows program managers to group work together and see the resource demands and cost at a consolidated level. I have five different projects and I can do that.

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.

I don't believe we're using the resource capacity to the highest extent. The project managers and resource managers are managing that outside of the tool. There are a few select Planview experts areas that are utilizing resource management to its full extent, not in my company though. 

Its ability to create summary reports across multiple projects is good. Our solution on-premise is a bit hamstrung though because we don't have Power BI. It's on the Oracle platform right now. It's not at that level for some of the reporting, but the reporting that we do have is good. Even our Planview administrators can make new reports if required.

It feels like Planview is moving away from Oracle and guiding people towards SQL server. For us to do a migration like that, it's going to be very costly. I don't know if they'd be able to support their analytics solution through Oracle or not. We'd love if there was a way to do that.

We don't use the summary reports on-premise to go to upper management. At least in my case, there are some areas within the bank that are using it. I know that we've got the data flowing out of Planview on-premise into our own recording database and we're using Tableau to report up there. We've created the functionality that we didn't see in Planview on our own.

There's integration with Planview Enterprise. We've created an integration with all the data out of Planview and we pull all of our other project management tools into this database, as well as other relevant interfaces, such as HR. We're looking at getting JIRA in there as well.

To a certain extent, it does facilitate end-to-end management but we have to use multiple tools. We're using our MIS in-house tool along with Planview. That may not be a limitation of Planview. It's likely one of our company's needs.

I find it a little difficult to forecast the remaining effort but even though I've been using it for years I don't think that as a company we have been using it to its full extent. There is probably a little bit of process change that's required on our side, as well as understanding as to how Planview works with forecasting.

It's more internal for us to look at from a process point of view, to understand how the forecasting works. We're a bit unique because we're also using another tool called MIS along with this application and it's integrated with Planview Enterprise One. It gets a ton of the information from there and that's where we're actually relying on financial forecasts.

The integration was okay until Planview changed its integration software from Appian. They have Integration as a Service now and we're not using it. We're continuing to use Appian with our own licensing of the software for on-premise.

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. We have to understand that Planview is upstream from our financial tool that derives the capitalization of applications. We have to do extensive testing and when we implement a release, we find numerous bugs and we have to have hot-fixes and patches put in on top of whatever we're testing at the time. Because it's such a huge amount of effort to upgrade the application we can't go to the next release, even if it has the next fixes on it because we're going to have to redo all the testing. We'll set the project back months, and then we find another bug. It's very difficult. If we can have better and higher quality testing coming from Planview software, then we'll have higher confidence in putting the software in and not testing the out-of-the-box functionality.

I have been using Enterprise Pro since 2012. 

The application has been around for a long time and there's some legacy framework that's still hanging around in the background that hinders them from moving forward. I think it actually hinders their stability at the same time. I know that Planview addresses it, but I think not addressing that legacy code framework is limiting and it is reflected in Planview's stability.

We have over 10,000 resources within Planview on-prem, so it seems pretty scalable. They used to enter times, so you could consider them users at one point. I think there were 10,000 to 12,000 users. There are around 1,200 project managers.

I have eight to ten people working for about four to five months to do an upgrade. After the upgrade, there are probably only a couple of people for maintenance but we have a full production support team that has a large budget on a yearly basis to support Planview. Not just Planview, but our whole project and portfolio-management system, from Planview all the way to our other integrated systems. It's mostly testers. We've got a lot of QA analysts, a QA lead, plus infrastructure technical leads, and then technical systems analysts.

From my experience, I think their overall tech support is good. They've got a Planview ticketing system. I don't know if it's us or what but it just seems like we do have to escalate sometimes unless they've heard of this issue before with other companies, whenever there's an issue. I think they're pretty good. From a development point of view, they're pretty good.

I've been dealing with them for so many years. Recently, their turnaround time and knowledge are good. If something new happens, then they have to get their legs right. I think part of their development was moved offshore at one point and we were right there at the beginning of it. It wasn't the best. Everybody individually was trying, but as a whole, they just had to figure out the process. Once they did, then they were able to work things very well. We had to have a little bit of patience.

I was around for the upgrade and it wasn't overly complex, but it's not an upgrade. It's an installation and a migration of the database, which is into itself complex. If you could just do a simple upgrade and not have to worry about that, that would be so much easier, which is my experience with other applications.

A typical upgrade takes four to six months and costs half a million dollars. 

In terms of strategy, we have to use swing equipment and we set up a parallel environment all the way from pre-production into production. Once we are confident in each environment level, then we can move on from dev to QA. Then once we're happy with QA, we've done our full functional system testing, integration testing, and all-inclusive regression testing, then we can promote it to production. There's so much configuration that's done after and because there's so much configuration done after you install, that's what makes it complex. Planview does a configuration upgrade because all of their configuration is captured in the database. They'll take an extract of that and then they'll work on it and provide it back to us so that we can apply it into our environment. It's not the easiest thing to do.

Every time we do an upgrade, we have to have Planview heavily involved. We end up spending quite a bit of money on just the Planview consultants to do the upgrade which is on top of the half a million.

We do have to be on top of them. If we're not on top of them, then they're not there, but it takes two to tango so if we end up getting caught up busy working on our environment, and we don't go and talk to Planview, then all of a sudden they're not available anymore. But when we do need them, sometimes we do have to escalate to get their availability.

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.

Mainly, we use it to manage all of our strategic and capital projects. There are about 80 to 100 projects per year that we manage with it: schedules, issues, risks, and financials. We manage everything in the tool.

Our reporting is much better. There is much more visibility on projects, schedules, tasks, and in our milestones. Now, we have a consistent way of reporting out to the committees and getting all of our schedules and milestones.

The most valuable feature is the reporting. We are able to extract monthly reports out of Planview Enterprise One. We then report out to our leadership and executive committees. It is a combined report that lists all of the issues, risks, our schedule, and milestone. It gives leadership as well as all the committee members and everyone a one page view of the progress of the project.

The tool is easy to use, and that is good.

We had some learning issues at the start, but now that the users are in the tool day after day, they are getting there.

Power BI versus getting reports within Planview could improve. Instead of having to leverage Power BI, those reports could just be generated within the Planview tool using the tiles. This would be a huge jump for the product.

For most part, it's pretty stable. The only issue that we have seen is with the reports. Sometimes within the application, when you pull a report, it takes awhile performance-wise for the reports to pull up. Otherwise, it's good for the most part.

The technical support is pretty good. We have opened up many cases with Planview which get addressed in a timely fashion. 

It's when we want to get into integrations that the time response could be a bit quicker.

It is changing the culture of project management within our company a little bit. Before, we had multiple tools, so project managers were either using Excel or some had Microsoft Project. Reporting was done in different ways. This tool just brings the project management community together. We're all on the same tool and reporting on the same structure.

The initial setup was complex because we also implemented it in a three month time frame. This was a pretty aggressive timeline for us. We got it done.

We didn't get all the integrations done, but that was sort of our phase two. We started in December with our build portion and went live in March.

We did not other vendors. 

We're part of UT. Because we already had an existing contract within the UT system, we piggybacked on that contract and utilized that to implement Planview.

It is about a seven or eight out of 10. I think for the most part that the tool itself is excellent. It meets our needs. It gets us the reports that we want. It has all of the portfolio and program management functionality. All of that is working well. I would've given it a 10 out of 10 if the integrations in some of the reporting capabilities were easier,

Our primary use cases are for using the requests, the work and resource planning, and the financials.

We are hoping to add a planning module strategy so that we can better track our program, work, resource capacity planning, and have a better handle on our financial forecasting.

Enterprise One allows us to provide a single-source view of our IT portfolio, how it aligns with the strategy of IT, and shows us the big picture of our workforce and where we're investing. 

It has also helped us with prioritization of projects, through alignment with strategic objectives. Our business areas are not using Planview, and it's difficult for us to align with the prioritization, but it shows a picture of how we believe we're aligning with their strategy.

This allows us to work with the business to help us find the priority of work, the work that we should be doing to move the business forward, as opposed to, "Here's the list of the things we want done." We can focus on the things that are needed now, as opposed to just a big list of work.

Having Enterprise One has increased our on-time completion rate by 40%. 

The work and resource planning are the most valuable features. We are able to track our IT portfolio of approved work and assign named resources to the work level, have a better handle of our resource capacity, and the ability to take on additional work. The financial planning helps us with making sure our investments in IT are aligned with the strategy of the company.

Enterprise One provides a variety of types of resource assignments for assigning work to people. It's very easy and straightforward to configure these assignments. Planview allows us to see the entire workforce. We can see where our skill sets of people are, what they're working on, and allows us to make informed business decisions based on priority. 

We don't use the full project management piece at this time, but we're working towards that and becoming a more agile workforce. We are working towards tracking our work better. We're just getting started on that piece of really understanding the phases of our work and conjunction with our spend.

Its view into resource capacity and availability helps us to manage work by entering our resources into the work and assignments to understand where our resources are working and looking at the skill sets, aligning them to our priority work. Some of our higher paid resources are working on our new development and understanding how to align our resources better through the financials and the skills that we have attached to those resources.

Enterprise One does a very good job of allowing us to create views across different projects of our resources who are working on multiple projects to understand the capacity of our resources. This feature affects our ability to share the big picture with management. We are able to show our management our extended views, our forecasted views of our approved work, and help make suggestions on where we could better align our investments and our resources.

It also provides end-to-end work management but we are using it with a combination of another tool, JIRA, to get that full picture. It gives them a better insight into the projects that are going on when they're scheduled and the available resources they have for the work and their budgets. 

The resource area needs improvement. The improvements that have been made recently in the later versions have been good improvements, but I think there are some more improvements needed there.

I would like to see where we could add a few of our own fields and be able to track some additional information such as release information attached to the pieces of work so we can tie our accounting codes into the work and the release at the resource level.

I don't think there's been a lot of investment in the request area. That's our intake and it seems to have remained the same over many years. I feel there's a disconnect from when we enter a new request, and if we approve it and dispatch work, the request and the work are then disconnected.

We've been using Enterprise One since 2012. 

It's very stable. We've had very few incidents.

Scalability is very good. It's very scalable for our organizations. We're a small implementation, we have 140 users. There are resource managers and application managers. We have senior staff who are mostly reporting, admins, and some architects.

For maintenance, we have two admins and two owners. One is a business owner and one is a technology owner who oversees what's going on. The admins are technical people from the development staff and the business owner would be like myself, who is more process-oriented around how we use the tool and what type of reports are needed.

Within the IT division, we have a 100% adoption rate. We have plans to increase usage. We're working with two other areas now to see if they will adapt it.

Their support is good but not as good as it was a couple of years ago. Since it's moved out internally from Planview to being outsourced, it has not been as responsive. It's still very good. We get where we need to be but it takes longer for us to get to support at times.

Before Enterprise One we were using Excel. We switched to have a more robust centralized system that we could do more for reporting. We wanted to have a centralized area for everything in a dependable system that we could do better reporting.

We've used PeopleSoft which is an Oracle product and Microsoft Projects.

The initial setup was complex. I think it was because of the consultants that were sent out to help us. They didn't understand our model and I think they were a little junior. They sent us a brand new person. We were his first assignment and he wasn't sure of how to set it up properly so we went through several consultants and rework those over about a six month period. Our deployment took six months. 

In 2012 our implementation was the basic Planview which we used the request to intake the work projects, to capture our approved book of work for portfolios work and resources to understand the capacity of our workforce.

We have seen ROI in the sense that we have fewer people involved in tracking work and resources than we did in the past.

It would be nice if all of the licenses were FLEX. They've been fairly stable with their pricing over the years.

We evaluated five other solutions. They were PPM solutions from Computer Associates, HP, and a couple of other smaller ones, mostly the ones in the upper right corner of the Gartner quadrant.

Some of the others were much bigger and more costly solutions. Planview seemed to meet our needs where we would need just one solution. We might have needed others to compensate for some of the areas that they didn't do as well as we plan. Microsoft had a product but their financials were nowhere near what we needed. We would have to have a secondary tool for that. Planview offers the best all-around package. Enterprise One is equal to them when it comes to intuitiveness and ease of creating reports. Oracle also requires more training.

Planview is a very well designed application that with a little bit of training can be easily adapted by the entire organization. The different modules really round out the product, which gives it an advantage over some of its competitors.

Enterprise One is a very reliable product and offers robust reporting. The company is very in touch with their customers.

I would rate it an eight out of ten. 

We use it for resource management, financial forecasting, and time reporting.

I am a user, not an administrator. I mostly do portfolio management.

It is good to have everything in a centralized place.

It has helped improve governance, mostly. People want to know where their money's going. Projects sponsors need to know what we're spending money on and what our burn rate is. Planview can give that to you straightaway.

The forecasting and time reporting functions are the most valuable features. We have about 200 people and can accurately forecast to the penny how much it's going to cost us for the year.

It is a bit of a rigid system.

We are looking to upgrade next year and the big thing for us is BI integration. The project already has that, so that is what I'm looking for, and Planview has sort of covered that base already. This will make our reporting a lot more customized. We can be more flexible. Right now, we are sort of using custom reports, which can be a bit buggy, as they're not native to Planview. This will be native integration.

Stability and reliability are absolutely fine.

We use it very basically. We only have 200 people on it. Most other organizations have thousands of people on it. Our entire company is 1,500 employees.

In the time that I've used it, we've doubled up the amount of dollars on our intended projects. We have managed to double the number of people using it and doubled the amount of projects. We went from one portfolio to three. All of that was a walk in the park.

I am a user, so I don't have to contact technical support.

It was there before I came.

I would recommend Planview compared to what is on the market. I would even say that Planview is the market leader.

I have also used a customer solution in the UK and Microsoft Project.

I would rate the solution as a 10 out of 10. It does what I need it to do, so I've got no complaints. From a user perspective, it's perfect.