JIRA Portfolio Reviews

As a user, my primary use case for JIRA Portfolio is mainly around project management, portfolio management, budget planning, and ideation. It is IT projects specifically related to the oil and gas domain.

The main feature of JIRA Portfolio that I find valuable is its alignment with the scaled agile framework. The portfolio planning, cross-program dependencies, and extensive reporting are very useful. The reporting feature is comprehensive and easy to use, which aids in planning and forecasting.

Originally, we used JIRA for help desk ticketing, but the biggest use case for the solution now tends to be supporting Kanban and scrum-based agile development.

JIRA Portfolio was a much more appropriate solution to support our move to agile systems development and implementation.

We use Jira Portfolio in our organization for issue tracking and task management. We had many projects. We didn't use it much for forecasting, but we did use it a bit for release planning by assigning tasks to releases. We didn't use it for project management or scenario planning; we just used it for tasks.

The tool needs to improve its speed and response time. 

Our organization uses the solution in scrum meetings and cycles for the internal teams. JIRA Portfolio is also used for tracking stories, and roadmap planning. In our company, I am also working on JIRA administration to configure the entire cycle of the stories and Epics by adding customized fields and workflows.

I have used JIRA Portfolio to adjust and add flexibility to the workflows according to the team's input in our organization regarding their working process. 

The backlog view feature is highly valuable and helps manage stories. JIRA Portfolio assists in prioritizing which stories the team in our organization should work in sprint and which ones can be postponed. The sizing of each story and planning the ideal size for each sprint is also carried out using JIRA Portfolio. 

I started using JIRA Portfolio for development. Typically, it was useful for backtracking in the first place and later for project planning. I tried to use it to track every kind of issue.

The most valuable feature of the product stems from the fact that it is able to give an oversight of what work is in progress while having a kanban board or similar visuals that can be used in an international context with video calls and where you can get away with just a piece of paper because you are not the same site. The good thing is that you don't lose the tickets, and you can connect them in different formats. You can connect the ticket if you want to track more static information on the wiki page, and such integration helps a lot, along with the other integrations with source code tools and other products.

The solution is simple to use. We use JIRA Portfolio with Azure Logic Apps, and it is easy to integrate them.

The solution should provide a monitoring interface for the customers to have more information about the issues. We cannot receive the information by mail. We can use the tool to share reports, but it should also have a space for customers to add comments. JIRA should provide more online video resources explaining how to use the solution.

We use the solution for large-scale agile planning in our organization and ensure that every project aspect is properly accounted for, like individual products, logged correctly, and progress tracked through the portfolio dashboard. The scenario planning feature impacted your strategic decision-making.

I use this data for resource allocation, called corrective measures or actions where you can take corrective measures beyond reporting. I also use this for backlog grooming and tracking progress.

Team collaboration has been enhanced because JIRA provides a comprehensive overview of key initiatives and their respective stages. This facilitates a better understanding of the progress of tasks, whether independent teams or specific individuals are working on them. Our integration with Slack allows seamless communication, enabling us to create tickets directly from Slack, which is synced with JIRA. This feature is highly convenient for fostering collaboration across our organization's product, technology, QA, and other teams.

The primary use case is project management. 

The entire features that are required for managing the product's communication between the team there are valuable. Managing product development and managing inter-team communications are also valuable features.