We performed a comparison between Jira, OpenText ALM Octane, 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.
"It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
"It has enabled us to keep track of features or projects. Previously, we used to manually keep track in Office. We now have a centralized repository for all the information."
"There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training."
"Integrates with other components."
"It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user."
"There are many good things about Atlassian."
"The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it.."
"We are seeing some real improvements in the way we do things. We are becoming more agile in the way we do it because of that and in a way that stories are managed. Stories are given lifecycles as opposed to just being entities within a tool."
"The solution natively supports Agile-Waterfall hybrid software development at an enterprise scale. This is very important to us. Because even though the company wishes to go Agile, we still have projects which follow a Waterfall methodology. In order for us to accommodate both, we needed some sort of hybrid system. Because if we are using a fully Agile system, then the reporting might not be correctly extracted."
"The key feature is the usability. It is fast to learn and easy to use. It's very intuitive to work with. Most of the important functions are available via a few clicks, compared to other tools where I have to open a sub-menu and then a sub-menu and another sub-menu, and then press a button."
"It is a very stable tool. The tool has been in the industry for so many years. Stability-wise, I rate the solution a nine out of ten."
"The user experience is a lot better than any tool that I have used before. Overall, it is great. It has a smooth interface, which is very user-friendly. It makes it easier to work together and have more transparency and customization, which is very good."
"With an Octane project, we have our automation, our requirements, our tests, our pipeline into build-and-deploy, and the ability to identify problem areas. It makes things quicker because it's more along the lines of an automated process."
"Current version of the solution is fairly stable."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"The most valuable features are test case writing and bug tracking."
"The most valuable features are related to source code management. Using TFS for source code management and being able to branch and have multiple developers work on the same projects is valuable. We can also branch and merge code back together."
"We use TFS for forecast management."
"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."
"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."
"Work item management integration with source control."
"User alerts are very helpful for knowing when work is required."
"It has great functionality: work items, backlogs, source code, build releases, and it's easy to use."
"We'd like to see more collaboration tools implemented within the product itself."
"It would be ideal if the solution could be available as a mobile application."
"The filtration could be better."
"Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc."
"I find the dashboard to be Jira's most problematic feature."
"I want the tool to integrate connectors."
"I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be."
"It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
"Updating items, sorting, bulk updates—these things could have a bit more flexibility, but it's still possible to do them."
"The limitation of Octane is that we can't do a release outside of the sprint. We can only plan the release in the sprint. With Agile and JIRA tools, we can plan the release outside the sprint and do a global release of all the projects from the sprint."
"I think the area of release management in the tool is an area of concern where improvements are required."
"There's a trend in our requests to have the ability to export data, en masse, out of Octane. There are capabilities within Octane to export data, but there are specifics around test suites and requirements and relations, as well as certain attributes, that we would like to be able to export easily out of Octane and into a database or Excel."
"When I manage projects that are being created in ALM, I have a standard template, but I don't have a template for them in Octane. I literally have to create the project from the ground up every time, which for an administrator, is a nightmare solution"
"Because JIRA is a leading tool for both development and requirements management - everybody is using JIRA - I'm pretty there will be a use case where people are trying to connect between ALM Octane and JIRA. The back-end configuration of the synchronization with JIRA could be simplified. The architecture is really complicated. We required a lot of machines to build the cluster and the configuration was not really clearly described within the documentation. This may have something to do with the fact that the software is pretty new."
"Security and security management, meaning the integration of the security, could be enhanced. We know about Fortify, but it would be better to have security features in the original Octane platform without the need for another solution or another application."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"The solution should have better dashboards."
"I understand Microsoft is phasing out TFS in favor of Git, so I would steer anyone interested in TFS to look into Git."
"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."
"Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements."
"As an end-user, I expect the solution's performance to be faster while staying as stable as possible."
"The dashboard needs more enhancements."
"There should be management of the project built-in."
"TFS isn't a great tool if you're on the cloud."
