Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
319 reviews
from
External reviews are not included in the AWS star rating for the product.
Semless integration with our existing tools
What do you like best about the product?
The platform's intuitive dashboards make it easy to track DORA metrics, sprint progress, and team allocation. I particularly appreciate how it integrates seamlessly with our existing tools like Jira and GitHub, providing a single source of truth for engineering data without adding overhead to the development team's workflow.
What do you dislike about the product?
The dashboard navigation could be more intuitive for new users, and sometimes we need support from their team to implement more complex reporting requirements. However, their responsive customer service has helped us overcome these minor challenges.
What problems is the product solving and how is that benefiting you?
The platform helps us identify bottlenecks in our workflow, balance feature development with technical debt, and make informed decisions about team capacity. This visibility has been tremendously beneficial in helping us align engineering efforts with business priorities and demonstrate the impact of our technical investments.
Incredible Tool Providing Actionable Insights
What do you like best about the product?
Jellyfish is easy to use once it is configured for your environment. Set up is easy and straightforward. If you can capture it in Jira, it can be surfaced in Jellyfish. Our primary use case was borad-level insights and reporting. It was trivial to add the necessary metadata to Jira, allowing us to slice-and-dice the data as needed to present different views of resource allocation (e.g., by functional area, business area, etc.) for board presentation. Our seconday use case was Software Cost Capitalization. Again, this was easy to set up and the resultant data was clear, concise, and able to be used directly with our financial reporting.
What do you dislike about the product?
Jellyfish's pricing model is a per-seat model for engineers making contributions to the product. This means that the annual cost increases as the team size grows. Jellyfish maintains that ALL engineers can benefit from logging into the system so, in that case,a per-seat charge might make sense. However, if your use-0case is such that only a handful of users (e.g., CTO, VPEs, Product Leaders) login to Jellyfish, a per-login model might be more palatable.
What problems is the product solving and how is that benefiting you?
Our biggest concerns were with board-level reporting and software cost capirtalization. Jellyfish is completelt meeting that need.
A Clear View of Today, with Data to Guide Tomorrow
What do you like best about the product?
Jellyfish gives me the clarity I need to focus on where I am right now—it provides a current, data-driven snapshot of team performance and delivery metrics. I really value being able to look at what's happening in real time and make informed decisions or adjustments based on those insights. It's not just about tracking; it's about aligning efforts with goals and continuously improving with confidence.
What do you dislike about the product?
The platform is powerful, but the initial onboarding can feel a bit overwhelming due to the depth of features available. It takes a little time to fully understand how to interpret all the metrics and dashboards. However, once you get past the learning curve, it becomes an indispensable part of your workflow.
What problems is the product solving and how is that benefiting you?
Jellyfish is helping solve the challenge of visibility into engineering work and team capacity. Before, it was difficult to get a unified view of how time was being spent or how well we were executing against priorities. With Jellyfish, I can spot trends, rebalance workloads, and make informed, data-backed decisions. It’s enabled better planning, more meaningful conversations with stakeholders, and a stronger focus on outcomes rather than just output.
Actionable Insights Easier In The Right Environment!
What do you like best about the product?
Once all connected and configured, Jellyfish provides easy to use and interpretable insights at every level, across a wide range of metrics & facets of software delivery. We now have reliable metrics that we're using almost daily to drive actions and continuous improvement, we have dedicated support and comms from their team, and they regularly ship new updates and enhancements!
What do you dislike about the product?
Expect a hefty setup phase to integrate your other systems, onboard and categorise users (although JF has tools to accelerate this process), and some tweaks or inclusions to your team workflows to unlock the full feature set of Jellyfish. And just like any other metrics system, it is only as good as the data it's given, so you may need to evolve your workflows and data collected!
What problems is the product solving and how is that benefiting you?
Understanding how we're allocating team and engineering capacity to maximise the creation of value for our customers, and making informed decisions on forward planning using the insights and capacity planning tools!
I love the quick visuals and dashboard to see how our team is doing
What do you like best about the product?
I like how I can quickly see the progress of work, the productivity and the main ideas that were the key themes for a given period of time.
What do you dislike about the product?
Lacking ability to integrate within existing products, but thats an issue with many other similar platforms.
What problems is the product solving and how is that benefiting you?
It gives a quick and deep view into the development work and how it ties to investments. Helps highlight areas that are not contributing to KPI and ability to quickly break them apart.
Jellyfish is evolving, and taking us together
What do you like best about the product?
The metrics are labeled and explained clearly with the info tags -> When adopting new tools, deriving value for the team and seeing the impact will take time, jellyfish is reasonably self-explorable and easy to understand right now
Gives me several options to view metrics, depending on the level of JIRA hygiene.
As a developer myself, the webhook data visibililty on DORA, helps me and my teams understand whats going wrong, nice!
Gives me several options to view metrics, depending on the level of JIRA hygiene.
As a developer myself, the webhook data visibililty on DORA, helps me and my teams understand whats going wrong, nice!
What do you dislike about the product?
As a product that goes through a lot of feature building, we have hit snags with broken UI, data refresh etc in the early stages. Which is being taken care of. On the positive side, the customer support teams have quickly jumped in to help unblock.
What problems is the product solving and how is that benefiting you?
Understand team metrics, individuals involvement with initiatives, plan capacity
Transformed Our Engineering Resource Planning and Cross-Team Collaboration
What do you like best about the product?
Before Jellyfish, we struggled with three key challenges that have now been addressed:
Resource visibility: We now have complete visibility into how engineering time is allocated between roadmap development versus support, and can track investments by business unit down to specific features.
Strategic alignment: We can ensure our engineering investments align with business priorities and make data-backed decisions on where to increase or decrease investments to better serve customers.
Cross-functional communication: Jellyfish has opened meaningful conversations with executives using engineering benchmarks that compare our performance to similar companies in our industry. This shared language ensures everyone is aligned on business priorities.
The ROI has been significant - by analyzing our investments across business units in 2024, we've been able to confidently plan our 2025 budget with clear visibility into which areas need more or less investment.
Resource visibility: We now have complete visibility into how engineering time is allocated between roadmap development versus support, and can track investments by business unit down to specific features.
Strategic alignment: We can ensure our engineering investments align with business priorities and make data-backed decisions on where to increase or decrease investments to better serve customers.
Cross-functional communication: Jellyfish has opened meaningful conversations with executives using engineering benchmarks that compare our performance to similar companies in our industry. This shared language ensures everyone is aligned on business priorities.
The ROI has been significant - by analyzing our investments across business units in 2024, we've been able to confidently plan our 2025 budget with clear visibility into which areas need more or less investment.
What do you dislike about the product?
While Jellyfish has been transformative for our engineering operations, the initial learning curve was steeper than expected. The platform offers so much data and so many features that it took time to determine which metrics were most valuable for our specific business context. For example having a single engineer metrics can lead to cases where one can try and measure engineers on an individual level, for agile teams this is not the way to go.
What problems is the product solving and how is that benefiting you?
The resource allocation feature provides unbiased, evidence-based insights that have replaced instinct-driven decision making. We can now see exactly how teams are spending their time and what value they're delivering across different business units. What I value most is the transparency it brings - engineering is no longer a "black box" to stakeholders outside the team. This data-driven approach has become our source of truth across the organization and strengthened collaboration between engineering, product, and finance teams.
Great metrics, and overview of engineering
What do you like best about the product?
The aggregation of Jira data into one view is the most helpful aspect of Jellyfish. A couple other call outs are the capacity planner, and the weekly review. I use both of those heavily to provide updates to leadership and my team.
What do you dislike about the product?
From an integrations perspective they only integrate with Jira. Then from a business perspective they are quite expensive.
What problems is the product solving and how is that benefiting you?
The main problem that Jellyfish is helping us solve is visibility into our engineering organization from a productivity perspective. It gives us great insight into how we are spending our team, what does our capacity look like for future quarters, and gives us the ability to have more productive conversations internally on how we are doing as an org.
Excellent Tool that Had Immediate Impact Identifying Team Workflow Problems
What do you like best about the product?
Fantastic metrics that shows how time was spent at the team and developer level vs what was planned.
What do you dislike about the product?
It's hard to keep up with all the tooling behind the different menus but the core features I use I can't live without.
What problems is the product solving and how is that benefiting you?
With a product team there is a constant flood of feature work, tech debt, bugs, refactoring work where it's hard to see in the trenches where the time goes Sprint to Sprint. With Juellyfish pulling in Github and JIRA metrics, it identifies where work enters the Sprint that should not have and where prod support tickets or poorly refined work needs an update in our process. Jellyfish dashboards are the core metrics for our team's Retro and Sprint Reviews.
Powerful Insight into Engineering Work with Jellyfish via Emburse
What do you like best about the product?
We've been using Jellyfish through Emburse over a year, and it has become an incredibly valuable tool for our team. It provides clear visibility into the progress of epics, tracks developer activity, and offers comprehensive insights into our engineering operations.
What makes Jellyfish especially useful is its ability to align engineering work with business priorities. We can easily monitor how time is spent across projects and identify where efforts are being focused. The integration with our existing systems was smooth, and the interface is intuitive and informative .
Thanks to Jellyfish, we now have greater confidence in our delivery pipeline and can make data-driven decisions more effectively. It's an essential part of our toolkit for tracking performance and progress across development teams.
Highly recommended for any team looking to improve transparency, accountability, and strategic planning within their engineering organization.
What makes Jellyfish especially useful is its ability to align engineering work with business priorities. We can easily monitor how time is spent across projects and identify where efforts are being focused. The integration with our existing systems was smooth, and the interface is intuitive and informative .
Thanks to Jellyfish, we now have greater confidence in our delivery pipeline and can make data-driven decisions more effectively. It's an essential part of our toolkit for tracking performance and progress across development teams.
Highly recommended for any team looking to improve transparency, accountability, and strategic planning within their engineering organization.
What do you dislike about the product?
We haven't encountered anything we dislike about Jellyfish so far. The platform has been reliable, intuitive, and consistently valuable in helping us track and manage our engineering work. It integrates well with our existing tools and meets our needs effectively.
What problems is the product solving and how is that benefiting you?
Jellyfish helps us solve the challenge of visibility and alignment across our enginering teams. By tracking progress on epics, developer contributions, and overall workload distribution, it ensures that our efforts are focused on the right priorities. This has improved our ability to plan, allocate resources efficiently, and make informed decisions backed by real-time data. The result is better collaboration, clearer reporting, and stronger alignment between engineering work and business goals.
showing 41 - 50