We performed a comparison between IBM Engineering Workflow Management, Jira, and TFS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Atlassian and others in Enterprise Agile Planning Tools.
"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."
"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."
"Work distribution among team members and accountability for completion with a clearer picture."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"Traceability reporting is inbuilt and includes all your requirements."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"The solution helps a lot with scrums."
"The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view."
"In general, the GUI is nice."
"Work management software that has the flexibility to be configured for any company. It's stable, scalable, and offers responsive support."
"You can record your unit testing, regression testing, UATs, et cetera."
"The way we can define and customize the search queries for the tickets in Jira is most valuable."
"The integration of other open source tools with Jira is very useful. It allows us to create documents and transcriptions, making it versatile beyond software development."
"The most valuable features are test case writing and bug tracking."
"The interface is easy to navigate."
"Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology."
"Stability is okay."
"TFS is very user-friendly."
"Basically, the capacity to construct various products is something I find handy."
"This solution enables us to link all items usefully, in the way we use Agile."
"The API for managing TFS programmatically is very powerful, you can listen on work items changes by TFS events."
"Some administrative tasks are difficult to perform. These could be simplified."
"The solution is very heavily vendor dependent."
"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."
"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."
"There needs to be easier integration with third-parties — personally, this is the biggest issue for me."
"Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira."
"It should be less expensive."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement."
"I would like to see test execution modules."
"We would like to see integration between Tempo and Jira."
"The solution is stable but could improve."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
"The usability of TFS is not that great."
"The project management side should be addressed and the project and release planning should be somewhat extended."
"The dashboard and the customization of dashboards is an area they have to work on."
"Its pricing could be improved."
"There should be management of the project built-in."
"The solution should have better dashboards."
More IBM Engineering Workflow Management Pricing and Cost Advice →
