IBM Engineering Workflow Management vs JIRA Portfolio comparison

Cancel
You must select at least 2 products to compare!
IBM Logo
728 views|316 comparisons
66% willing to recommend
Atlassian Logo
998 views|811 comparisons
98% willing to recommend
Comparison Buyer's Guide
Executive Summary

We performed a comparison between IBM Engineering Workflow Management and JIRA Portfolio based on real PeerSpot user reviews.

Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
To learn more, read our detailed IBM Engineering Workflow Management vs. JIRA Portfolio Report (Updated: May 2024).
772,679 professionals have used our research since 2012.
Featured Review
Anonymous User
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"The most valuable features of the solution are highly customizable reports and visibility for all the higher management.""Traceability reporting is inbuilt and includes all your requirements.""We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data.""All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security.""Work distribution among team members and accountability for completion with a clearer picture.""Good for managing stories, sprints, hydration and releases.""Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."

More IBM Engineering Workflow Management Pros →

"The product makes it easy to collaborate even though it can use some improvement in that area.""The solution includes good and fast notifications for other project team members.""Having an option to view dependencies between projects and teams is great.""I think the solution's most important and valuable feature is its ability to track the issues.""Has many functionalities including good supervision and workflows.""The solution is very stable.""The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects.""The graphics and the resolution of the work are very good."

More JIRA Portfolio Pros →

Cons
"Some administrative tasks are difficult to perform. These could be simplified.""The solution is very heavily vendor dependent.""If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load.""We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it.""Lacks ability to customize and reporting can be slow.""Teams need clearer pictures of resource availability in charts and dashboards along with plans."

More IBM Engineering Workflow Management Cons →

"There should be an integration of efforts between the cloud service providers' side and JIRA Portfolio.""Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support.""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.""The HR aspect of the solution could be improved.""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.""The solution is sometimes complex to use""As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required.""In the next release, Portfolio should include more metrics and develop their portfolio planning."

More JIRA Portfolio Cons →

