Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
$81.85
per month 10 users
Planview Portfolios
Score 8.3 out of 10
N/A
Planview Portfolios is an end-to-end project portfolio management and enterprise architecture management tool. It includes two components: Portfolio and Resource Management and Capability and Technology Management. The platform is available as a cloud-based or on-premise service.
Planview Portfolios is the market leader in the area, the flexibility of the product and the continuous investment by Planview makes Planview Portfolios currently the best in the market. The support organisation for implementation and run of Planview Portfolios rounds off the …
Verified User
Professional
Chose Planview Portfolios
In our organization we selected Planview Portfolios for the capabilities it offered.
We are currently using Planview AgilePlace. Also we use Tasktop Hub for integrating with other applications within the organization. We would like to use ProjectPlace which is integrated with Planview Portfolios in the future.
Planview is a much more robust Resource and Portfolio Management tool. It is easier to use and provides drill down visibility to address critical issues.
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
Planview Portfolios allows the ability to establish strategic goals, set financial targets, and then associate work so that business areas can easily see current forecasts compared to baselines. Lower-level resource management is handled nicely within Portfolios, allowing Resource Managers to pivot the assignment data quickly to do a variety of analyses. There is room for improvement in the ease of connecting Ideation to Delivery. Companion tools are available but it does not flow smoothly between applications. I would rather have Ideation embedded within Portfolios so that projects can be created/aligned more easily.
Capture potential opportunities using the Requests Module and analyze and rank these opportunities via lifecycles and promote (dispatch) approved opportunities into Projects. Information captured during the request process automatically get transferred to projects.
Robust schedule management; time reporting; resource management and financial planning and management
Risk and Issue management controlled via robust lifecycles.
Extensive reporting capabilities via SSRS and Power BI Dashboards and delivered to users via tiles in Project and Portfolio views.
this is the area I can see Planview Portfolios is very much lagging behind. If you see Atlassian, they are having a robust API information and using that we can securely access the necessary information based on the role. I think a similar kind of approach need to done in Planview Portfolios as well.
User Information and Resource information is separate. Expecting that, during the User creation, when a resource is linked, automatically all the basic fields should be populated with the values, also if a person is having an User account there is no way for that person to know that what User role that he/she is having. Also none of the reports covering that details.
Automation - It's mentioned using the UiPath some of the Automation has been done in the User creation but don't find any necessary document for better understanding.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
We have been a Planview customer since 1999 and have seen it grow and mature as a tool. We have looked at other tools and have found that PV continues to meet our needs and is easy for our resources to use. They work to stay up on the project management industry and the direction it is going, keep on on current technology so that we can work more effectively, provide excellent customer support and have great pricing for what they offer. We can purchase only the modules we need versus buying a tool where we would only use a portion of the functionality.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
There is a learning curve that needs to be overcome for new and occasional users. Need to clearly training users on how to filter the data with "Portfolio's"
We are long time Planview users and its availability is only limited to our internal SLAs for nightly backups. I have never experienced any unexpected or prolonged software downtime from Planview itself.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
Going through proper channels of support is fine for minor to moderate issues. However, lately the critical issues that arise have been frequent and the standard support cases do not always seem to relay just how critical these issues are and we have to utilize our customer rep to help escalate. Fortunate to have that escalation method.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
Always have a pre-implementation meeting or conference call with Planview to ensure all are on the same page, disclosure of all and any customization (including reports) and plan for support after implementation of a specified amount of time with the assigned implementation resource. And document everything
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.
Odoo, like this platform, has allowed us to efficiently organize our projects so that they can be prioritized by importance, to know which is the most urgent, in addition, it has also allowed us to assign work in an organized way among our collaborators, and their reports have allowed us to improve.
The positive impact is the ability to manage our projects enterprise wide.
Managing and reporting on projects and programs via portfolios makes it easy to identify troubled projects/programs that need immediate attention.
The negative is that pushing too much change too quickly is hard for us. We need to get our users focused on the basics of PM before we can adopt everything else. We need to introduce change to different companies based on their maturity level. Too much change too quickly is not always beneficial. We need to focus on core competencies.