Anonymous UserSenior Management Consultant at a consultancy
MartinMonteiroSr Domain Specialist at a healthcare company
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"The graphics and the resolution of the work are very good."
"With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"The product makes it easy to collaborate even though it can use some improvement in that area."
"The integration is very good. We've more or less integrated with everything including reporting and registering."
"The customized workflows we can define are very valuable. JIRA's private projects is very useful as well. There are also a lot of plugins that they provide."
"We've brought our portfolio altogether. We have had multiple ways of reporting out what our portfolio is, whether it's in Excel, Word, or in different places. We brought all of our projects together in one place. That has worked out well for us. We've been able to manage the work on Gantt charts and our resources better. The big thing for us on research and development is around managing people's time, on which projects they are working on, and how much effort does it take to launch our projects."
"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."
"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."
"I like that everyone is able to see the same data. All of our users who aren't just time reporters have read access to all the data that is out there. So, it is one source of truth where everybody can go in and see the exact same data that everybody else sees. It is transparent."
"The portfolio management gives you a view of all the projects as well as all the information about the total amount of effort, time, and cost being spent on the projects. It gives the organization how much money and effort should be spent towards projects so they can budget and do better capacity planning in the next fiscal year. It gives them visibility into their resources and if they have capacity."
"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."
"We have a fairly good picture of time tracking."
"The look and feel of it is pretty clean."
"If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out."
"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."
"I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."
"The initial setup could use improvement."
"The product could do with more flexible reporting."
"Some key features like integration, big data warehousing and data modeling need work."
"The workflow needs improvement."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"Recently, we have gotten on a newer version. We're currently on version 15. Some of the things that we've been running into roadblocks on, it looks like the solutions will be coming out in versions 17 or 18. So, we have to upgrade before somethings can get completed."
"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."
"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."
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"I would like to see more documentation pieces. Right now, they do have the content repository. I would like to see more out-of-the-box features with document repository capabilities."
"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."
"There's still a lot of reluctance within the organization. We're not using all of the capabilities that we have today. We're still doing our strategic and capital investment planning on spreadsheets rather than using the capabilities that exist within Enterprise One. I definitely need to leverage the experts here at Planview to help drive a culture change. There's just a lot of reluctance on behalf of people within the company to put data into the tool."
"Our version is definitely set up a bit more waterfall world. It would be better if some of the agile features were more in the standard product."
"The pricing of the solution is expensive."
"We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
"The pricing continues to get higher."
"The product is really not very expensive."
"We pay our fees annually, although monthly payments are also available."
"We are on the Flex licenses."
"We have unlimited licenses for all of our functionalities. Since we went global, we went with that model."
"The cost of other pieces and integrating them in needs improvement."
"We have portfolio managers, resource managers, project managers, and time reporting licenses. These are the licenses that we have."
"I don't think we have necessarily purchased everything that I would have liked to have seen."
"We have several hundred licenses. It costs us several hundred thousand dollars a year."
"We overbought our licenses. We looked at our needs three to four years down the road and tried based our contract on that. However, we were over aggressive. We use about a third of the licenses that we have. We're looking to adjust the makeup so we can start utilizing the amount of money that we are spending. Right now, we're overspending, and my organization is not seeing the value in Planview because we are paying so much for licenses that we're not using."
"Our licensing costs are probably $150,000 to $180,000 a year with 270 licenses total."
The agile portfolio management tool, built for JIRA.
With Portfolio for JIRA, you can plan and forecast a realistic roadmap, make data-informed decisions when the unexpected happens, and keep everyone in the know.
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 13 reviews while Planview Enterprise One is ranked 1st in Project Portfolio Management with 46 reviews. JIRA Portfolio is rated 7.8, while Planview Enterprise One is rated 8.0. The top reviewer of JIRA Portfolio writes "Good documentation, good visualization of tickets, and relatively stable". On the other hand, the top reviewer of Planview Enterprise One writes "Provides end-to-end work management for the full spectrum of types of work in one tool". JIRA Portfolio is most compared with Microsoft Project Server, Smartsheet, Planview PPM Pro, Broadcom Clarity PPM and Trello, whereas Planview Enterprise One is most compared with Planview PPM Pro, Broadcom Clarity PPM, Microsoft Project Server, Sparx Systems Enterprise Architect and SAP Portfolio and Project Management.
See our list of best Project Management Software vendors.
We monitor all Project Management Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.