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."Traceability reporting is inbuilt and includes all your requirements."
"Work distribution among team members and accountability for completion with a clearer picture."
"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."
"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 most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"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."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"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."
"The backlog view feature is highly valuable"
"Managing product development and managing inter-team communications are also valuable features."
"The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"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."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"The solution is very heavily vendor dependent."
"Lacks ability to customize and reporting can be slow."
"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."
"Some administrative tasks are difficult to perform. These could be simplified."
"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."
"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."
"The workflow needs improvement."
"Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved."
"The solution's look and feel could be a bit more intuitive and user friendly."
"There is room for improvement in terms of scalability."
"Another thing could be to have an easy way to manage the Portfolio and have more ways to share and to show graphics and reports"
"If you want to generate a report for individual usage, it's difficult."
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 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.