Jellyfish Reviews

Jellyfish gives us real visibility into engineering work and Q&A bottlenecks that Jira alone could never provide. We are about 45 engineers, including 10 QA test engineers. Our primary use case for Jellyfish is mainly to get end-to-end visibility into our SDLC. Before Jellyfish, we had Jira burndown charts. We had no idea how much time was going into new features versus bug fixes, versus keeping the lights on. Now Jellyfish connects to our Jira, GitHub, Jenkins, and Slack.

One positive impact Jellyfish has had on my organization is that it reduced unplanned work. We found that 30% of our QA time was going into production hotfix testing, which was not planned. With Jellyfish data, we created a dedicated buffer for unplanned work in sprint planning. Unplanned work dropped to 12% in three months. It has improved developer-QA collaboration and led to better sprint estimation. We started comparing estimated versus actual allocation. Now our sprint predictions are 85% accurate versus 50% earlier. There are no more last-minute release postmortems. It also helped identify bottlenecks in QA where Jellyfish showed that tickets were stuck in 'Ready for QA' status for an average of 1.8 days due to environment unavailability. We then containerized our test environment with Docker and Jenkins, cutting wait time to four hours.

The best features Jellyfish offers are Allocation and Investment View, seamless integrations, DevEX and delivery metrics, Team Health and Work Profile, Executive Reports, and justified test automation investments, improved developer and QA collaboration, and better sprint estimation.

The Allocation and Investment View stands out for me as a killer feature. It shows us exactly where engineering time is invested, such as roadmaps, bugs, infrastructure, and KTLO. This helped us balance feature work and quality work. When it comes to Executive Reports, they provide very clean dashboards that even non-technical managers can understand. There is no need to explain Jira queries anymore.

I would also say the seamless integrations are impressive. The Jira plus GitHub plus Jenkins integration took less than 30 minutes. It automatically maps commits to Jira tickets, so no manual tagging is needed.

One positive impact Jellyfish has had on my organization is that it reduced unplanned work. We found that 30% of our QA time was going into production hotfix testing, which was not planned. With Jellyfish data, we created a dedicated buffer for unplanned work in sprint planning. Unplanned work dropped to 12% in three months. It has also improved developer-QA collaboration and led to better sprint estimation. We started comparing estimated versus actual allocation. Now our sprint predictions are 85% accurate versus 50% earlier. There are no more last-minute release postmortems. It also helped identify bottlenecks in QA where Jellyfish showed that tickets were stuck in 'Ready for QA' status for an average of 1.8 days due to environment unavailability. We then containerized our test environment with Docker and Jenkins, cutting wait time to four hours.

A few areas for improvement are that the initial onboarding period needs patience. The first two to three weeks, the data looks inaccurate until it learns your Jira workflow and Git patterns. The documentation for investment categories is confusing. Additionally, the interface can be slow when you filter data for six or more months.

I would also say the pricing is on the higher side, especially for smaller teams working under a tight budget. This means it may not be suitable for startups below 20 engineers. Jellyfish should improve the mobile dashboard view as well.

I have been using Jellyfish for the past nine years, even in my previous organization.

Our stability experience with Jellyfish over the last five years has been excellent. I would rate it a nine out of ten. It is a very stable SaaS platform. We have not seen a single major outage where the platform was completely down. In about three years, I remember only two times when dashboards were slow to load for about 15 to 20 minutes, and their status page showed they were doing database maintenance. They have a status page at status.jellyfish.co, and they are very transparent.

Scalability experience with Jellyfish has been very positive. We started with 35 engineers in our department, and now we are over 50 engineers, going to 60 next quarter, and Jellyfish handled the scale without any issues.

I have had to reach out to them a couple of times, and my experience with them was great. They are quick to respond to any of our questions or disasters, and they are also solution-oriented and very professional.

We still use Jira. We did not switch from it. We switched from only Jira reporting to Jellyfish plus Jira combined.

The deployment of Jellyfish in our environment is very easy and straightforward. It is a SaaS platform, so there is no heavy infrastructure to manage from our side. We did not need to provision any servers or databases.

