We're a small outfit. We don't have a lot of people logging in at once, so I don't think we're a good use case for that. Our entire IT department has fewer than 200 people, and I'd say we have like 30 people tops in the system. They're resource managers for the most part. I've got six project managers that are in there regularly. Then there are other people who are not within the PMO doing some project management. They go in and do some updates maybe once a week. It's very few people, and it's mostly my team that's using the platform. So it's a tiny group who are heavy users. We're constantly trying to get people to log in. It's not that extensive, but I'd like to try and make it as extensive as possible.

The scalability is good. Nothing is required, technically, for millions of employees to log in to the application. For end-users, the scaling process is fine. Planview provides optimized resources and infrastructure.

The pricing changes based on how it is scaled.

The biggest advantage of any cloud solution is scalability. 

We have plans to eventually scale it up. Eventually we want to start using the request and the what-ifs, right now we're not using those. We'll probably do so mid-next year.

From a scalability point of view, it's not so much the platform as the cost of the license that is limiting. 

We have close to 200 users. Some of the users are global service, delivery manager, project managers, finance, we have a service desk, infrastructure team, and networking team. 

There are roughly 20,000 people in the organization and we have roughly 200 people on the tool. That demonstrates the scope of who's using it. It's mostly folks at our corporate office and IT folks at two of our other companies. Carlisle is made up of four divisions and each division has multiple companies under it. It's a company of companies.

It's being used broadly across the company and I think we will continue to need to work on the adoption of it from some of our senior directors and VPs. We need to build out the parts that they can see, like reports and dashboards, and make it useful for them.

I have no concerns over the flexibility of the combination of PPM Pro and Projectplace. The product will grow with us.

The scalability is very good. 

Scalability is great. 

We have 1,026 full users and time and entry users for one instance. We have five other instances so we have close to about 2,500 users. Every division under the group has their own admin. If we have five divisions in one instance, we have an admin for each division but we also have IT teams, which I am part of. We are a team of three people, me along with two of my colleagues and we take care of all the admin needs for those five groups and for those five divisions. If somebody wants resource or user access for PPM Pro for a particular division, only the division admin or IT admin can do that. We are the IT admins and then we have the division level admin. 

R&D users use it immensely. They use it for timesheet management, reporting, dashboards, and project management.

We've had no issues with scalability. Being a software as a service, the amount of power that we need is determined by the number of licenses that we have.

There are 30 to 40 project managers. We have business partner managers who are the key interface in the business. We also have a number of resource leads. There are around 20 resource leads who are responsible for ensuring that resource demand can be met with the availability of their team members on that side.

Maintenance purely happens in the background. If we're developing new configuration changes, we'll do that ourselves in the sandbox and release it at an appropriate time. It's very minimal impact.

This is a scalable solution.

Our footprint on the PPM Pro side is fairly small. That's just where the project managers and the resource managers go, whereas Projectplace is where the teams themselves go.

I definitely believe that it's scalable. Just listening to where they're going and their ideation is exciting. 

We have 53 licensed users currently and they range from a project manager to system administrators, to stakeholders and senior-level management.

There is a staff of two for the deployment and maintenance: myself and one other. We are portfolio managers.

PPM Pro is primarily utilized in the IT department but we do have representation in most of the departments, not all of the departments. There is at least one licensed user per department.

Planview increased the scalability of its product over the years, so it's very scalable now. It used to be an issue, but they've addressed it. Our whole IT department uses the solution.

It is really scalable. The kind of information that was getting captured and the level of projects have significantly improved as of today. Scalability is not a challenge, but there is a catch. There is a limit in terms of how many fields you can introduce to the system on an entity, the more you add it may affect the system performance. This will be one challenge when multiple BUs shares the same implementation instance. If you have many fields coming into the PPM Pro, it tends to slow down. Any team that is implementing more user-defined fields, it is better to ensure that it is analyzed thoroughly and does not have many junk fields. 

We have a team responsible for maintaining this application in good shape. This team has representatives from each division. We also have an IT department to gives us advice in terms of IT aspects. Every division's requirements are different; so, we come together as a team to share inputs and take a collective decision for a system-level change.

PPM Pro has a 60% adoption rate as present in my division. We do have plans to increase usage. There are multiple types of projects we are running in our company. The R&D team uses PPM Pro for project management. It is slowly growing to adapt all the views into the system for R&D projects. And slowly other groups are also coming into the system, like the operations team. PPM Pro's horizon is slowly expanding here.

In terms of the project waterfall methodology, the scalability is there. We are seeing improvement around the agile side in the software, but it's not at a level we think we can reach in the timescale we have. However, with the Planview products on the market, we are looking potentially at something different to help us with that element of our work.

