What is our primary use case?
This was an enterprise rollout of Planview, as well as a number of projects. One of them had me as the senior project manager. I had a Planview entire project, which included resources, budget, work breakdown structures, and everything else that a Project plan would normally include. Through Planview Projectplace, I ran the agile side of things.
What is most valuable?
The most useful features of Planview are its integration with resource management and the ability to commit and reserve various resources. Oddly enough, I liked how they did the time updates. Every two weeks, it would update all timelines to the current date, and you would then be sort of locked into what you had completed. That was confusing to a lot of people, and if you weren't familiar with it, that's a Planview feature that I haven't seen in Jira, Microsoft Project, or other products. That was very thoughtful. I liked how they handled current time management. It enforced best practices.
What needs improvement?
We did not purchase the agile package. I believe this relates to what we had. We had Planview and Projectplace, but not, the full agile package. We had cards in Projectplace, but we couldn't put them into Epix and then stories because they were part of the agile package.
Planview turned out to be completely useless for my use cases because I needed to be able to take large, stories or large Epix and put them on a backlog and associate them with Planview work breakdown structure schedules. In Planview, we would have to migrate application A and application B, but we would be doing this for 30 different applications. In the absence of a way to represent large sub-projects in Planview and have them moveable in time, with the resources associated with them also moving as you move them, I had to work around that limitation and mostly work in Projectplace.
That being said, I did not have access to the agile module, but my suspicions are that it would not have made much of a difference due to the poor integration between Projectplace and Planview.
Planview is a resource management and project management system. Projectplace allows you to create boards and associate some of Planview's work breakdown structure as a top-level tree under which you can place cards, but there are many limitations because when you make a change in Planview, it is reflected in Projectplace. However, except for a few specific things, changes made in Projectplace are not ported back to Planview. At this point, they're two completely different products. The flaw is that there is very little integration between the two.
For how long have I used the solution?
I have used Planview Projectplace for one year in a contract position that recently wrapped up.
I am not sure what version number it was, but we kept up with the most recent, active contracts, and it was a multimillion-dollar contract. There was a lot of money spent, such as 2.5 million dollars.
It was deployed through the Planview Cloud.
What do I think about the scalability of the solution?
It was highly scalable and would occasionally slow down, but this was clearly a choice in the resources allocated to the web servers and could be changed.
In terms of usability, I thought it was far more useful than a Microsoft Project, Asana, or Jira, because, while it wasn't a particularly best-practices user interface, it was better than Jira, which is straight out of the 1990s.
Because of the project's complexity, there are probably ten different roles that span, for example, project management, product owners, various developers and testers, and so on. I would say that a couple of hundred people were involved in the initial rollout, which is probably fairly accurate.
Ideally, it will be rolled out to 1000 people, but due to the difficulties of working with enterprise, this will most likely take longer than expected.
How are customer service and support?
I would rate them a four out of five, but keep in mind that we had a person that we paid available 24/7 to answer our questions. Even so, they only get a four.
I believe the environment in which Planview and Projectplace were deployed was probably complex. It required a lot of customization, Planview should have included more people, but they only included what they chose to include.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have experience with products such as Asana and Jira.
Asana, I've used it, but I don't have any strong feelings either way. It is not something I use on a regular basis.
I have used the entire Atlassian suite, and I am very familiar with it. I have set it up for startups and established businesses numerous times.
How was the initial setup?
The initial setup was very complex. They made us take a month of classes, and at the end of the day, it could have probably been explained to me in three hours, but because a lot of people need the same type of comparative experience that I have, perhaps they needed that month-long immersive class.
What about the implementation team?
The deployment was done in-house. However, due to the size of the contract, Planview provided a lot of assistance. We had a Planview representative on call, that could cover everything with us. It was simply someone from Planview who was available to us 24 hours a day, seven days a week.
There are two approaches. The first was a failure, and the second was what I used. The overall strategy to implement Planview was across the entire enterprise, which failed due to silos and pushback. My strategy was to take a small group of people and a small project, only two or three million dollars, and win hearts and minds by having people adopt Planview and Projectplace. My project was a success, and I believe it is now being reevaluated for the use of Planview and Projectplace across the enterprise, and they will hopefully choose the approach I took for future implementations.
What was our ROI?
It will take a decade to see a return on investment because enterprise adoption requires the consolidation of the five or ten other competing tools into Planview and Projectplace. If that does not happen, the project will fail and the return on investment will be close to zero.
What's my experience with pricing, setup cost, and licensing?
That is also where the sale is. You need a full-time person to maintain Planview and Projectplace, as well as a technical person who can solve problems and do new implementations. You will need three people to manage Planview and Projectplace alone. It's a fixed cost, and each of these will most likely cost a couple hundred thousand dollars per year.
Licensing, in my opinion, was absurd. There were share licenses, one-to-one licenses where everyone with a Projectplace license could access Planview, and licenses where everyone could access Planview but couldn't do a certain set of activities that were really necessary. I would say the licensing maturity was probably a three out of five. They have a long way to go before they can scale out and retain enterprise customers.
You have to pay for Projectplace access, for example, and then you can choose between a few models. It depends on the model. If you have to add per user, then each user has an additional cost. If you choose different modeling, which I believe is more, or you get a certain amount of resources and the people are not counted was one approach, but it was extremely confusing. As a result, the way it was implemented seemed to incur additional costs everywhere.
What other advice do I have?
If you want to drive adoption, my advice is to negotiate with Planview and get all of the licensing you need ahead of time, so you don't get nickel and dimed, choose some best practices for adopting any new project management tool and an agile tool, which means you start with a small group of people, win hearts and minds, and then extend it throughout the organization.
It's one of the better tools that I have ever used. I would rate Planview Projectplace a seven out of ten.
Which deployment model are you using for this solution?
Public Cloud
*Disclosure: I am a real user, and this review is based on my own experience and opinions.