Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
391 reviews
from
External reviews are not included in the AWS star rating for the product.
VP of Engineering
What do you like best about the product?
Everything is clickable! I can quickly drill down from high-level executive summary views into the details. This allows me to better understand the signals I'm seeing, and quickly garner actionable insights (eg, whether or not I need to realign focus in am area and which team or individual to check in with, fix the way an epic is categorized, check in on a project that is projected to miss target date, etc).
What do you dislike about the product?
There is a learning curve. It was overwhelming at first, even with the awesome support from the customer success and implementation team.
What problems is the product solving and how is that benefiting you?
1. Dev allocation, cost reporting, and focus - we used to do these manually every month. It was labor intensive and error prone. And it was a very lagging indicator. Jellyfish does this all automatically for us in near real time. Now we not only benefit from automated allocation reporting on canddnces for quarterly business reviews, financial audits against P&L, and board-level reporting. We also benefit from real time view into where the efforts are going. This helps us ensure our teams are focused on the right things and quickly course correct rather than waiting for lagging indicators like missed deadlines or monthly manual reports.
2. Project management- the project and initiative view allows us to see in one screen how a project is going, what work is scoped vs active, and what the FTE effort/focus has been over time. It also projects target completion date. This has allowed us to easily see and show when there is scope creep, too little capacity, etc. It also shows the cost for the given project or initiative which is hugely helpful in calculating the investment portion of ROI.
3. Manager insights - our Engineering Managers have benefited from viewing their team activity. They use this information to catch unspoken blockers, influx of unplanned work, and metrics around productivity, quality, etc. We are still evolving how EMs use it but so far we have already garnered many usable insights.
4. Operational tuning - we are just getting our feet wet here but the team and org-level metrics are a powerful way for us to see how we are operating and areas for tuning. It is especially helpful that we can see our metrics compared to industry metrics, as well as an individual team's metrics against our Engineering-wide metrics.
2. Project management- the project and initiative view allows us to see in one screen how a project is going, what work is scoped vs active, and what the FTE effort/focus has been over time. It also projects target completion date. This has allowed us to easily see and show when there is scope creep, too little capacity, etc. It also shows the cost for the given project or initiative which is hugely helpful in calculating the investment portion of ROI.
3. Manager insights - our Engineering Managers have benefited from viewing their team activity. They use this information to catch unspoken blockers, influx of unplanned work, and metrics around productivity, quality, etc. We are still evolving how EMs use it but so far we have already garnered many usable insights.
4. Operational tuning - we are just getting our feet wet here but the team and org-level metrics are a powerful way for us to see how we are operating and areas for tuning. It is especially helpful that we can see our metrics compared to industry metrics, as well as an individual team's metrics against our Engineering-wide metrics.
Big picture of investments & allocations.
What do you like best about the product?
Jellyfish has been instrumental in providing clear visibility into our engineering investments and allocations across our very large engineering team, making it easy to see both what we plan to invest in and how we actually spent our engineering resources.
What do you dislike about the product?
Limited number of buckets for allocations.
What problems is the product solving and how is that benefiting you?
It helps us to define Investment categories & help with strategic planning. It gives visibility into Engineering. Engineering has always been a black box before, now you actually see what each team contributes to and how it influences our strategy. Our new strategy is HRM+ and we need alignment across Engineering and strategy. The platform delivers exactly what we need - a transparent, comprehensive picture of our allocation decisions that helps drive better strategic planning.
Jellyfish helps us visualize the impact of our business decisions!
What do you like best about the product?
Jellyfish does an excellent aggregating and displaying the data needed to understand where I am spending all my effort.
What do you dislike about the product?
It is not yet sufficiently self-service, although recent releases have made great strides in that area.
What problems is the product solving and how is that benefiting you?
Our initial use-based was preparing board-level presentations. The Allocations Screen was a superb tool for this purpose.
Growing Quickly
What do you like best about the product?
Jellyfish is quickly growing and listening to their customers' needs.
They have many great ways to organize and report on utilization metrics and adjust for our organization's needs.
They have many great ways to organize and report on utilization metrics and adjust for our organization's needs.
What do you dislike about the product?
They are going through fast growth and changes. This requires extra attention to keep up with the pace of change and added functionality.
Being a newer product, they are also still missing some functionality that ultimately will be needed around admin control and configuration.
They cannot handle manual FTE time reporting for staff who do not show signals in JIRA. Many types of work go into the capitalization of software, not just engineers; unfortunately, Jellyfish can not capture these staff members today.
Being a newer product, they are also still missing some functionality that ultimately will be needed around admin control and configuration.
They cannot handle manual FTE time reporting for staff who do not show signals in JIRA. Many types of work go into the capitalization of software, not just engineers; unfortunately, Jellyfish can not capture these staff members today.
What problems is the product solving and how is that benefiting you?
Our teams were manually tracking time, and now many will be able to stop this manual practice and allow Jellyfish to report on their efforts.
This will also give insights into the spending on our efforts that has not previously been transparent at our orginization.
This will also give insights into the spending on our efforts that has not previously been transparent at our orginization.
Powerful and Rapidly Growing Engineering Management Platform
What do you like best about the product?
Extensive library of insightful metrics to help tell the story of how Engineering is spending its time
What do you dislike about the product?
Not yet easy to report on or integrate with other tools
What problems is the product solving and how is that benefiting you?
1. Having a Common Language with the rest of the Business
2. Tracking Against our Priorities throughout the course of the quarter
3. Having a consolidated view of Engineering Performance across teams and geos
4. Understanding Team Health
5. Backing Financial decisions with objective data
2. Tracking Against our Priorities throughout the course of the quarter
3. Having a consolidated view of Engineering Performance across teams and geos
4. Understanding Team Health
5. Backing Financial decisions with objective data
Great platform to understand where we invest time and to find areas to improve processes
What do you like best about the product?
I like they way it tracks work accurately, without effort by engineers. Jellyfish is constantly improving how you can view allocations, progress against deliverables, and team health metrics.
My favorite part is that Jellyfish automates virtually all of the manual work I used to have to do to track Software CapEx!
Our CSM and the Jellyfish team is always quick to help us figure out how to do something new, and to get our feedback on new features.
My favorite part is that Jellyfish automates virtually all of the manual work I used to have to do to track Software CapEx!
Our CSM and the Jellyfish team is always quick to help us figure out how to do something new, and to get our feedback on new features.
What do you dislike about the product?
My only feedback is I think we'd get better adoption/buy-in from our product team if there was more transparency/detail how how time/work gets allocated on each team.
What problems is the product solving and how is that benefiting you?
Jellyfish solves three problems for us:
1. The need to understand where we are investing our time
2. The need to track software dev CapEx
3. The need to understand areas to dig into to help teams become more productive through retros and coaching
For us, the benefit is time savings and productivity.
1. The need to understand where we are investing our time
2. The need to track software dev CapEx
3. The need to understand areas to dig into to help teams become more productive through retros and coaching
For us, the benefit is time savings and productivity.
Operational efficiency
What do you like best about the product?
Jellyfish helps to understand engineering work.
What do you dislike about the product?
You cannot do a bulk upload to update missing information.
What problems is the product solving and how is that benefiting you?
Understand engineering work, Manage Tech Budget, Identify pain points and where to focus. Helps increase efficiency and productivity of the engineering Team.
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.
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.
showing 331 - 340