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.
Excellent tool for monitoring Engineering Productivity
What do you like best about the product?
It brings together data from our ticketing management system and our code repository to show productivity metrics per developer, team and sprint. This is invaluable in identifying areas of improvement and enabling fruitful discussions between development managers and the developers. This also helps us in our discussions with vendors who can then align skillset to our technology and needs around velocity.
What do you dislike about the product?
It can appear expensive at first, however we were extended a long trial period and support that helped justify the costs.
What problems is the product solving and how is that benefiting you?
Planning of sprints and releases and allocation towards initiatives.
Ease of Use
What do you like best about the product?
It's easy to use for most parts. The AI impact should make our use of GitHub Copilot simpler. Understanding other teams' velocity isn't straightforward, but it's not difficult to locate the information. We also received training on how to interpret these metrics.
What do you dislike about the product?
The interface is a bit complex, and without training, we aren’t aware of features like team activities, Jira, and PR measures. The team also has many questions about how these are calculated.
What problems is the product solving and how is that benefiting you?
The company uses this tool to track team velocity and AI activities. We are in the process of learning how to use it. It's important for us to have a shared understanding when we communicate.
Great for tracking personal engineering impact!
What do you like best about the product?
Absolutely the best functionality is the ability to drill down into my stats for a given time slice. The granularity in which I can how I performed for a given week is astonishing. Love the different metrics and how they tie back to my work for the week.
What do you dislike about the product?
I wish the was the ability to have custom groups of individuals favorited. It does not appear easy to select all the SR staff engs and then compare their metrics at once. I'd love to be able to do this so I can see where I stack up against the group.
What problems is the product solving and how is that benefiting you?
Jellyfish allows for me to have great insight into the ACTUAL work I did in a given week. It allows me to tie back that work to true impact on the engineering org. It also helps to provide metrics when I am going to bat for an engineer or for myself.
Jellyfish takes the obscure and makes it visible
What do you like best about the product?
I love that there are easy to use dashboards taking information that is also already available in different systems like Jira, and Bitbucket - and makes it easy to be able to grok what is going on from a numbers standpoint. It also helps hold all the teams across the company accountable to have good Jira hygiene to ensure the reporting is as expected. Its pretty easy to add new teams, and begin consuming data. You can absoultey get the same results going directly to each application, however this makes it easy and visible without having to search for the data and where it lives in a consistent way.
I tend to use it on the daily to check in on the heartbeat of the team, see how engaged my developers are, and who deserves recognition for going above and beyond even if its not in a forum that is easily visible to me (code reviews, meetings, etc.).
I tend to use it on the daily to check in on the heartbeat of the team, see how engaged my developers are, and who deserves recognition for going above and beyond even if its not in a forum that is easily visible to me (code reviews, meetings, etc.).
What do you dislike about the product?
Due to the nature of the refresh happening on a rolling 24 hours, I wish it would reflect changes a bit quicker.
What problems is the product solving and how is that benefiting you?
Today, when we are asked on what kind of capacity we have today, tomorrow, and a month from now - much of that is done manually in excel spreadsheets, smartsheets, or other PM tools that are familiar with our Program Managers. The data is readily available in Jira, however finding it can sometimes require a more power user approach, and each user can customize it so it makes measuring across the Enterprise org difficult. Jellyfish makes that easy, and enables quick adoption by new users - providing a consistent way to measure and share capacity when doing thigns like Quarterly Planning.
Because its a known tool by PMs its also useful when asked to 'prove' the numbers behind our estimates when doing Quarterly Planning exercises.
Because its a known tool by PMs its also useful when asked to 'prove' the numbers behind our estimates when doing Quarterly Planning exercises.
Jellyfish is good platform for data-driven engineering/business decision making
What do you like best about the product?
end to end tracking particular project/epic
What do you dislike about the product?
it should consider log time from Jira to calculate the effort spend
What problems is the product solving and how is that benefiting you?
It is helping me to see where is my engineering team contributing, how they make progress or improvement in development process. Where they can expedite the development process.
Great for understanding where engineering effort is spent
What do you like best about the product?
Jellyfish provides the visibility we need for understanding where our development teams are spending their time. It has also helped us to be more aware of JIRA data hygiene, and following best practices for ensuring work items and code PR reviews are properly connected. Equally for managers such as myself, the tool provides a wealth of information for informing individual discussions with team members too.
The scenario planner helps with estimating projections for likely work completion - thereby taking some of the 'guesswork' out of this. This helps inform stakeholders such as product managers as to likely delivery.
The tool is generally easy to use, one of the key aspects during my evaluation and eventual selection of Jellyfish was that it provides the ability to drill into any chart or metric to see the constituent data. The DevEx aspect for gathering information on the 'qualitative' aspects of how development teams work i.e. their 'feeling' about efficiency and good process is up and coming (its not yet as strong as some competitor tools I evaluated) - but this is more than enough for our needs, considering our initial engineering focus is predominantly on quantitative aspects - which is where Jellyfish excels.
Their customer support team is very responsive to any queries or issues, and having a dedicated person as point of contact for advice has been very helpful for us to try and get the most out of the tool.
The scenario planner helps with estimating projections for likely work completion - thereby taking some of the 'guesswork' out of this. This helps inform stakeholders such as product managers as to likely delivery.
The tool is generally easy to use, one of the key aspects during my evaluation and eventual selection of Jellyfish was that it provides the ability to drill into any chart or metric to see the constituent data. The DevEx aspect for gathering information on the 'qualitative' aspects of how development teams work i.e. their 'feeling' about efficiency and good process is up and coming (its not yet as strong as some competitor tools I evaluated) - but this is more than enough for our needs, considering our initial engineering focus is predominantly on quantitative aspects - which is where Jellyfish excels.
Their customer support team is very responsive to any queries or issues, and having a dedicated person as point of contact for advice has been very helpful for us to try and get the most out of the tool.
What do you dislike about the product?
A couple of features we'd like to have:
- ability to set 'alerts' for specific thresholds e.g. 'large' PRs, though some of the other things we'd be interested in have been covered by the recent Team Pulse feature
- integration with Microsoft 365 calendars (currently only Google is supported)
- integration with HR systems, to pull in team structures & reporting lines
- ability to set 'alerts' for specific thresholds e.g. 'large' PRs, though some of the other things we'd be interested in have been covered by the recent Team Pulse feature
- integration with Microsoft 365 calendars (currently only Google is supported)
- integration with HR systems, to pull in team structures & reporting lines
What problems is the product solving and how is that benefiting you?
Jellyfish provides the visibility we need for understanding where our development teams are spending their time. It has also helped us to be more aware of JIRA data hygiene, and following best practices for ensuring work items and code PR reviews are properly connected. Equally for managers such as myself, the tool provides a wealth of information for informing individual discussions with team members too.
Enabling actionable insights and driving valuable outcomes by making engineering work visible.
What do you like best about the product?
Engineering work is clearly segmented into categories that fit with the way our organisation delivers.
What do you dislike about the product?
Sometimes there is a lack of granularity in control of users' access to information.
What problems is the product solving and how is that benefiting you?
Jellyfish shows us exactly what software engineers are working and when. By being aware of the effort, cost and timescales associated with deliverables, products, platforms and teams, we can make investment decisions and prioritise accordingly to maximise the value we get from our engineering capability.
Insightful and Elegant
What do you like best about the product?
Jellyfish is a daily companion for our team. We use it regularly to track progress, and review metrics on a weekly basis to inform our planning and retrospectives. It’s easy to use, even for non-technical team members, and the overall interface is clean and approachable. The graphs are beautiful, useful, and easy to interpret, which makes spotting trends or anomalies straightforward.
I also really appreciate the powerful filtering capabilities, which let us cut the data by team, time range, epic, ticket or delivery status in just a few clicks. The integrations with tools like GitHub and Jira work smoothly and help bring everything into one place.
I also really appreciate the powerful filtering capabilities, which let us cut the data by team, time range, epic, ticket or delivery status in just a few clicks. The integrations with tools like GitHub and Jira work smoothly and help bring everything into one place.
What do you dislike about the product?
The initial setup experience could be smoother. While the documentation is decent, configuring access and getting the right level of granularity in the data takes a fair amount of time and effort. For teams without a dedicated resource, this might be a bit of a hurdle.
Additionally, one issue I've noticed with their AI usage metrics is that "advanced users" are identified based on cumulative usage volume. This can be misleading, high usage doesn’t necessarily equate to expertise or effectiveness. A more nuanced or behavior-based measure would better reflect actual proficiency with the tool.
Additionally, one issue I've noticed with their AI usage metrics is that "advanced users" are identified based on cumulative usage volume. This can be misleading, high usage doesn’t necessarily equate to expertise or effectiveness. A more nuanced or behavior-based measure would better reflect actual proficiency with the tool.
What problems is the product solving and how is that benefiting you?
Teams performance and visibility
Custom Alerts and Tracking
What do you like best about the product?
What notifies me when an Epic is about to expire.
I can see the status of activities and the team's performance without having to log into Jira.
I have centralized the information from Jira and Github in one place.
I can focus on performance analysis and see possible improvements for team members.
I can see the status of activities and the team's performance without having to log into Jira.
I have centralized the information from Jira and Github in one place.
I can focus on performance analysis and see possible improvements for team members.
What do you dislike about the product?
There are some errors in the synchronization of information, alerts of open pull requests, which were actually already closed, giving false positives.
What problems is the product solving and how is that benefiting you?
Centralize the information from different sources like GitHub and Jira, which provides a more accurate view of the team's work, allowing easy identification of areas for improvement.
JellyFish - The software engineering intelligence platform
What do you like best about the product?
I like how Jellyfish gives visibility into our engineering work without disrupting workflows. Being able to track DevOps metrics and align delivery performance with business goals helps our team continuously improve.
What do you dislike about the product?
- Steep learning curve: Some users find it takes time to fully understand and configure the platform effectively.
- Limited customization: There can be constraints when trying to tailor dashboards or reports to specific team needs.
- Data delays: Real-time reporting isn’t always as immediate as expected, which can affect decision-making.
- Limited customization: There can be constraints when trying to tailor dashboards or reports to specific team needs.
- Data delays: Real-time reporting isn’t always as immediate as expected, which can affect decision-making.
What problems is the product solving and how is that benefiting you?
- Disconnected data: Engineering activity is scattered across tools like GitHub, Jira, and CI/CD systems. Jellyfish pulls it all together.
- Unclear performance metrics: It tracks DORA metrics (like deployment frequency and lead time) to measure DevOps health.
- Limited strategic insight: Leaders often struggle to understand where time and effort are going. Jellyfish maps work to business priorities.
- Manual reporting: It automates reporting on engineering output, reducing time spent on spreadsheets and status updates.
- Unclear performance metrics: It tracks DORA metrics (like deployment frequency and lead time) to measure DevOps health.
- Limited strategic insight: Leaders often struggle to understand where time and effort are going. Jellyfish maps work to business priorities.
- Manual reporting: It automates reporting on engineering output, reducing time spent on spreadsheets and status updates.
showing 11 - 20