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."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."
"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."
"Traceability reporting is inbuilt and includes all your requirements."
"Work distribution among team members and accountability for completion with a clearer picture."
"The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian."
"Jira offers tools for managing projects using Agile methodology. I think it is good to encourage the development team to use Jira, so that the organization benefits from the proper execution of projects on time. Basically, it helps our organization to execute in a better way."
"Jira is very user friendly, easy to install, and easy to access."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"The two features that have been most valuable have been backlog management and sprint planning and tracking."
"It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks"
"It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer."
"The API for managing TFS programmatically is very powerful, you can listen on work items changes by TFS events."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"The solution is very much stable."
"As far as queries are concerned, creating, grading, or customizing the queries as a primary requirement is very easy to do."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"It's an integrated system that includes all the information that we need to deliver our products smoothly and to track the progress of each piece of code."
"It is a stable solution."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"The solution is very heavily vendor dependent."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"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."
"Lacks ability to customize and reporting can be slow."
"I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool."
"The Jira dashboards could be more useful. The dashboards have good widgets but the comparison of data over time or extraction of trends from the data is not easy."
"I'd like the solution to be more secure."
"Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows."
"Integration with some of the automation tools could be improved."
"If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
"We'd like to see Jira have more integration with a development ID."
"The solution could improve by having its own tool for quality lifecycle management."
"The manageability and performance of the product are areas of concern where improvements are required."
"The project management side should be addressed and the project and release planning should be somewhat extended."
"The solution is stable but could improve."
"TFS and MTM have their own style of working and they are different from other tools like Jira or TestRail, which are simpler and easy to use."
"There are many things that I cannot do, and I have a lot of bugs."
"I understand Microsoft is phasing out TFS in favor of Git, so I would steer anyone interested in TFS to look into Git."
"TFS needs to be stable."
"They should have design patterns in TFS for the development team, and design patterns for the QA."
More IBM Engineering Workflow Management Pricing and Cost Advice →