The configuration process experience with Jellyfish was smooth, guided, and well-supported. It is not a plug-and-play tool where you just connect and forget. You do need to configure it properly to get real value, but the Jellyfish team makes it very easy.

Before Jellyfish, we saved $15,000 per year in reporting time. Because before Jellyfish, our engineering manager, QA lead, and I spent 10 to 12 hours per week manually creating reports from Jira, GitHub, and Jenkins in Excel. Now Jellyfish automates all of it. This is approximately 40 hours per month saved across the team. If we calculate at $40 per hour engineer cost, that is around $19,200 per year saved just in reporting. We have also seen faster release cycles with a 30% improvement, a reduction in unplanned work, enhanced QA efficiency and cost savings, better resource planning, and a 40% reduction in bug leakage into production.

The deployment frequency has increased by 30%. Lead time for changes, especially commit to production, reduced by 42%. Cycle time in progress to done reduced by 28%.

Jellyfish pricing is based mainly on the number of engineering or contributors whose data is being tracked, not per viewer. If you have 45 engineers committing code, you pay for 45 contributors, but you can have unlimited managers or viewers for free. This was good for us because we had 10 managers who needed view access but do not code. The price or the plan depends on your number of engineers.

Jellyfish is a premium price tool, not a cheap tool, but for us, the return on investment justified the cost.

My advice to others evaluating Jellyfish, as a software test engineer who has used Jellyfish for about nine years and was part of the evaluation team, is to not evaluate with fake data users. Use your real Jira and Git data. Spend time on investment model configuration. Do not try to replace Jira.

If you are 20 or more engineers and tired of Jira plus Excel reporting, Jellyfish is worth every dollar. It changed how we manage engineering from gut feel to data-driven within a period of three to four months, which was a great thing. I would rate this product an eight out of ten.

My main use case for Jellyfish is that it has helped us save several hours of work each month for leaders. It incorporates detailed metrics that give us an idea about how the scrums can be improved and boost team performance.

A specific example of how Jellyfish helped my team save hours or improve scrums is that it gives us a holistic picture of data collected from various systems, regardless of the tech stack teams use. It is superior to other vendor products available in terms of customization, offering organization when necessary.

Jellyfish can collect data from various development teams and provide analysis without intervention.

Jellyfish has positively impacted our organization as it helps us grow our team efficiency at work. The documentation is excellent to start working with the product.

It helped my team grow efficiency through its easy setup, which takes time to learn, but is overall easy to use once you get the hang of it.

In my opinion, the best features Jellyfish offers are data collection, its lightweight nature, and the wonderful Jellyfish team.

When I mention data collection, Jellyfish stands out in that it can collect data from various development teams and provide analysis without intervention, helping us to make data-driven decisions easily. It is very lightweight, easy to configure, and provides accurate intelligent predictions. The Jellyfish team is wonderful, knowledgeable, and practical in resolving our queries on time.

Jellyfish provides a very excellent and intuitive user interface that helps to understand where time is being spent across our organization and is integratable with other platforms and software we use daily.

To improve Jellyfish, I suggest adding the view on the return on investment, making it easy to identify waste within our processes. It is a great way to see engineering overall results and measure.

Sometimes understanding the metrics is not simple. I also believe they should keep improving the user interface.

The individual developer metrics are not very useful and make the interface feel cluttered, which is an improvement that Jellyfish needs.

I have been using Jellyfish for five years.

Jellyfish is stable and has been reliable for our organization.

Jellyfish's scalability is good, as it handles our growth effectively.

The customer support is very responsive and proactive, and I have had good experiences with their support team.

I previously used Jira software, GitHub, and GitHub.

My experience with pricing, setup cost, and licensing is that everything was excellent, straightforward, and the cost is very cost-effective compared to other alternatives.

I have seen a return on investment as it is easy to set up and a great tool. It is a great tool because it is easy to identify waste within our process.

Before choosing Jellyfish, I evaluated other options such as Miro.

My advice to others looking into using Jellyfish is that I really recommend using it. If this is something 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. I would rate this product a 9 overall.