Pricing and Cost Advice
  • "Licensing: The solution cost is high and should be brought down to increase competition."
  • "It's an expensive investment to make, so the decision should be driven on individual requirements."
  • "It is not a free tool. We use a token-based licensing model, which is specific to IBM. The cost per token is around $115-$120."
  • "I've heard IBM Engineering Workflow Management is more expensive than other tools."
  • More IBM Engineering Workflow Management Pricing and Cost Advice →

  • "This solution has a comparable pricing in comparison to other similar products on the market."
  • "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."
  • "The price could be improved."
  • "We have a license to use JIRA Portfolio, we are not using the free version."
  • More JIRA Portfolio Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
    772,679 professionals have used our research since 2012.
    Questions from the Community
    Top Answer:We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data.
    Top Answer:Customers need to pay for a license to use this product. It is not a free tool. We use a token-based licensing model, which is specific to IBM. We have about 7,800 tokens, and including maintenance… more »
    Top Answer:There is room for improvement in the UI. The UI has to improve a lot compared to the competitive tools, like Atlassian Jira, for example. It's very easy to use. It is easy to manage and easy to use… more »
    Top Answer:The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
    Top Answer:I do not believe that the product provides value for money since I feel that it is quite expensive. I don't have a clear view of the cost associated with the licensing part of the tool. The product… more »
    Top Answer:From an improvement perspective, I would like to see the product of more integration capabilities with different platforms. The APIs work, but what my company noticed is that Atlassian offers… more »
    Ranking
    Views
    728
    Comparisons
    316
    Reviews
    2
    Average Words per Review
    825
    Rating
    7.0
    Views
    998
    Comparisons
    811
    Reviews
    33
    Average Words per Review
    514
    Rating
    8.4
    Comparisons
    Also Known As
    IBM Rational Team Concert (IBM ALM), IBM RTC
    Portfolio for JIRA
    Learn More
    IBM
    Video Not Available
    Overview

    IBM Engineering Workflow Management manages plans, tasks, the project status and acts as the critical link between required and delivered work. It provides flexibility to adapt to any process, which enables companies to adopt faster release cycles and manage dependencies across both small and complex development projects. This solution offers no-charge server software and flexible pricing models. It becomes a complete IBM Engineering Lifecycle Management solution—when purchased as a set of seamlessly integrated tools: IBM Engineering Workflow Management, IBM Engineering Test Management, and IBM Engineering Requirements Management DOORS Next.

    Jira Portfolio is an agile roadmapping tool designed to help teams build plans, envision the big picture, track progress, and share the process with stakeholders.

    Jira Portfolio is planned based. A plan in Portfolio is a complete view of the tasks, teams, and release dates for your Jira projects.

    Once you start to create a plan, there are three main factors you need to define: 

    • Scope: A list of tasks that need to be carried out in order to complete the plan.
    • Teams: Who will be implementing the work? With the correct data in place, Portfolio can estimate how long it will take for the team to complete their tasks.
    • Releases: Your scheduled release date.

    With Jira Portfolio, you can create a visual timeline to gain visibility across each of your teams and projects in a single place from a granular level and review cross-team and cross-project dependencies to prevent bottlenecks. This visibility can help you plan realistic release dates and manage your team’s capacity. The solution allows you to try out different scenarios with your roadmap and resources to help guide your decision making. Once you have a solid plan, you can easily integrate with Jira Software and commit your changes.

    Jira Portfolio allows managers to easily add team members. The tool’s powerful scheduling algorithm assigns tasks to teams while taking priorities and dependencies into account so it can create a realistic forecast for project completion. 

    Jira Portfolio Benefits

    Some of the top benefits of using Jira Portfolio include:

    • Roadmaps and roadmaps dependencies: Roadmaps list details about the tasks that need to be executed in order to complete a project, as well as predictions for when they will be completed, which teams are in charge of the task, and a list of resources they require. By setting dependencies on your team’s roadmaps, unnecessary bottlenecks are avoided.  
    • Integration with Jira: Jira Portfolio is dynamically integrated with your Jira Software project data and constantly pulls your latest data from Jira Software, allowing you to plan your projects with updated information.
    • Envision scenarios: Create what-if scenarios and save them to Jira if you decide to adopt them.
    • Reporting: Share capacity reports and more to allow team members and stakeholders to gain visibility and insights into the process.
    • Task completion estimation methods: Estimate how long a specific task will take and compare these estimations with the actual time to completion to help assess team performance and efficiency and improve the accuracy of estimation calculations over time. 

    Reviews from Real Users

    Jira Portfolio stands out among its competitors for a number of reasons. Two major ones are its roadmap creation tools and its flexibility.

    Meeta L., a lead product manager at a tech vendor, says, “The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.”

    Juan P., a senior IT project manager at Avantica, writes, “Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company.”

    Sample Customers
    Telstra Corporation, Visteon, Atos SE, Panasonic Automotive Systems, IBM Global Technology Services, CareCore National, JTEKT Corp., ItaÒ BBA, Avea, CACEIS, Danske Bank Group, APIS IT
    Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
    Top Industries
    REVIEWERS
    Computer Software Company43%
    Financial Services Firm43%
    Comms Service Provider14%
    VISITORS READING REVIEWS
    Manufacturing Company23%
    Government13%
    Computer Software Company10%
    Financial Services Firm8%
    REVIEWERS
    Computer Software Company34%
    Manufacturing Company14%
    Educational Organization10%
    Financial Services Firm7%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company16%
    Manufacturing Company10%
    Government7%
    Company Size
    REVIEWERS
    Small Business14%
    Midsize Enterprise29%
    Large Enterprise57%
    VISITORS READING REVIEWS
    Small Business12%
    Midsize Enterprise8%
    Large Enterprise80%
    REVIEWERS
    Small Business26%
    Midsize Enterprise20%
    Large Enterprise54%
    VISITORS READING REVIEWS
    Small Business16%
    Midsize Enterprise10%
    Large Enterprise74%
    Buyer's Guide
    IBM Engineering Workflow Management vs. JIRA Portfolio
    May 2024
    Find out what your peers are saying about IBM Engineering Workflow Management vs. JIRA Portfolio and other solutions. Updated: May 2024.
    772,679 professionals have used our research since 2012.

    IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 15 reviews while JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 55 reviews. IBM Engineering Workflow Management is rated 6.8, while JIRA Portfolio is rated 8.2. The top reviewer of IBM Engineering Workflow Management writes "Offers good traceability elements but UI needs improvement ". On the other hand, the top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". IBM Engineering Workflow Management is most compared with Jira, Codebeamer, Microsoft Azure DevOps, GitLab and Polarion ALM, whereas JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Azure DevOps, Microsoft Project Server and Adobe Workfront. See our IBM Engineering Workflow Management vs. JIRA Portfolio report.

    See our list of best Enterprise Agile Planning Tools vendors.

    We monitor all Enterprise Agile Planning Tools 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.