Jellyfish vs. Typo

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

My experience while using Typo has been smooth so far so nothing to dislike. I would appreciate more customizations on how to track Github activities.

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

Incentivized

• Code Analysis
• Developer productivity
• Developer experience

• 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

It is one of the most effective tools I have used for my team.

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

Quality UI & instant support. Also the pricing is relatively very cost affective for us.

• 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

• Increase in productivity