We performed a comparison between PTC Integrity and TFS based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."PTC Integrity has good stability."
"It's a good tool to manage software versions, update the status, and manage tasks."
"Complete traceability as per process requirements."
"The solution is flexible in terms of customization. You can bend and reformat it in many ways. You can also customize the APIs and public functions."
"The most valuable feature is traceability starting from the requirements until the end of a project."
"We have been using it because it gives certain abilities in the automotive industry, such as auditing or keeping track of information."
"We found the requirement management and the version control features to be the most useful for our client."
"The tool is quite structured and has a good command set."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"The most valuable feature is the backlog."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"The interface is easy to navigate."
"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."
"Version Control: TFS offers both the centralized “TFVC” version control technology as well as the distributed “Git” version control technology."
"This solution enables us to link all items usefully, in the way we use Agile."
"I feel that the test plan and test tools are more manageable in TFS."
"There are not enough reports. People would like to see something similar to what is available in JIRA."
"To be honest, the third controller system is kind of old. There are lots of transactional changes that have not been implemented in PTC. If you have a larger project, for example, whenever you give bits and need to change 10,000 files you can just commit them. But here the work style is a little more file based, so you'll have to take care of almost all the files individually. It's not a single commit like you do here, but rather you have to allocate time for each component or file that you want to check in or commit. That's a very big issue."
"I would like to see better integration from the architectural side."
"It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer."
"It's not easy to plan on this solution and it's not user-friendly. The interface should be more like a web interface. It's not easy to use."
"For complex businesses, the internal templates could have more flexibility and compatibility."
"The web version does not have all the functionalities of the non-web version. Administration and adding/removing fields, etc. cannot be done on the web version. People want solutions that are compatible with Android. I also want to have a version by which I can bulk edit all the fields."
"We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all."
"It has been really dated. When you start to work more in an agile environment, it is not really that flexible. They tried to replicate the look and feel of Jira, but it is not quite there. It was nice to use in the past, but it is not as flexible now with the changing development environments and methodologies."
"The solution's server for deployment needs to be improved."
"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."
"We encounter issues with backups."
"Merging branches is definitely one of the more challenging aspects for people new to TFS."
"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."
"The reporting functionality is something that they should work on."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
PTC Integrity is ranked 12th in Application Lifecycle Management (ALM) Suites with 10 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 93 reviews. PTC Integrity is rated 7.0, while TFS is rated 8.0. The top reviewer of PTC Integrity writes "A flexible tool which you can bend and reformat in many ways ". On the other hand, the top reviewer of TFS writes "It is helpful for scheduled releases and enforcing rules, but it should be better at merging changes for multiple developers and retaining the historical information". PTC Integrity is most compared with Codebeamer, Polarion ALM, Jira, Microsoft Azure DevOps and Rally Software, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software and Visual Studio Test Professional. See our PTC Integrity vs. TFS report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites 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.