We have 250 licenses at the moment, and 80% of them are basic users. They are time-keepers who are just updating projects, etc. Probably 15% of them are in the management category, such as project manager, capability manager, and portfolio manager. So, they're the ones maintaining the workspace and the projects, and then, of course, we have about three or four users who are administrative. So, all in all, we only have three types of users in the system, and they are basic, management, and administrator.

At the moment, it is being extensively used in the IT department, which probably covers about a third of the company. We are currently trialing the software in other departments with the view of expanding out across the whole company at some point in the near future. What we are looking at is an end-to-end deployment. So, with it now joining the Planview family, there are other options we're looking at potentially to help us provide end-to-end functionality; for example, Spigit being the upfront or the idea-generating piece of tool to maybe LeanKit being with us for the agile element.

We're a small organization, however, from what I've seen, is that the other clients the product has are a lot larger than us. The things other companies are using it for, it just amazes me how it can accommodate everything from a small organization to something much larger. Having seen its capabilities with other companies, I would assume it's scalable for us in the long run.

Our organization has over a thousand users, however, we have only 130 licensed users. We have our stakeholders, which are our C-suite partner or employees, and that's just basically to approve requests and view dashboards. Then we have our entire IT department and our team users that utilize it mostly for time tracking. We also have our business team members, who also use it for time tracking, however, they can also get in and view the reports and be able to drill down into specific data on the projects. 

We plan to increase usage by adding more users to the system. We've tried to stay focused on the people that work on projects probably more than half the time, however, we want to make sure that we're capturing all project team members so they can record time as well. 

The tool can growth with us.

It's definitely scalable. There are a lot of opportunities to customize. It's just how you implement it. That's why we think we have to use LeanKit, because of the agile integration, which is why we're here attending the conference.

It's definitely very scalable. We've seen growth in our business. I know we've seen a lot more users using it for requests. As our governance structure has changed over the last couple of years, we've used it quite differently and scaled it to a lot of different users and a lot of different uses. It's done just fine.

We have our request users who are submitting requests for enhancement-type items. There are over 6,000 request users. Then for full users, these would be folks who are doing more than just requests, they might be tracking time, working in this system, providing updates, or doing approvals. For those types of things, we have over 250 users.

For maintenance, we have several of our project managers, including myself, that are administrators of the system.

PPM Pro is being used quite broadly in our IT department and for requests coming into our IT department. We use it for all of our enhancements as well as projects. It has a 100% adoption rate. We have to use it. That is our IT tool for tracking time and handling new requests. We use it all the time with IT.

We haven't had scalability issues too because we don't have that many entries in regards to performance and scalability testing so far. 

It should grow with us for now.

I've gone from a company that used to manage about 8,000 projects simultaneously. It was a global solution here at LPL, which is more of a nationwide solution. It can handle it. Maybe the one problem on the global side is when you have teams that are working on a particular project all around the world, the whole time zone issue becomes a problem. Sometimes because of how the reporting solution that has been put in place it cannot provide real-time reports for people that are on the other side of the world. It gives them a lag where they don't know what to do or what not to do.

There are 1,500 users in my company. The great majority are just time entry contributors. They are around 75% are contributors, time entry folks. Then the rest of the 25% are between project managers, program managers, and financial people that go into the tool and approve capitalization. 

Right now, we have two dedicated and two shared staff members who work in regards to configuration and ongoing maintenance. In regards to any changes that need to happen in the tool or, and proof of concepts, things that we want to test out. And then we have two that are shared, which are more like admin activities who add remove users, add value to existing structures, and all that.

It's heavily used, it's the project management tool. This is where all project data and financial data is related to a project are being stored. It's a brand new project management and technology. I would say it has a 100% adoption rate. 

It has had no issue scaling to what we do, but we're not a large corporation. Based on how it is designed, I assume it would scale just fine.

We don't necessarily use it for the entire company, just within IT projects. We have 40 licenses right now. We have our business stakeholders in place as well as all of our workers, whether they are developers or system engineers. That level does the tasks within the project.

We typically do about 80 to 100 projects a year. We have done 637 project in four to five years.

It can grow if we need it to.

We have around 200 users in my company, including portfolio managers, project managers, and two admin. 

We are at an optimum level right now so we don't anticipate more users at this point in time.

I am neutral about the scalability. That's not something we really have spent too much time diving into.

In terms of scalability, I think for what it's built for it scales well. It's just whenever we get into the integrations it's something I need to see more because we get to a point where it's hard to track everything within just Planview. I think the integrations that they're doing improve that scalability, hopefully.

LeanKit and Projetplace both have the cards and the actual task-level definitions that can just build into what's in PPM Pro.

There were some scalability issues. Our organization is too large/complex to use the planning tools (Predictive Portfolio Analysis and What If workbench) with this solution.

Other than that, there were no issues with scalability on day-to-day project management and reporting.

The product is not scalable. We have around 15-20 users for the product. 

I did not encounter any scalability issues.

We did not encounter any stability issues, as we are a fairly small shop.

I have not encountered any scalability issues.