Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
384 reviews
from
External reviews are not included in the AWS star rating for the product.
Using Jellyfish as an Engineering Manager
What do you like best about the product?
I like the overall UX when using it, I like features like issue resolving cycle and deliverables. It’s been incredibly helpful for me!
What do you dislike about the product?
Nothing comes to my mind. Maybe I’d love to see more tooltips explaining how the data was collected?
What problems is the product solving and how is that benefiting you?
Planning work for the team, updating stakeholders with feature statuses and observing performance in the team for good discussions afterwards.
JellyFish review by admi user and data analyst
What do you like best about the product?
I appreciate the platform for the way it allows me to interact. I also enjoy the level of detail in the data that is available. I also enjoy the quality of the support service
What do you dislike about the product?
What I don’t really like is that there’s too much data and too many metrics that might not fit my company. What I’d like is the ability to create metrics based on the data that’s available — maybe something like a metrics builde
What problems is the product solving and how is that benefiting you?
Well, Jellyfish mainly helps us measure development times and the progress of each type of work. It’s most useful for verifying the work of each developer when we have doubts or want to review what they did.
In summary, we focus more on team velocities, and whenever we have doubts, we check what each developer or each team has done
In summary, we focus more on team velocities, and whenever we have doubts, we check what each developer or each team has done
Jellyfish understands how tech companies work
What do you like best about the product?
The jellyfish software suite is able to put together connections between your work items in Jira and the actual work committed to your repositories. It meshes the data between these two worlds in a way that could previously only be done by custom scripts and Excel sheets. This saves us time and gives us out-of-the-box business intelligence about where we are investing resources. In turn, this allows us to compare our espoused business strategy to our actual resource allocation.
At it's core, Jellyfish lets us see if we're putting our money where our mouth is.
At it's core, Jellyfish lets us see if we're putting our money where our mouth is.
What do you dislike about the product?
Getting everything set up does require a lot of investment. But, the more you put into the software, the more it gives back. But, if there was a magic button to get all your developers and theirs salaries into the system, that would be great.
It also requires engineers to properly connect their commits in GitHub to the Jira ticket that spawned the work. There are many cases where that doesn't happen or where there simply isn't a ticket. I understand that this is a process hygiene problem, but it's still a point of failure in the way Jellyfish collects data.
I appreciate that the JF staff is up front about both of the above friction points.
It also requires engineers to properly connect their commits in GitHub to the Jira ticket that spawned the work. There are many cases where that doesn't happen or where there simply isn't a ticket. I understand that this is a process hygiene problem, but it's still a point of failure in the way Jellyfish collects data.
I appreciate that the JF staff is up front about both of the above friction points.
What problems is the product solving and how is that benefiting you?
Our C-Suite and Board need to know what we are working on at the strategic initiative level. Our teams know what they are working on at a more granular level. Translating that granular, ticket-and-epic-based information into data digestible by our leadership in the way that they need the data was a tedious, manual process that was subject to drift depending on who was preparing it. Jellyfish solves this problem with built-in quantitative displays that we can customize to our business imperatives.
It's not just a tool, it's insight.
What do you like best about the product?
First, it's an easy and relatively intuitive tool to get acquainted with. I feel like a kid in a candy store exploring the different lenses through which I can view our work. It has made me very curious about the way in which we do work. As we become stronger with Jellyfish, we're able to ask better questions and experiment with our options, and we're able to see what comes of it very quickly! Second, the support has been outstanding. Andrey has been utterly patient as I pepper him with questions, and has consistently guided me to the answers I need. Third, Jellyfish University has been very helpful, especially the lessons that help with diagnostics. It's an excellent, effective resource and makes me feel like the Jellyfish team is invested in our success (which is very refreshing)!
What do you dislike about the product?
First, dislike is too strong a word. There's nothing I dislike - at least not yet!
The learning curve is real but again, the tool is intuitive and once you get a toe hold in even one aspect, additional understanding comes quickly if you put in the effort. (Isn't that just the nature of operations, though?) I'd also like to see roll-up reports to the executive level, and I'd like additional, diagnostics-oriented JF University training. For teams that have no history in observing how they work, it's a real necessity to help them understand that this is intended to be used by them (or their leaders, anyway) as an aid, and as a way to align, and yes, protect, their team. Our greatest challenge hasn't been learning the tool, but gaining traction internally. I would also like a report that shows who's logged in and who hasn't. Maybe that exists at the administrator level, but I suspect some of those complaining the loudest haven't spent much time in it.
I would also REALLY like to see more robust planning options to give teams better long-term insight into how realistic their plans are, especially with regard to pulling in dependencies.
The learning curve is real but again, the tool is intuitive and once you get a toe hold in even one aspect, additional understanding comes quickly if you put in the effort. (Isn't that just the nature of operations, though?) I'd also like to see roll-up reports to the executive level, and I'd like additional, diagnostics-oriented JF University training. For teams that have no history in observing how they work, it's a real necessity to help them understand that this is intended to be used by them (or their leaders, anyway) as an aid, and as a way to align, and yes, protect, their team. Our greatest challenge hasn't been learning the tool, but gaining traction internally. I would also like a report that shows who's logged in and who hasn't. Maybe that exists at the administrator level, but I suspect some of those complaining the loudest haven't spent much time in it.
I would also REALLY like to see more robust planning options to give teams better long-term insight into how realistic their plans are, especially with regard to pulling in dependencies.
What problems is the product solving and how is that benefiting you?
The primary issue it's helping us solve, or at least shed light on, is how much work we do that doesn't pertain to our stated priorities. We're still straightening out some of our data issues - JF has highlighted anomalies we hadn't know about - and seeing, for example, the lifecycle report or CapX reports has swung us around. It's also highlighting how misaligned certain groups are, whether internally or across teams. For example, we've uncovered some significant misalignment with leaders that we might not have realized without the data from JF.
Great insights into engineering maturity
What do you like best about the product?
The most helpful feature in Jellyfish is the ability to measure allocations across multiple areas such as investment themes, initiatives/epics, and releases.
What do you dislike about the product?
In the future I would like to see more self service capabilities when configuring new teams and adjusting existing teams.
What problems is the product solving and how is that benefiting you?
Understanding engineering team maturity, measuring investment allocations, and guiding managers on areas of improvement.
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.
showing 41 - 50