Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
389 reviews
from
External reviews are not included in the AWS star rating for the product.
Jellyfish for Managing Software Dev Teams & Performance
What do you like best about the product?
Jellyfish provides a decent dashboard to view metrics for development and team performance including commits, code additions, PR cycle times and Jira ticket cycle times. Good ability to compare metrics across teams and individuals.
What do you dislike about the product?
(1) Not enough proactive insights or alerting. Jellyfish metrics are great but the real value is in identifying outliers, deviations or under-performers. Currently I need to do this myself and manually by analyzing data across various different teams, people and time periods, and making inferences about whether a metric is good or bad. And this isn't easy or obvious.
What I'd really want is for Jellyfish to alert me for potential issues like:
- underperforming individual or team
- sharp changes/deviations in an individual or team's performance
- concerns about a team process (cycle time, etc.)
This would allow me to look deeper into those areas and take action to address or improve the problems.
Jellyfish already has metrics and benchmarks for both our organization, as well as the broader development industry, so Jellyfish is in the best position to provide this analysis. For now Jellyfish is just a fine tool for analyzing metrics manually. But what would make it an INDISPENSABLE and CRITICAL resource if it could handle that analysis by itself using AI to analyze the data and team/individual performance across various time periods and suggest how my developers are performing both within our organization, and as compared to general benchmarks.
What I'd really want is for Jellyfish to alert me for potential issues like:
- underperforming individual or team
- sharp changes/deviations in an individual or team's performance
- concerns about a team process (cycle time, etc.)
This would allow me to look deeper into those areas and take action to address or improve the problems.
Jellyfish already has metrics and benchmarks for both our organization, as well as the broader development industry, so Jellyfish is in the best position to provide this analysis. For now Jellyfish is just a fine tool for analyzing metrics manually. But what would make it an INDISPENSABLE and CRITICAL resource if it could handle that analysis by itself using AI to analyze the data and team/individual performance across various time periods and suggest how my developers are performing both within our organization, and as compared to general benchmarks.
What problems is the product solving and how is that benefiting you?
The main things I'm using Jellyfish for is to identify problems around team performance and productivity. I'm personally less concerned about investment areas as I trust and work closely with my product team and engineering leads as far as our roadmap.
I'm concerned with:
- Identifying team members who are not contributing at an expected rate and who might be negatively affecting their teams.
- Identifying teams who are not executing a good agile process. Teams who might have very long cycle times implying they are not structuring their work in an agile way.
- Identifying teams who are impacted by frequent blockers.
I'm concerned with:
- Identifying team members who are not contributing at an expected rate and who might be negatively affecting their teams.
- Identifying teams who are not executing a good agile process. Teams who might have very long cycle times implying they are not structuring their work in an agile way.
- Identifying teams who are impacted by frequent blockers.
Great insights on investment allocation and high-level analysis
What do you like best about the product?
I love the UI and how clearly the information is displayed. It’s easy to filter by teams, divisions, and the company view. The ability to select specific metrics for the team homepage and the investment allocation chart are great. We’ve been using these metrics heavily, especially cycle time, investment allocation, and throughput. Jellyfish has been very useful for driving relevant company decisions. I also value seeing where Epics stand, how many are in progress, and the associated risks and projections. The customer support is outstanding, always available directly on Slack, and the recurring meetings help ensure alignment and maximize our use of the tool.
What do you dislike about the product?
I miss having percentile data in the charts instead of only median and average. I’d like the ability to create custom metrics from raw data and access more Kanban metrics (e.g., cycle time breakdown, aging chart, CFD, Monte Carlo simulations). The lifetime explorer is limited since it only displays items with PRs, which isn’t relevant for us, we want visibility into the full work type of a team.
My strongest criticism is that Jellyfish is too focused on individuals, which can drive misleading analysis by managers. For example, capacity simulations often reduce to “just add people to a project,” which doesn’t reflect the reality of software development. I’d prefer to see the emphasis on team-level effort and delivery capacity, rather than individual metrics like cycle time per person.
My strongest criticism is that Jellyfish is too focused on individuals, which can drive misleading analysis by managers. For example, capacity simulations often reduce to “just add people to a project,” which doesn’t reflect the reality of software development. I’d prefer to see the emphasis on team-level effort and delivery capacity, rather than individual metrics like cycle time per person.
What problems is the product solving and how is that benefiting you?
JellyFish provides clear visibility into how the team is performing, both in terms of responsiveness (pace) and focus (investment allocation), which is very hard using only Jira.
Jellyfish is able to extract valuable insights into the team velocity
What do you like best about the product?
It is great to see an overview of the impact I'm having across projects. It helps project velocity for other projects and keep check on consistency. The UI is quite clear and easy to use to review relevant stats. I like that it integrates seamlessly with Jira which we use as our project management tool. While the data is valuable, I'm not frequently checking the dashboard as it does not affect my day-to-day work, but it definitely helps plan for new projects and recap our velocity of past projects.
What do you dislike about the product?
One stat that I find confusing/counter productive is the notion that all work (git commits) should be able to be attributed to a work item (jira ticket). I understand that this is needed from a reporting perspective, but in the real world it it often creates significant overhead for small changes to require creating a jira ticket just to "track the work". It would be awesome if somehow work without a jira ticket could be associated to a project by looking at the context/content of the work.
What problems is the product solving and how is that benefiting you?
It gives me relevant insights in the team velocity on the current project
Must-have engineering intelligence platform
What do you like best about the product?
It's an invaluable tool for engineering leaders seeking to understand the environment in which their teams work. It enables tracking of trends across various investment types, such as Growth, Support, and Technical, while also providing analysis of SDLC bottlenecks and overall efficiency metrics. This helps leaders determine the right moments and areas for intervention.
What do you dislike about the product?
There’s nothing I dislike about it. I do think there are a few additional features that could be added to save time, but overall, it’s a comprehensive and useful tool when used for the right purposes.
What problems is the product solving and how is that benefiting you?
Understand and visualise with data my teams pressure points and bottlenecks. Visualising trends across quarters
Clear visibility into engineering work and priorities
What do you like best about the product?
I really like being able to check team metrics such as velocity and cycle time, which helps me identify trends early and adapt quickly. Jellyfish gives our team a clear, data-driven view of engineering investments and progress. It makes it much easier to align engineering work with company priorities and to communicate impact with leadership. I also appreciate the intuitive dashboards, which make complex development analytics easy to understand, and the Jira integration that saves time on manual reporting.
What do you dislike about the product?
While Jellyfish is powerful, there can be a learning curve at the beginning, especially when setting up integrations and customizing views. Some of the reports could offer more flexibility in filtering or drilling down into details. That said, the support team is responsive and actively improves the product based on feedback.
What problems is the product solving and how is that benefiting you?
Jellyfish is helping us track and analyze engineering team performance in real time. By monitoring metrics such as velocity, cycle time, and work distribution, I'm able to identify trends early, detect potential bottlenecks, and adapt quickly. This visibility ensures that engineering work stays aligned with business priorities and makes it easier to communicate impact to leadership. The tool reduces the need for manual reporting and provides a single source of truth for data-driven decisions.
Easy to use tool, offers great insight into how the organization and each team is performing
What do you like best about the product?
Love the visibility the tool provides and how easy it is to use!!! We are able to look at each team more objectively. Each team has the same metrics, with some variance based on the way the teams work (scum, scrumban, kanban, etc) . I love that the tool keeps improving at a pretty rapid pace, and they are so welcoming of ideas and feedback to make Jellyfish even better! The support team is super helpful, and communicates well as they work to resolve issues.
What do you dislike about the product?
Sometimes the teams don't like the visibility.... Also, managers have a lot on their plate and may not be leveraging the tool as effectively as they can so I wonder if we are getting as much value as we could be (but that is on us, not JF).
What problems is the product solving and how is that benefiting you?
helping teams with accountability. We have great baseline data so when teams want to change up how they work, they have lots of flexibility as long as they are improving metrics and not going backward. Also, giving us insight into how well our AI tools are working for us (or not), giving us better insight to make decisions.
When we aren't actively looking at Jellyfish data sometimes the teams aren't as diligent about delivering upon their commitments. Jellyfish has helped us to improve our predictability with the level of visibility/transparency
When we aren't actively looking at Jellyfish data sometimes the teams aren't as diligent about delivering upon their commitments. Jellyfish has helped us to improve our predictability with the level of visibility/transparency
Jellyfish enhances strategic decision-making with insightful engineering metrics.
What do you like best about the product?
What I like about Jellyfish is how its engineering metrics surface trends that help us spot issues and opportunities early. It enables more targeted conversations that drive real improvements in operational outcomes. The new DevEx features are especially valuable—they highlight areas of stress or overload, which helps us boost both productivity and developer well-being.
What do you dislike about the product?
What I dislike about Jellyfish has mostly been around user administration. Progress has been made to address those concerns, though some work still remains.
What problems is the product solving and how is that benefiting you?
Jellyfish helps solve the problem of visibility into engineering work. It surfaces trends and metrics that make it easier to identify bottlenecks, stress points, or misalignment early. This benefits me by enabling more targeted conversations with teams, improving operational outcomes, and supporting both productivity and developer well-being.
Versatile tool for both engineering and strategy product planning
What do you like best about the product?
Jellyfish has become an essential part of my workflow not only to understand engingeering operations but also as help to shaping early product strategy. Its core lies in surfacing engineering metrics but I found immense value using it to estimate new product concepts and MVP efforts as well.
We can set more realistic expectations and improve cross-functional alignment early in concept phase.
The interface is easy to use and various academy courses are helpful if you just starting to use it.
As we work in a product portfolio (over 12 products) the tool helps to bridge the gap between product and engineering in a data-driven, actionable way and allow us to validate whether teams cant take on MVPs without disrupting core roadmap items.
We can set more realistic expectations and improve cross-functional alignment early in concept phase.
The interface is easy to use and various academy courses are helpful if you just starting to use it.
As we work in a product portfolio (over 12 products) the tool helps to bridge the gap between product and engineering in a data-driven, actionable way and allow us to validate whether teams cant take on MVPs without disrupting core roadmap items.
What do you dislike about the product?
Occsionally some learning curve in advanced custom views, but nothing much
What problems is the product solving and how is that benefiting you?
- helping to anwser critical questions about visibility gap: can we deliver this MVP without derailing core roadmap items, are we investigating in the right areas
-for me specifically early-stage estiamtion and scopting of new product concept using real data on past initatives and current capacity
- accurate MVP planning, stronger alignment and in general less friction between teams and leadership
- apart from this of course resource allocation, reducing delivery risk and overall driving better product outcomes
-for me specifically early-stage estiamtion and scopting of new product concept using real data on past initatives and current capacity
- accurate MVP planning, stronger alignment and in general less friction between teams and leadership
- apart from this of course resource allocation, reducing delivery risk and overall driving better product outcomes
Very useful to track several engineering metrics and performance
What do you like best about the product?
It's easy to see metrics for the whole team but also individual.
What do you dislike about the product?
Sometimes the UI gets confusing to find the right information.
What problems is the product solving and how is that benefiting you?
Visibility on DORA metrics, and how engineers are working in general (PR merge time, etc)
Great functionality with simple yet powerful design
What do you like best about the product?
There is a good selection of various metrics and dashboards, which helps me identify areas where our work can be improved. The platform offers great functionalities within a fairly intuitive interface.
What do you dislike about the product?
It's difficult to say for sure, but I think improved integration with Intellij Junie, if that's possible, would be a great addition.
What problems is the product solving and how is that benefiting you?
It is helping me in unblocking my team members in their daily challenges but also helps me to find places where we are stuck or what is our bottleneck which we should analyse during Retros.
showing 51 - 60