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 Review
What do you like best about the product?
I like the ability to see what has impacted a sprint and when one of my developers might have struggled to complete work during a spting.
What do you dislike about the product?
I wish data updated real time for thing like sprint metrics, and open pull requests
What problems is the product solving and how is that benefiting you?
We use jellyfish to analyze project health, sprint velocity, and performance of our engineering team
Best in business tool for engineering managers
What do you like best about the product?
The integration with Jira and our git repositories is seamless, bringing together and highlighting all the key data we need. The DevEx module, along with the ability to survey teams with extensive customization, has been particularly valuable. Slack alerts and team pulse features help keep everyone informed—even those without a Jellyfish login—by surfacing any tickets that are stuck. The daily digests provide insights into what is slowing the team down, enabling us to investigate issues and improve our processes. Allocation metrics reveal how much time is spent on bugs or specific components, which helps guide prioritization discussions and supports more accurate estimates. Additionally, the individual metrics and interaction data are useful for facilitating performance discussions with engineers.
What do you dislike about the product?
The permissioning and data privacy settings in Jellyfish are too rigid, making it difficult for my boss to grant granular access to non-managers. For instance, we are unable to provide our tech lead with a team-specific view without also exposing individual performance data for everyone, which is not ideal.
What problems is the product solving and how is that benefiting you?
Performance management, team prioritization and planning, identifying blockers and slow-downs.
Great tool for team tracking
What do you like best about the product?
I appreciate its team pulse feature, which helps in reviewing stuck pull requests and tickets.
What do you dislike about the product?
Jellyfish lacks integration with the Outlook calendar.
What problems is the product solving and how is that benefiting you?
I use this to track my time, which makes it easier for me to generate reports when needed. It helps in tracking bug to feature ratio to analyze where the issue lies, either with requirements or implementation.
infra work in jellyfish needs some work
What do you like best about the product?
I like the general overview that is given across the various jira projects. It allows me to dig into who might be overcommited and on what they are stuck working on.
What do you dislike about the product?
Since I manage multiple jira projects it would be nice to combine them into a singular overview.
Since one project is also jira service desk it would be helpful to have some ability to map tags to investments. otherwise it appears that service desk work doesn’t really map to anything.
Since one project is also jira service desk it would be helpful to have some ability to map tags to investments. otherwise it appears that service desk work doesn’t really map to anything.
What problems is the product solving and how is that benefiting you?
the ability to quickly and easily see team level metrics and then view how those metrics were contributed to by various team members.
Great product for engineering teams
What do you like best about the product?
It's simple to monitor the progress of features and develop a capacity plan.
What do you dislike about the product?
At times, the projections can be inaccurate by a significant margin.
What problems is the product solving and how is that benefiting you?
Capacity planning and understanding where the team is allocating most of their time are important aspects to consider.
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.
showing 41 - 50