We can have time entries, projects, reports, and the portfolio all in one system
What is our primary use case?
PPM Pro started out being just an IT application. Within the IT PMO, we needed a way to track our portfolio. We had spreadsheets with project data on them and it was cumbersome. Being able to get some portfolio analytics was important to us, and then our project managers were using all different kinds of tools. They were using MS Project, Excel, and all good stuff, but the templates and everything was all over the place. I liked PPM Pro because we could essentially build out the forms, the fields, and everything to mirror a project charter. The risk and issues log was already in there. Instead… more »
Pros and Cons
"The dashboards are one of the most valuable aspects of this solution, although, we've only developed a few that anyone's using. There is more maturity there and, of course, we're a month and a half into this, but getting our executive leadership to see these things is half the battle. I think dashboards are going to be critical."
"From a usability standpoint, the part where there are people on the tasks section on a team is a little challenging. Then for some reason, the in-demand reports are embedded in the resource section and to run them is just completely different and separate from the reports entity which is a lot."
What other advice do I have?
I would have changed the project team that implemented this and I would have found someone much more technical if I had known that Planview wasn't going to do it. I'd probably try to find somebody who knows more about reports and dashboards because that's where the real bread and butter of it is. Right now we're getting by with some reports. Having that resource, which we just don't have right now, would have been helpful for us to really knock it out of the park when we went live with it. My advice would be to find someone technical to build it and then I would rearrange some of the…