JIRA Portfolio Reviews

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.

JIRA has helped us reduce the rate of unseen or undetectable issues in the future. It has also helped us understand the demand overload across the defense team, including capacity and availability, and how we can leverage different teams to ensure overall success.

From a usability standpoint, JIRA doesn't work properly with excessive information on the dashboard. It would be beneficial if the product team could modernize or customize the dashboard to tailor it to individual users' needs. For instance, I might only require a few key metrics on my dashboard, whereas another user might need a different information set. Introducing modularity in how information is displayed or communicated to the end user could simplify the user experience and improve overall usability.

I have been using JIRA Portfolio for seven years. We are using the latest version of the solution.

250 users are using this solution.

I did work with Monday.com. It was a disaster to manage across teams, particularly with updates from individual teams. 

The deployment is easy and takes a week to complete. There haven't been any major challenges with our IT team's new upgrade version of JIRA. As end users, we haven't encountered any challenges either. Two or three people are required for the deployment.

Deployment was handled solely by our internal IT team. We did not engage any third-party assistance. Initially, we actively participated in defining our desired user experience during the deployment phase, mainly focusing on aspects such as access, SSO integration, and other functionalities. Beyond that, it was easy.

The scenario planning feature in JIRA does have a direct impact on meeting system requirements. It assists in identifying future quarterly planning initiatives, aiding in prioritizing customer-focused tasks. This functionality consolidates numerous initiatives, helping teams pinpoint the most relevant ones to achieve specific goals. 

JIRA isn't a new framework. With multiple teams involved, including product development, finance, security, data privacy, and more, the goal is to facilitate collaboration and provide end-to-end visibility, enabling intervention whenever necessary. Collaboration and visibility are key areas of focus when developing products like JIRA. Additionally, other products, such as Monday.com, offer similar functionalities, and the adoption rate in the market depends on which product effectively meets these evolving needs.

I recommend the solution.

Overall, I rate the solution an eight out of ten.

JIRA Portfolio gets used by my company's customers for its capabilities, like portfolio management, project management, and generating high-level project reviews for their CXOs.

The most valuable features of the solution for my customers are the product's ability to generate dependency reports and provide the basic view where they evaluate the task status, like to which team it got assigned with respect to certain versions and how they are placed.

In general, the valuable features of the tool are its capabilities concerning dependency reports and task status.

The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA. JIRA fails to showcase particular information missing, including how resources are placed and the capacity in the coming weeks or in a particular time zone.

The product's scalability should be improved in the future. The big setback when I look at JIRA Portfolio is that though we provide multiple kinds of templates, like JWM or JSM, in place, JIRA doesn't give you an option where you can play with multiple kinds of project methodologies. If you look at the bigger picture, Atlassian gives you a box mechanism where it has an approach where it provides lean, LeSS, and waterfall as well, and that particular flavor is missing in JIRA Portfolio.

I have been using JIRA Portfolio for the last four years. My company has a partnership with Atlassian. My company is a platinum partner of Atlassian in India. I use the solution's latest version.

It is a stable solution since I haven't faced any issues. Stability-wise, I rate the solution a ten out of ten.

Scalability-wise, I rate the solution a seven out of ten.

My customers are mostly enterprise-sized businesses. My company does serve medium segment clients as well. With respect to JIRA Portfolio, we get many queries from enterprise customers.

The delay in response from the solution's technical support causes us to beat around the bush to identify the exact issue. I rate the technical support a nine out of ten.

Positive

On a scale of one to ten, where one is difficult and ten is easy, I rate the initial setup an eight or nine since it is not that difficult. We can do a little bit of customization, and configuration is pretty much straightforward.

The solution is deployed on Atlassian Cloud.

The time taken for deployment depends upon the configuration of JIRA Portfolio and what its users do with it. Depending on what the customers want from the tool, it may take a day to a week.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a six. The product is slightly on the inexpensive front considering its competitive feature at the pricing point it offers.

