Jellyfish vs. Pluralsight Flow

I really recommend using Jellyfish; if this is something that your company is looking for, definitely give it a try. The Jellyfish team is also very responsive and supportive while updating, changing, or modifying required data. Having metrics from different tools in one place is very useful, especially when you have several engineering teams.

Incentivized

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

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

GitHub provided a lot of issues for us from an end-user point of view. Overall, Jellyfish is more intuitive; although it does come with its struggles and downfalls, these are something that just takes time to figure out. GitHub was more focused on developing metrics ONLY, and a lot of these metrics were black and white, which resulted in a failure to analyze the bigger picture. GitHub's metrics were mostly unreliable. After using Jellyfish for the past 2ish years, we love it so much better. Despite the learning curve to understand how to use the interface, overall, this provides so much more insights and analytics in a way that allows us to be strategic with our business goals.

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