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."The tool is quite structured and has a good command set."
"It's a good tool to manage software versions, update the status, and manage tasks."
"The most valuable feature is traceability starting from the requirements until the end of a project."
"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."
"We found the requirement management and the version control features to be the most useful for our client."
"Complete traceability as per process requirements."
"We have been using it because it gives certain abilities in the automotive industry, such as auditing or keeping track of information."
"PTC Integrity has good stability."
"For what I need TFS for, I have never run into any limitation."
"I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is."
"TFS's best features include user-friendly test management, bug reporting, and ID assignment."
"The most valuable feature is simplicity."
"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 most valuable features of TFS are the test plans. We can reproduce reusable test plans in test automation. We have a lot of queries and this feature is very useful."
"Team Foundation Server (TFS) is easy to use, and we have a complete trail and traceability. We also like the access control part."
"The most valuable feature is integration, particularly if you have a .NET application."
"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."
"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."
"For complex businesses, the internal templates could have more flexibility and compatibility."
"It's not so customizable. Compared to other tools, defining user stories is a slightly more cumbersome process as an ALM engineer."
"I would like to see better integration from the architectural side."
"There are not enough reports. People would like to see something similar to what is available in JIRA."
"We are unhappy because everything that we needed required customization and this is not a plug-and-play type of solution at all."
"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."
"The reporting functionality is something that they should work on."
"The usability of TFS is not that great."
"Not all of the functionality, which is exposed by the command line interface (tf.exe) is available in the Visual Studio GUI."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS."
"TFS's CI/CD, project pipelines, and management development could be improved."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
PTC Integrity is ranked 12th in Application Lifecycle Management (ALM) Suites with 2 reviews while TFS is ranked 3rd in Application Lifecycle Management (ALM) Suites with 27 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 Jama Connect, whereas TFS is most compared with Microsoft Azure DevOps, Jira, Rally Software, Visual Studio Test Professional and Jama Connect. 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.