If an organization requires just the reporting or portfolio view at a high level and is majorly operating on the agile front, JIRA Portfolio is the right product for them. If a company has multiple project methodologies and wants something beyond just a Gantt view in BigPicture might be the right choice.

Overall, I rate the solution an eight out of ten.

I am using JIRA Portfolio for tracking and reporting issues. We use it for the entire sprint and will have all the information there, such as testing, and all the developers.

The solution has improved our production process. We have fewer issues and everything that happens in our process is captured in the solution.

The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it.

The automation in JIRA Portfolio could improve, it takes some time. We have to do some other tactics to have the same integration. Manually integrating something will take more work than if it was automated, but the automation scripting in the solution is not simple.

The ability to connect to market-leading tools should be easier, such as Selenium. A smaller package installation would make it easier. One component would speed up the process. For example, if people choose Selimiam in Jira Portfolio should be one component, such as one .exe file which everything can be installed. A similar process should be done for Cypress to make the process easier.

I have been using JIRA Portfolio for approximately five years.

The solution is stable.

We have approximately 30 people using the solution. We plan to increase usage in the future.

The scalability of the JIRA Portfolio is good.

We have a team that provides us with support. However, we have used support that has helped us with a few aspects, but it has been minimal.

I have used ALM prior to Jira Portfolio. JIRA Portfolio is easier to use. When using ALM, creating tickets can be difficult.

The initial implementation of the JIRA Portfolio was simple. We use templates for the process.

We have seen an ROI using JIRA Portfolio.

The solution does not require maintenance.

My advice to others is to make the automation simple that is put into Jira Portfolio.

I rate JIRA Portfolio a nine out of ten.

I gave my rating of nine out of ten for the solution because it is easy to use and has benefits over ALM.

With JIRA Portfolio, you can do your portfolio after projects and right away you are able to see all the tickets of your portfolio. You can change the project which belongs in the portfolio at any moment and you can do any simulation you want. You can have many scenarios, and, when we agree with the scenario, we can push the scenario inside to JIRA.

The documentation is very well done.

Today, when we want to prepare PI planning, we have a dedicated plugin, which allows us to print a ticket. We have beautiful tickets which is an advantage. We can print tickets and put them right on the wall. It's better for PI planning due to the fact that you can read information, and it's always written in the same way.

On each ticket, you can see priority, version, et cetera, always written in the same way. If you write it directly, however, it's not always readable. JIRA Portfolio can help you during PI planning because you can write your dependencies directly. 

However, it would be better if you didn't have this manual part of the process. If we don't have to print a ticket and to put a ticket on the wall, it would be easier. It's very difficult, for example, for sizeable companies to find large rooms to do PI planning.

With coronavirus, we have to work from home. PI planning needs to be re-imagined. It needs to be virtual, not physical. It would be better if it was more like Klaxon, where your ticket is pushed to a blackboard.

JIRA is very poor at reporting.

I've been using the solution since the beginning of this year. It's been just over six months.

We introduced JIRA in 2018 and since then we haven't had any issues with stability. In my opinion, two years isn't a sufficient amount of time to really gauge stability, however, that said, it's never given us trouble.

We have about 2,000 people in the company using the solution.

We have reached out to technical support in the past, however, we prefer to use Google or search the forum. In fact, if you send a request to Atlassian, it's like throwing a bottle into the sea and waiting on a response. If I send a ticket directly to the expanded portal, I have a response 24 hours later, and if I send a ticket to Atlassian on JIRA Core, I'll get a response maybe one month later. It's easier, therefore, to search for a solution yourself than to expect a response from Atlassian.

In order to set up the solution properly, you need proper training first.

