Azure DevOps Server (formerly Team Foundation Server, or TFS) is the on-premise version of Azure DevOps. 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
BMC AMI DevX
Score 9.3 out of 10
N/A
BMC AMI DevX is an integrated software platform that provides mainframe development teams with modern Application Development and DevOps capabilities. The solution connects traditional mainframe environments with contemporary development practices through components for source code management, testing, debugging, and analytics.
N/A
Jellyfish
Score 8.4 out of 10
N/A
Jellyfish is an Engineering Management Platform that enables engineering leaders to align engineering work with strategic business objectives. By analyzing engineering signals and contextual business data, Jellyfish provides complete visibility into engineering organizations, the work they do, and how they operate. Jellyfish Co, headquartered in Boston, states companies like SessionM (A Mastercard Company), Medium, and Toast use Jellyfish to optimize the allocation of engineering resources to…
Azure DevOps is good to use if you are all-in on the Microsoft Azure stack. It's fully integrated across Azure so it is a point-and-click for most of what you will need to achieve. If you are new to Azure make sure you get some outside experience to help you otherwise it is very easy to overcomplicate things and go down the wrong track, or for you to manually create things that come out of the box.
I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.
Jellyfish allows us to understand the allocation of our efforts without time tracking. We are also able to integrate this platform with our existing ticket tracking system and can see analytics instantly! Jellyfish works well for our teams because it has an opinionated view. Jellyfish understands that the metrics for an engineering team should help you understand what your organization values and is actively working on. We can use Jellyfish in a strategic way compared to other tools like this.
The tool I use is fairly intuitive. It doesn't take long to be using it full time.
Changing the layout/view is fairly easy. This allows it to fit individual preferences.
It is helpful to be able to view specific windows in full screen. Usually, I have it set up to view multiple windows, but sometimes, I just want to view one window in full-screen mode.
UI and navigation aren't very intuitive and require additional research before being able to use.
The individual developer metrics are not very useful and make the interface feel cluttered.
Overall, it takes time for the end-user to truly learn how to use the platform and navigate. There is so much information/data available that although the above is a con, we felt it still made sense, despite the learning curve.
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.
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.
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
Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.
The installation teams for these products have never complained about any difficulties during the integration of this range of tools into our IT system.
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. The productivity increase we realized with DevOps is worth real money!
The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.
The really cool thing about Jellyfish is the integrations that it has with the other tools, which are also very common within the software development industry. Consolidating all this data and being able to see graphs, numbers, and percentages in one place gives you a better way to analyze and define better solutions to improve your software development processes.
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.
Possitive impact. It is main product suite to enable devops in the mainframe applications team. All developers use these on day-to-day work.
Negative impact: Recent usability issues caused disappointment in the application teams. It became hard motivate the development community to increase usage.