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."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."
"Good for managing stories, sprints, hydration and releases."
"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."
"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."
"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."
"The documentation is very well done."
"The solution is stable and reliable."
"The customized workflows we can define are very valuable. JIRA's private projects is very useful as well. There are also a lot of plugins that they provide."
"In general, the valuable features of the tool are its capabilities concerning dependency reports and task status."
"The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
"Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
"Version management is the most valuable feature of JIRA Portfolio."
"The most valuable feature is that it fits very well into an agile framework, and it is especially helpful with the planning aspects."
"Lacks ability to customize and reporting can be slow."
"Some administrative tasks are difficult to perform. These could be simplified."
"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."
"The solution is very heavily vendor dependent."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"The product's initial setup phase is complex."
"If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out."
"An improvement would be if Portfolio were integrated with Office 365."
"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."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"There is room for improvement in terms of scalability."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
More IBM Engineering Workflow Management Pricing and Cost Advice →
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 50 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 Project Server, Adobe Workfront and Microsoft Azure DevOps. 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.