We have created a system inside our company. I do a sort-of training for JIRA Portfolio. I have coached about 1,000 people. I would estimate that you need two hours of training for a JIRA team member and two additional hours for a JIRA administrator, or a project administrator, and about two additional hours on top of that for JIRA Portfolio. If we set up, it takes one day. And of course, after setup, users will have to practice on the system to get used to it.

We compared five different products last year, including JIRA Portfolio, BigPicture (which is another plugin available on the Atlassian marketplace), JIRA Align, and a Micro Focus Solution. We also looked at Planview, which we already use to forecast for budgeting purposes.

We chose JIRA Portfolio for two reasons: firstly, due to the fact that it was connected directly with to JIRA, so we have a direct synchronization between BigPicture and Jira Portfolio, and secondly because you don't have to really plan anything to make it happen.

The difference between JIRA Align and JIRA Portfolio is that JIRA Align is for a large company, for example, a multinational and when you want to aggregate several JIRA instances. As we have only one Jira instance, it's more accurate for us to take on something like JIRA Portfolio.

In general, we are on a server configuration and not a cloud solution. That means, each year we have that specific version until we update it. I suppose since we have installed the JIRA Portfolio in January, it's the last version. However, I'm not sure.

I'd rate the solution eight out of ten overall.

If the solution would work for others depends on the size of their company. 

If we had to do the implementation again, we should have bought JIRA Portfolio at the same time as JIRA Core. I think we did a mistake by introducing JIRA Portfolio without it. When you buy JIRA Core, you have only three levels of subtask stories and epic in JIRA, and it's difficult for us to have only three different levels. With JIRA Portfolio, you can have as many additional levels as you want. We adopted a scaled agile model with squads and tribes. We need to implement a safe model instead.

We've since introduced, as a pilot, two additional levels as we believe it's better to have all level you need at the beginning of your project.

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. 

The reports generated using JIRA Portfolio are not intuitive enough. The product should also provide report customization capabilities. For instance, if I need to create a chart on the dashboard , I can only generate the chart in tabular format using the filters and widgets offered by JIRA.

Thus, the solution should allow chart generation in the form of a histogram or other chart formats. The product presently lacks visualization capabilities for reporting. In future releases of JIRA Portfolio, the workflow, including the templates and forms, needs to be further simplified; the vendor has already made simplifying efforts in past releases. There should be a portfolio or workflows for startups adopting JIRA Portfolio. 

I have been using JIRA Portfolio for eight years. 

I don't recall any instances where I have faced difficulty in accessing the solution. I would rate the stability a ten out of ten. 

I would rate the scalability a ten out of ten. 

Previously, in our company, Asana was being used, but as it's a project management tool that operates through resource utilization, it wasn't suitable for our use cases, and thus, we shifted to JIRA Portfolio. 

I would rate the initial setup an eight out of ten. Before adopting JIRA Portfolio, when I was comparing multiple products, including pricing and other differences, I found the setup process was not as simple as I expected, and it was time-consuming to find some specific information regarding the setup. 

The deployment process involved creating an account and inviting the rest of the organization's team and few integrations were needed. At the beginning of creating an account with JIRA Portfolio I had to create a migration project between Asana and Jira because our organization was working with Asana before using JIRA Portfolio. The deployment of JIRA Portfolio in our organization took just a day. 

In our organization there are ten users of JIRA Portfolio as we are using the free edition. But our company has plans to increase the usage in the future. 

The price is reasonable for the time being as our company is in the early phases and we need to cut costs as much as possible. Our company is presently relying on the free version of JIRA Portfolio, but the price of the complete version is also quite reasonable. 

I used Microsoft TFS a long time ago, and then I have also evaluated and worked on Asana. Our organization was using Asana six months ago and we realized that JIRA Portfolio is a better solution for managing the backlog and working on trial methodologies or scrums. 

The solution interface allows the view of name boards, lists, calendars, and timelines for the projects. The timeline view is highly beneficial for checking the stories dependencies on the timeline. Certain customizations can also be implemented in the timeline and the view can be changed between monthly, quarterly, and yearly. The timeline feature also provides a holistic view of all the stories in the backlog, including the completion time required for each story.  

