What advice do you have for others considering JIRA Portfolio?

I rate the overall solution an eight out of ten.

Overall, I rate the solution a seven out of ten.

Speaking about how the tool's road mapping or capacity planning features impacted our company's project management area, I would say that I haven't used it much. I think it could be useful to have some resource leveling across bigger teams, but I don't think it is currently used for such areas. I think JIRA Portfolio is quite a complex tool with a lot of configuration options. You really need to have some people dedicated to seeing what is all in the box and what is needed for my business and gradually introduce them. Everyone can do something with Jira, but when you scale up, it can become messy so you need data architects and technical guys who can automate and glue the things properly to your business. The product's integration capabilities work pretty well, especially considering that more tools are always needed in enterprise-sized businesses. In terms of the value derived from the use of the product by our company, I can say that the integration of the tool's ticketing system with wiki and with software trackings, thereby giving a complete portfolio to users even though there are better or cheaper tools for individual things. You can have free wikis with the tool, but then they are not linked, which is good. I think the integration and also the fact that you have open APIs to connect it with other tools so that it is not a closed system. The product already has a big portfolio, but there are still many links that are valuable, and in the marketplace, it is a good tour considering all the extensions available in it from third-party products, though it may get complex to find the right solution. With some dedication, it is possible to find the right extensions for the product. In general, I rate the product an eight out of ten.

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.

I used the solution's Advanced Roadmaps feature instead of the regular roadmap feature. I liked it because it provided a visual that allowed my leadership and my partners to understand the roadmap, when we were getting work done, and when we were launching a feature or functionality. I've mostly found solutions when I go to the community. I google JQL a lot, which is probably the extent of my interaction with a community knowledge base. JIRA Portfolio helps facilitate cross-team collaboration in projects. In Jira, you can explicitly define a dependency between work, issues, and items within different projects. With Advanced Roadmaps, you can create initiatives and projects that facilitate cross-team collaboration in projects. I would recommend JIRA Portfolio to other users because it provides good visibility. Jira gives you the tools to see what work you've planned and if there are any dependencies or risks that might be creating any issues. The solution has adopted SAFe, which is a type of process management, workflow management, and software. The Advanced Roadmaps is the type of tool that helps support SAFe methodologies, which are an extension of agile project management. Overall, I rate the solution ten out of ten.

Integrating Jira Portfolio with Slack, Camunda, and other tools is part of our standard operating procedure. It helps in coordination. However, I didn't handle the integration myself. Instead, I relied on a team of more experts about the product. Our team has worked with the product previously and didn't need to overcome learning curve challenges. 80 percent of my organization is well versed in it. They can help people who don't know the product. I rate it an eight out of ten.

Before using the solution, we were working manually. I would recommend the solution to others. Overall, I rate the tool an eight out of ten.

Overall, I would rate the solution a nine out of ten. It is a good solution.

We use a cloud version of the JIRA Portfolio. My suggestion would be to come up with a customization plan or a business case regarding what you need for a particular project and what is possible and what is not possible with JIRA Portfolio. Then, present that business case to the technical team to avoid issues later. I've seen scenarios where we didn't put forth a particular question and had to reconfigure and move everything to a new project. It's best to understand the project requirements and then configure accordingly to avoid such a situation. Overall, I rate JIRA Portfolio a nine out of ten.

JIRA Portfolio is deployed on the cloud in our organization. My advice to people looking into using JIRA Portfolio is that it's absolutely fine if they want to use it as a standard deployment. However, the more they want to change anything, its complexity increases quickly. Overall, I rate JIRA Portfolio a seven out of ten.

This is a great tool for life cycle management. I rate JIRA Portfolio an eight out of ten.

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.

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.

If you have the budget, then Jira is the way to go. I rate this solution nine out of 10.

I rate the solution an eight out of ten. The solution is good, but its integration capabilities could be improved.

This is a good solution overall. I'd rate the solution seven out of ten.

I would rate Portfolio eight out of ten.

