Azure DevOps Server vs. Jellyfish

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.

Incentivized

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.

Incentivized

• Reporting Integration- Azure boards provides Kanban and other dashboard, their templates for easy management of project.
• Project Pipeline- easy integration and development of CI/CD pipelines, helped in testing, releasing project artifacts.
• Version Control- Integration with Git and code IDE made it easy to share, review our code, fix bugs and do testing.

Incentivized

• Integration with JIRA.
• Integration with GitHub.
• Friendly UI.
• Easy to read.

Incentivized

• Can add more build templates for specific technology requirements
• Can have more features in dashboards which can help dev teams stream line their tasks and priorities
• Can have raise alarm feature in case of any sort of failure in devops pipeline execution

Incentivized

• 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.

Incentivized

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.

Incentivized

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.

Incentivized

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

Incentivized

Do research beforehand and, if possible, do a trial run before implementing into production environment.

Incentivized

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!

Incentivized

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.

Incentivized

• 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.

Incentivized

• Easy setup and takes time to learn, but overall easy to use one you get the hang of it.
• Strategic roadmapping.
• Return on Investment increased.

Incentivized