Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Jellyfish takes the guesswork out of decision making
What do you like best about the product?
Jellyfish does a fantastic job of identifying a unit of work for engineers to understand how each resource is deployed in a given day, week, or sprint and accurately layer on data from Jira to provide precious insights into how engineering resources are allocated. We initially licensed Jellyfish to offer insights to engineering leadership into how our resources are deployed. The value has extended well beyond the engineering organization and delivers value to product, finance and program management.
What do you dislike about the product?
Over the next couple of years, I would like to see greater tooling around data hygiene for example, suggestions around mistagged epics and miscategorized employees.
What problems is the product solving and how is that benefiting you?
Jellyfish is helping us understand our investment allocation against strategic themes and initiatives and helping us make resourcing decisions based on business drivers set by our leadership.
- Leave a Comment |
- Mark review as helpful
Make sense out of the data
What do you like best about the product?
Jellyfish resolves a lot of product gaps within JIRA, such as providing reliable cycle time reporting and getting better BI on the epics.
What do you dislike about the product?
The interface takes a lot of clicks to navigate and is difficult to use on small screens.
What problems is the product solving and how is that benefiting you?
Jellyfish has given us real cycle time reporting and epic statuses since those out-of-the-box in JIRA are nearly useless. This helps us with quarterly planning and knowing what our true utilization rates are.
Capitalization reporting without burdening engineers with time sheets
What do you like best about the product?
Jellyfish enables us to measure engineering productivity in a way that I don't think is possible with any other software. Not only does it aggregate data from multiple sources, but it also provides measurements that you can't easily/natively get from the source data.
Another major reason that we use Jellyfish is for capitalization reporting. Before Jellyfish, our finance team was basically guestimating what our capitalization spend was. Now with Jellyfish, our capitalization reporting is much more evidence-based which makes audits much easier to deal with.
Another major reason that we use Jellyfish is for capitalization reporting. Before Jellyfish, our finance team was basically guestimating what our capitalization spend was. Now with Jellyfish, our capitalization reporting is much more evidence-based which makes audits much easier to deal with.
What do you dislike about the product?
While there are very useful velocity/story point reports/metrics available for our sprint-based/scrum teams, there doesn't seem to be a great way to meaningfully use story point/velocity data for our Kanban teams with Jellyfish. There are plenty of other data points that we can leverage instead, but I'd like to see better ways to use our story point data for our kanban teams.
What problems is the product solving and how is that benefiting you?
We can see where engineers and engineering teams spend their time and group it into categories (product, tech debt, maintenance, etc.). We are able to put a dollar amount on the engineering effort of epics/stories worked on by our teams. Our finance team is able to confidently provide capitalization reporting based on reliable data that doesn't require engineers to log their time.
GITHUB Metrics for performance analysis of engineers
What do you like best about the product?
A good number of metrics are provided by Jellyfish
We do an analysis of a software engineer based on GitHub metrics collected by Jellyfish.
Jellyfish is used by all the managers in our current organisation.
We do an analysis of a software engineer based on GitHub metrics collected by Jellyfish.
Jellyfish is used by all the managers in our current organisation.
What do you dislike about the product?
Jellyfish UI is a little old; it can be made engaging.
Jellyfish JIRA integration should be improved.
Jellyfish should give an alert if the candidates performance is going down.
Jellyfish JIRA integration should be improved.
Jellyfish should give an alert if the candidates performance is going down.
What problems is the product solving and how is that benefiting you?
Jellyfish JIRA analytics helps us to find bugs which are taking a long time for resolve.
Jellyfish GITHUB analytics helps us to find PR which are taking long time for complete.
Jellyfish GITHUB analytics helps us to find PR which are taking long time for complete.
Good metrics to improve the analyse the engineers
What do you like best about the product?
It gives metrics like
1. Number of coding days in a week.
2. Total time spent on code review
These metrics helps the managers to analyze the performance of a candidate.
1. Number of coding days in a week.
2. Total time spent on code review
These metrics helps the managers to analyze the performance of a candidate.
What do you dislike about the product?
I would like to see the following improvements
1. The UI can be improved
2. It can tell the manager if an engineer is overburden or not.
3. It should also do an analysis of figma too.
1. The UI can be improved
2. It can tell the manager if an engineer is overburden or not.
3. It should also do an analysis of figma too.
What problems is the product solving and how is that benefiting you?
It gives metrics like
1. Number of coding days in a week.
2. Total time spent on code review
These metrics helps the managers to analyze the performance of a candidate.
1. Number of coding days in a week.
2. Total time spent on code review
These metrics helps the managers to analyze the performance of a candidate.
Unique tool to get insight of Agile and DevOps metrics
What do you like best about the product?
JellyFish collects the data from all tools and puts it into helpful information in different metrics.
The Engineering team can use these metrics to understand the gaps in their process to improve their team's efficiency, which eventually enhances the organization's overall efficiency.
Excellent product and support Team that responded quickly to resolve the problem.
The Engineering team can use these metrics to understand the gaps in their process to improve their team's efficiency, which eventually enhances the organization's overall efficiency.
Excellent product and support Team that responded quickly to resolve the problem.
What do you dislike about the product?
Role-based configuration could be better for set-up users of JellyFish.
Sometimes it felt like a lot of dependency on the JellyFish team to set up various things, which improved drastically with time.
Sometimes it felt like a lot of dependency on the JellyFish team to set up various things, which improved drastically with time.
What problems is the product solving and how is that benefiting you?
JellyFish provides a great dashboard and gives a big picture of the activities happening at the Developer, team, and organization levels which is helpful for engineering leaders.
Aggregate analytics in a few clicks
What do you like best about the product?
Jellyfish gives me immediate insight into how my team is doing, with line-level detail at a click of a button. It's also interesting to see the benchmarked data of any group against any group; team against company, company against external companies, team members against the team, etc.
What do you dislike about the product?
The user experience is a bit jarring, depending on the platform user. For an executive, it's easy to see data for the entire organization. However, for an engineering manager, the default view is too macro. I want to default to my team on practically every page, but the default is always too large. I'd also prefer to dig into the configuration myself with the settings entirely at my disposal, such as what I have access to (self-service). Finally, finding what I'm looking for is difficult—I know the data is in the platform, but where? I'm not sure.
I want a dashboard to drill into the current team's metrics or velocity, with a metric that suggests whether a team member is being overworked and needs work to be spread out. LinearB, a competing product, has a dashboard like this.
I want a dashboard to drill into the current team's metrics or velocity, with a metric that suggests whether a team member is being overworked and needs work to be spread out. LinearB, a competing product, has a dashboard like this.
What problems is the product solving and how is that benefiting you?
Aggregate insights into development cycle metrics. Communicating our engineering value. Focusing on what's important and digging into where our time is being spent.
Excellent tools for Engineering Teams' Metrics
What do you like best about the product?
The dashboard is a one-stop shop for engineering teams' metrics. It provides a quick summary of how individuals and groups are performing. It gives you a short sight of the investment allocation of the engineering projects to see where the engineering teams are putting their time. It also provides an investment breakdown showing how much we invest across different areas. Most importantly, it allows you to determine whether the engineering teams follow best practices.
What do you dislike about the product?
Your sprint backlog items must exceed a minimum number of issues in Jira to show a sprint report in jellyfish.
What problems is the product solving and how is that benefiting you?
JellyFish gives a snapshot of data across all teams, allowing us to use it in evaluation and analysis and to determine any improvement areas to focus on.
Fantastic tool for aggregating metrics and letting you see the big picture
What do you like best about the product?
Jellyfish does a great job of aggregating data from multiple sources and channels that data into a deep well of metrics that paint a clear picture of how well your organization is performing. The metrics library is extensive to help zero in on the numbers that matter most for your organization and go beyond developer productivity to include Planning, DevOps, Support, Documentation and more. The Customer Success team was eager to help customize the data we wanted to fit our needs and even provided helpful tips on configuring other products so that Jellyfish could better utilize the data. I love the ability to take any of these metrics and drill down to the team or individual level to help identify inefficiencies or bottlenecks in productivity. Also, being able to compare our metrics against industry benchmarks really helps gain much needed perspective.
What do you dislike about the product?
The only pain point I felt during onboarding was the lack of additional webhook & third-party integrations. I would have benefitted from an OpsGenie webhook to send incident data, and transmitting deploy data from Harness took some time to get right. Additionally, not every metric is clear on how it's calculated (e.g. coding days), though Customer Success was great about explaining everything in detail.
What problems is the product solving and how is that benefiting you?
Having Jellyfish in place has already helped us gain visibility into each development team's efficiencies and problem areas. This added insight makes it much easier to pinpoint what is working well and what isn't. The DevOps metrics are also helping identify processes and queries that are causing incidents in our environment.
Wonderful tool for implementing agile with technology teams
What do you like best about the product?
Jellyfish is a great tool that has helped me immensely in getting our development teams to adopt agile, follow sprints, and improve predictability.
What do you dislike about the product?
There is nothing I dislike about the tool so far!
What problems is the product solving and how is that benefiting you?
Jellyfish is helping us keep the integrity of the sprint; we've gone from 50-60% predictability to 80-90% predictability after only a few sprints.
showing 131 - 140