JIRA Portfolio is easy to integrate with other tools. In my organization, I use JIRA Portfolio in integration with Slack, this is advantageous because it allows me to track whenever a team member adds a story or task. The aforementioned integration additionally allows me to monitor which project or tasks each member is engaged and I can make adjustments accordingly to the stories activities if needed.

For instance, when I check through a notification that a team member is working on a story that is not yet ready to work, I communicate it to the team member to refrain from working on that specific story. In our organization, JIRA Portfolio is also integrated with Outlook. 

The solution has allowed seamless communication between our company's managers and the rest of the teams, providing a holistic view of workflows and assisting in organizing the whole product cycle. Overall, I would rate JIRA Portfolio an eight out of ten. 

We use the tool to track issues and develop pipelines. We also use it for versatile projects in the IT department. It helps to track KPIs, present progress to the business with dashboards, and complete the QA team's plans.

What I like about the product is its extensive features, particularly the wide set of attributes for tracking issues. Jira Portfolio allows us to track not only the overall project but also specific components within it. This is beneficial for all stakeholders, including developers and business owners. For example, business stakeholders can track all issues, regardless of status. 

When using a scrum board, it only shows the current or open sprint. However, we also need to see past and future sprints, which is important for planning the next sprint. To solve this, we tried using a Kanban board instead, but since we follow the Scrum methodology, it's not the ideal solution.

I have been using the product for one and a half years. 

I haven't encountered any system issues myself. During my time with the company, we've had at least one upgrade of Jira Portfolio. 

My company has around 30-50 users for Jira Portfolio. We have around 100 licenses. 

The solution's support is good. 

We know about Jira Portfolio's work and capacity planning features. However, we do not use them. Instead, we use KPIs relevant to our business. I rate the overall solution as nine out of ten. 

I would recommend the product for IT project teams because of its stability and wide range of functionalities. Although we don't use the capacity plan feature, I recommend it. It's very useful for various purposes. 

We have integrated the tool with Lucidchart and Power BI. It has add-on functionality. 

We use JIRA Portfolio to implement the scaled agile methodology and conduct retrospectives. It's also used by us for writing bugs and managing our daily structure.

The workflows are the most valuable feature of the solution, whether for tasks, bugs, or chain requests from the site. I also like the solution's GUI, which is easy to navigate for everyone.

I think the solution can improve in graphs and the analysis part.

Considering what I would like to see in the solution that could simplify my life, I would like to mention Miro. Currently, we have to visit Miro specifically to carry out PI planning.

I use the cloud version of JIRA daily for the standards and traceability of defects coming from a point. I am unsure whether I am using JIRA Align or JIRA Portfolio. However, I think it is JIRA Portfolio because it has everything developed adequately for dev track, dev caller, and dev dash. Also, it has everything JIRA provides.
I think I have been using JIRA for three years. Also, I'm not sure about the version of JIRA that we are using in our organization. Since I work for a very big company in the Netherlands, the company manages all the tooling-related matters. So, only the testers and developers have access to the version information.
I am a customer of JIRA Platform.

The integration platform for the tooling now available is very easy to use, requiring no expertise in computer science engineering or any such related fields. Simply select the desired options from the provider's interface and use the tool without the need for explicit configuration. For these reasons, I rate this solution an eight out of ten.

I use the solution in cases when I need to report something such as escalating a scale. 

The solution includes good and fast notifications for other project team members. 

The solution's look and feel could be a bit more intuitive and user friendly. 

I have been using the solution for one year. 

The stability is rated an eight out of ten. 

The scalability is rated a seven out of ten. 

The technical support is good so is rated a nine out of ten. 

Positive

It is important to learn about the solution's functionalities and features to prepare for use. 

I rate the solution an eight out of ten.