AzureDevOps Server (formerly Team Foundation Server, or TFS) is a test management and application lifecycle management tool, from Microsoft's Visual Studio offerings. To license Azure DevOps Server an Azure DevOps license and a Windows operating system license (e.g. Windows Server) for each machine running Azure DevOps Server.
N/A
Teamcenter
Score 8.1 out of 10
N/A
Teamcenter is a product lifecycle management system designed to help organizations integrate and standardize product development processes across functional silos.
Jira has been growing in hardware design teams since is being integrated with CAD software. The best of Azure is that you can manage since level of access control to multiple types of teams. Another bonus is that Jira has more mobile features that let your team stay connected …
Because of the microsoft ecosystem and the product is also build on ms services cloud which uses azure internal services so it is easy to integrate. more reliant support available for the microsoft services because of the well established user community of the product and …
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention …
Managing projects is a breeze using Azure DevOps Server, and the tool also automates testing and checks to see if the project is within its scope. Intuitive, with a low learning curve for novice users; it's also simple to collaborate on projects and keep tabs on their progress …
Honestly speaking, GitHub is better in terms of version control and JIRA has better functionality when it comes to Agile boards, other than that, the UI could have been a bit better for Azure DevOps Server. In all other areas, I feel overall Azure DevOps Server is better.
In my opinion, DevOps covers the development process end to end way better than JIRA or GitHub. Both competitors are nice in their specific fields but DevOps provides a more comprehensive package in my opinion. It is still crazy to see that the whole suite can be used for free. …
I was new to the agile methodology when it was first introduced to the Enterprise. Different project teams opted to leverage different project management tools, two of the most common being Jira and DevOps. For someone overcoming a huge learning curve already, I felt that …
My organization already has an established Microsoft relationship which allowed us to move faster in procuring the product. The alternative would require my large organization to move at a snail's pace at procurement. This is not necessarily a hindrance for most other …
I was not involved in the purchase decision for this product. Since I have started working at my company, we have always used [Azure DevOps Server]. So I can't comment on how it performs vs its competitors. I have used many project management tools that are not as robust, but I …
I've used and currently use JIRA, which is a similar software to Azure DevOps Server. Azure DevOps Server is more detailed and comprehensive than JIRA. They both offer many of the same features and capabilities but Azure has a better overall interface and is more in-depth. It …
Azure DevOps Server is a fantastic tool and my favorite for organization and management of large application building projects. It was selected for its ease of use with a user-friendly design that allows any team members, particularly outside of developers, to quickly get up to …
At the time we brought Azure DevOps in-house it really was the only game in town. Our company migrated from Visual SourceSafe to TFS to Azure DevOps without any issues or downtime. Git isn't overly intuitive so I never recommend it and shy away from it. I loved it when …
Microsoft Azure DevOps is the one that integrates everything you can possibly use and provides a solution that eases your developing process. It has a strong support community and well-written documentation. No matter what you do, you will always find the right pipeline. It is …
Azure DevOps server has quite an upper hand while we compare it with other tools in the market. Its not just a tool in fact its been a complete suit. If we look out at other products available as alternative options to Azure DevOps Server, they are meant for a specific purpose …
TFS gives and edge over JIRA for inbuilt version controlling that TFS has. TFS provides a GIT version control repository that offers centralized TFVC and distributed GIT Version control. Version controlling is a key feature that promoted TFS over JIRA in the implementation of a …
The advantage of Team Foundation Server is the integration capability with Microsoft technologies and products, such as Visual Studio. Although this is an important consideration, Team Foundation Server is not a straightforward tool and needs to be improved to work seamlessly …
Git and GitHub are very popular right now and they are OK. But they do not integrate automated Testing and Building... The Work Item Management of Jira is about as complicated as the one of TFS so we use Trello. The other Source Control Systems are more complex to use because …
Teamcenter performs better compared to other two tools, due to it's efficiency with collaboration of multiple teams and acting as a central repository.
Earlier, some of the companies acquired by my organization were using PTC Windchill, but the overall stability, user experience and depth of functionality which are provided by Teamcenter doesn't match with any other PLM software and thus, all the acquired companies which were …
I was using the SAP and Teamcenter integration, Teamcenter and SAP often reside in separate data silos within a company. Integration breaks down these barriers, enabling a single source of truth for product and manufacturing data. Information exchange between engineering …
Oracle PLM offers a comprehensive platform for product lifecycle management. Its strengths lie in integration with other Oracle solutions, providing a unified ecosystem. However, compared to competitors, its learning curve can be steep, impacting initial adoption. Yet, once …
Teamcenter has a unique way of collecting data that is different (Items) but works well once you have made the mental switch. Other systems are more object/relationship based. Windchill is quite mature and within the areas it overlaps Teancenter is quite competent. Enovia …
Teamcenter provides robust capabilities for managing product data, including CAD files, documents, bills of materials (BOMs), specifications, and other related information. It offers version control, change management, and secure storage, ensuring that teams have access to the …
Teamcenter was selected almost 21 years ago in the manufacturing area and for almost 11 years the engineering area merged the PLM (Windchill) with Teamcenter due to its strength.
In our case it was best suited when we started working remotely, we were able to track everything in out projects easily, able to share our codes, give reviews for the codes and also create integration and deployment CI/CD plans for the release and testing. It helped our team members with the productivity, early prototyping and release. Create summarised reports of different aspect of our projects. Even in other scenarios it is one of the best tools to use for collaboration and project management. I haven't found any specific scenario where it is not appropriate
Teamcenter is perfect for working in large-scale projects related to manufacturing and engineering where collaboration and management of data are crucial. It is evident where the complexity of the products is high such as in automobile and aerospace industries. Some of its features may seem too elaborate for the small business with a less complex process and therefore too expensive. It is less useful in organizations that do not have complex PLM needs or have less IT capacity to implement the system.
Data Management: your Parts divided into Item Types.
Data Management: You can easily add pseudo folders to segregate data inside. You don't have to look for anything now.
Change Management: Use the built-in or customize it. Now, you have workflows and can decide who is responsible for every task. It's done automatically.
Project Management - built-in MS Project, can manage tasks and still have a Gantt chart from it.
CAD integration - a lot of time saved when single source of true.
I'm going to be a little blunt here. So the way how MPP and bombs are getting separated out, that is creating some issues when we want to implement end-to-end processes. The bomb team, the manufacturing or the sector manager kind of team, tries to give various features for the materials and bombs related to them, but all of those features are not available for BOP. For example, solution variant creation. When we have a variant based structure, I can create a solution variant for bombs, but I cannot create a solution variant for BOPs and this is, I would say something of a gap that Siemens should address and get it fixed. We have to do customization, but if the product is itself giving us then this is an elegant way to push it further. This is what I would say is the issue.
Because we are a Microsoft Gold Partner we utilize most of their software and we have so much invested in Team Foundation Server now it would take a catastrophic amount of time and resources to switch to a different product.
Because of our current customer needs, we will most likely maintain use of Siemens PLM products for some time. Aside from the initial software cost, we pay for yearly maintenance. Maintaining our yearly maintenance licensing with Siemens, we receive access to all of the latest software releases, as well as premier technical support
For standard users the interface is friendly. but if you are a manager some tools are a little confusing to use, like the query system that you always need to create from scratch. Templates should be more helpful for queries and for standard procedures that you need to duplicate PBIs over time. The search history of Work Items is a little painful to use.
As previously mentioned, due to the intense amount of features and modules present in the software, the usability of the software suffers greatly. Many of the features are not used in our context, and many of the modules are not purchased, but the options are still present on the interface leading to a lot of clutter, much of which is never used. The interfaces suffer from a lack of design and tend to feel like a conglomerate of Windows 98 elements.
I have not had to use the support for Azure DevOps Server. There have never been any issues where I was not able to figure it out or quickly resolve. Our Scrum Master has used support before though, and the service has always been prompt and clear with a customer-focus
In the time that we have used Teamcenter we have received a good response from the support team, they have great customer service, we have solved the problems that have arisen very quickly, and they are attentive and answer us if we have any questions.
Azure DevOps is a fully integrated solution that solves all of the problems that our separate tools did in a much easier-to-use way. Before we implemented DevOps we had three different solutions that we had to integrate with each other and required a lot of manual intervention to make sure they worked correctly.
Earlier, some of the companies acquired by my organization were using PTC Windchill, but the overall stability, user experience and depth of functionality which are provided by Teamcenter doesn't match with any other PLM software and thus, all the acquired companies which were earlier using PTC Windchill has now slowly started into moving towards Teamcenter.
Teamcenter is easily on the best scalable solution. The single source of product information allows us to collaborate more effectively on the product lifecycle. Also, being a cloud solution, it is pretty straightforward to scale as the maintenance required is quite low . In addition, the overall cost is also easily manageable for businesses like ours.
It has streamlined the pipeline and project management for our agile effort.
It has helped our agile team get organized since that is a new methodology being leveraged within the Enterprise.
The calendar has improved visibility into different OOOs across the project team since we all come from different departments across the larger organization.
We chose Teamcenter because of its cost-effectiveness, and we can say that it has lived up to our expectations because we have been able to save in other more expensive tools to do what we can do in this one. The ROI has been over 40% because we have integrated it across multiple teams and it has allowed us to reduce the amount of errors in our processes and create a more centralized environment.