We performed a comparison between IBM Rational ALM, Jira, and TFS based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."The word emulation and importing is good."
"The integration with Git works well."
"One of the key advantages of IBM Rational ALM is its workflow capabilities, which enable seamless collaboration between development and production teams and ensure that all stakeholders are aware of the progress and readiness of the solution. Additionally, the solution is good for integration."
"Everyone in a team can work on the same platform and share the same information."
"We have something called the GC (global configuration), which is a unique feature compared to any other competitor we have in the ALM space."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The most valuable feature is the reporting of the CPU usage on the dashboard."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"The solution is easy to use and user-friendly."
"When combining Jira with Bitbucket, you have the possibility to ensure continuous integration and other functions which is highly appreciated by our software development team."
"The scalability is good."
"The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards."
"The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
"A most valuable feature involves the ability to customize the entries and to update them quickly."
"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."
"The timeline management is great."
"The most valuable feature of TFS is integration."
"The interface is good with TFS."
"Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part."
"TFS is very user-friendly."
"Since it is a robust solution, I face no performance issues. Also, considering how well the implementation process of the solution was carried out, we never faced any issues while using the solution."
"The most valuable feature is the backlog."
"I like the build management features and the integration with Jenkins and many other tools."
"User alerts are very helpful for knowing when work is required."
"I would like to see better reporting features. The out-of-box reporting is - I don't want to say limited - but the focus is on the Scrum and Sprint reports. We need more reporting features regarding the history of the work, tracking it more deeply."
"In the next release, we expect a traceability metrics configuration where we can configure the user stories. We also expect them to improve or simplify the query process."
"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The GUI is a little bit outdated."
"Some improvements to the user interface (UI) would be helpful, such as exposing more services to make it easier to customize to the needs of each customer."
"The reporting functionality needs to be improved."
"I think nowadays people are getting into Jira and other tools. What is happening is, this solution is becoming more traditional, whereas Jira and other tools are more attractive for the new users to learn and start using because of the graphical interfaces."
"The product must be more user-friendly."
"Sometimes it takes time to load the data."
"If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side."
"The solution's stability could be improved, and it could be made more robust."
"Tracking is important but the built-in features don't meet our needs."
"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."
"I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira."
"Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed."
"There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"We encounter issues with backups."
"Integration from Visual Studio could be improved."
"Merging branches is definitely one of the more challenging aspects for people new to TFS."
"The tool needs improvement in stability."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS."
"Access and permissions are confusing when attempting to include basic manual testing functionalities."
"Currently, we are looking for a solution with which we can incorporate third-party development sites or third-party project teams into the system. Because it is on-premise, it is a bit problematic because we need to have a VPN or something else in the system. A cloud-based solution would be better for us, and that's what we are looking for. Our biggest problem is the external connection, which, of course, is limited by our own IT. It would be good to have some kind of publishing service for this external connection. It might be there, and it might be that our IT is making it impossible for us. Its template editor could be easier to use. Currently, customizing the project templates according to your needs requires some work."