We are integrators, partners, and resellers. If an organization doesn't meet the minimum footprint for a product like Jira Align, which would be they would have to have a mature scrum or agile practice across, I'd say, a minimum of five teams, yet they're still looking to scale agile beyond the team level in Jira, we'll suggest Advanced Roadmaps, which was formerly called Portfolio for Jira. That gives the company an option to work in between Jira and something as big as Jira Align and begin to prepare to scale agile so they can get those teams orchestrated through planning and events and long-term planning, and start adopting agile ceremonies and so on by using just Jira with the Advanced Roadmaps feature. The most important thing for Portfolio is to learn how the product is intended to work and take a considered approach. Users need to be mindful of how they will plan across teams and the taxonomy or vocabulary that will be used within your organization. Those types of things will help with the configuration and change management aspects, which are also so foreign. Someone needs to take credit for everything and must be prepared to guide teams in their use for a while. There may be skeptics too around the new tools. Therefore, it's sometimes helpful to share use cases and studies from other companies in your industry. Change management aspects are part of any new tool, which is why I would say that they should have a strategy for their change management and also have a strategy or considered approach for how they're going to implement them so that everybody's on the same page. I’d rate the solution eight out of ten.

Portfolio is user-friendly, and the escalation in the organization is faster and better. I would rate it as ten out of ten.

Whether or not this solution will be a benefit to your project depends on a lot of factors, such as your requirement. I rate JIRA Portfolio a nine out of ten.

I would give Portfolio a rating of eight out of ten.

I'm an end-user. I'm not overly technical. I would rate the solution eight out of ten.

We are just customers. We don't have a business relationship with Jira. It's important to know about the database. It is important to know about databases for implementing Jira Software Management. I'd rate the solution a nine out of ten.

I would recommend that those wanting to implement JIRA Portfolio do a smaller implementation first. Once they know the features then they can do a full-scale customized implementation for exactly what they need with the appropriate features. I rate JIRA Portfolio an eight out of ten.

I rate Jira Portfolio nine out of 10.

Doing digital transformation is difficult. It's not regarding JIRA. It's difficult to change the mindset of our teams to be more agile and to adapt JIRA as a new way of working. We have to change the mindset and the mentality of the teams with a new way of working so that we can move forward. JIRA will help us to be more agile because JIRA is built for agile teams. We had to work with a consulting team based in France to help us with the organization of the process. Atlassian doesn't directly work with West African countries. So, we had to work with a French company. I would rate JIRA Portfolio an eight out of ten.

From a developer's perspective, this tool works fine and I don't have any complaints other than wanting to convert between features, tasks, etc, when a mistake has been made in creating one. The only advice that I have for people who are implementing Jira Portfolio is to make sure that they manage their licenses properly. I would rate this solution a nine out of ten.

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.

I would rate this solution as seven out of ten.

We use the cloud deployment model. I'd advise others to start with a good analysis of the solution before implementing it. I'd rate the solution nine out of ten.

If you are looking for collaboration, then I would definitely recommend the product. It is one of the easiest and not very expensive. On a scale from one to ten where one is the worst and ten is the best. I would rate the products overall as a seven. It could not get a ten. Seven leaves room for improvement.

I would rate it a seven out of ten. I don't know everything about the solution and every feature.

I would definitely suggest going for it. I would rate JIRA Portfolio an eight out of ten. To make it a perfect ten it should have a better user interface, be more clear, and more responsive.

I would rate this solution a seven out of ten.

JIRA is a very flexible solution, so if you are a mid or small-sized team, it is very useful for the team. When you have a higher scale of work, I would say the portfolio management and the reporting need to improve. You either have to build your own solution on the APIs or you have to manage how you can configure in the current flows. My rating out of ten will be seven or eight. In the next version, I would like to see better reporting and safer plugins, as well as easier scalability.

We are dealing with several products and clients, and each product has it's good points and it's weak points. I don't have an opinion because I think that a good process does the job and you can apply a good process to any tool. The tools are more and more user-friendly. Even JIRA. When you want to implement something, keep it simple and it will work. With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things. In the end, it needs to fit the process. If the process is of poor quality, then your tool will look poor. For the most part, with several tools, you can do nearly anything. JIRA is a good tool. Perhaps a little bit too much to configure and adapt, because it can be adapted to any kind of customer's needs and it's not dedicated to a specific solution, but it does the job. I would rate this solution a seven out of ten.

I like JIRA portfolio the most out of any tool I use for my job. It is my most favorite tool. It was easy to get used to using it and I highly recommend it. Personally, I say: use it. Go for it. Don't bother using other tools. Realistically, it is good to look at the other options in the marketplace. There are many companies around offering add-ons, plug-ins, and applications that are quite good. The biggest lesson I have learned in using JIRA is that you should not start with Excel. It is a good idea to evaluate your business plan and look forward to growth by choosing the right solution.