Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
300 reviews
from
External reviews are not included in the AWS star rating for the product.
Deep insights for Engineering managers
What do you like best about the product?
Jeelyfish provides multiple levels of consolidation on data and trends. At the same time, it gives you the ablity to see the contributing matrices at an individual level.
What do you dislike about the product?
A lot of the data looks empty due to either bad integration or the inability to follow right steps. Jeelyfish should highlight that an provide tips in the tool to improve that.
What problems is the product solving and how is that benefiting you?
The engineering headcount increased by almost 4x in the last couple of years and jellyfish enabled us to scale well while effectively monitoring sprint health, and track work allocation, and productivity at an individual level.
Opens your eyes up to new ways of thinking
What do you like best about the product?
My favourite feature is "Interactions and Activity". I've never thought which developers are reviewing whose PRs before, but this feature makes it super easy to visualize direction and amount of interactions in Git PRs.
What do you dislike about the product?
I'm very conscious that people could use Jellyfish metrics the wrong way, such as tying a specific metric to somebody's performance review. Maybe Jellyfish could highlight risk in its UI? Sort of an in-UI education thing?
What problems is the product solving and how is that benefiting you?
I haven't figured this out yet. I've spent maybe 5-10 hours on Jellyfish. I'm still learning the tool and how it can benefit me.
Jellyfish is a powerful tool for Engineering team insights
What do you like best about the product?
Jellyfish (JF) gives you a LOT of data and insights into your teams. While much of this data is available in source tools like Jira or Github, JF makes it very easy to get aggregated information, extrapolations, and insights gleaned from their algorithms and combined metrics. We also use the Cost Capitalization module which is game-changing for our Engineering teams. We get most of the Cost Capitalization data/reports for "free." The Cost Capitalization module has meant our Fiance teams don't need to bother Engineering teams to get Cost Capitalization data (time spent on projects, etc), respond to audits, etc.
What do you dislike about the product?
Not a dislike, but an acknowledgment of "garbage in, garbage out". For JF to become useful, your team's processes and data practices need to be clean. If Jira data is incomplete, Jira or Github practices spotty or inconsistent, then the information in JF will be poor. A powerful effect of adopting JF has been a concerted effort to clean up our data and processes. It can't be understated the amplification effect in JF if your source data in Jira nd Github are poor. While it's been a heavy lift to clean up data/processes, it's been a significant benefit across our Engineering teams that extends well beyond just JF.
One challenge in JF itself is its learning curve. It can be a complex product and requires commitment and consistent adoption to see value. But if you're willing to work to clean data and learn the ins and outs of the tool, it is very powerful and valuable. More/better training resources and some UX changes could make it more intuitive and easy to pick up quickly.
One challenge in JF itself is its learning curve. It can be a complex product and requires commitment and consistent adoption to see value. But if you're willing to work to clean data and learn the ins and outs of the tool, it is very powerful and valuable. More/better training resources and some UX changes could make it more intuitive and easy to pick up quickly.
What problems is the product solving and how is that benefiting you?
Jellyfish (JF) provides a lot of easy to see metrics and insights that used to take us a lot of time, forensics, data processing to get before JF. It's difficult to quantify Engineering effectiveness. There is no single metric, piece of data, or silver bullet to tell you how an Engineering team is doing and if it's effective, productive, or healthy. Where are teams feeling pain? Do we have bottlenecks? Are we being efficient? These are notoriously difficult not only to measure but to interpret and act upon. JF's super power is giving us fast, easy access to a lot of data points that let's us spot trends -- but then has the ability to double click and drill into areas we have questions.
Awesome tool for tracking project split and finding inefficiencies with sprint plannings
What do you like best about the product?
UI is great - easy to use and understand, and tickets/projects/teams are imported from our ticket management system, so everything is consistent.
What do you dislike about the product?
The import process for first time initialization could be better - there were quite a few duplicated entries from JIRA projects/tickets.
What problems is the product solving and how is that benefiting you?
We wanted a clear picture of how our efforts are spent during product development and the planning process. Jellyfish provides a central place to analyze and visualize related data.
Powerful Insights to Guide Decision Making
What do you like best about the product?
I have been using Jellyfish now for several years. It opens up a plethora of insights that had historically been difficult to compile. This information unlocks much more powerful decision making capabilities. My teams use it to retrospect and make continuous improvements. The deliverables views also deliver as close to ground truth as possible on the status of your company initiatives. All around great product.
What do you dislike about the product?
Any time I have an issue or feature request the Jellyfish team is very responsive. They are continuously delivering new and powerful features. Most recently my teams have benefitted from the new Life Cycle feature. It provides great, actionable detail into the software development lifecycle.
What problems is the product solving and how is that benefiting you?
We use Jellyfish to confirm our actual work allocation is in line with company objectives, our teams use the team-based metrics for retrospectives and reviews, and we use the deliverables views for ground truth on the status of our key company initiatives.
Software Capitalization Campion
What do you like best about the product?
The platform's ease of use, simplicity and smoothness and the only platform I have used that does software capitalization cost really well.
From an accounting point of view, managing projects in JIRA while trying to assign engineer costs to each project accurately has been a headache. Jellyfish has been a breath of fresh air. It takes away all the formulas and spreadsheet work of tracking time/cost and has helped improve our team's efficiency, allowing us to report accurate monthly costs.
Customer support has been very impressive as well as timely releases of platform improvements and updates!
From an accounting point of view, managing projects in JIRA while trying to assign engineer costs to each project accurately has been a headache. Jellyfish has been a breath of fresh air. It takes away all the formulas and spreadsheet work of tracking time/cost and has helped improve our team's efficiency, allowing us to report accurate monthly costs.
Customer support has been very impressive as well as timely releases of platform improvements and updates!
What do you dislike about the product?
While the platform becomes better, I think a better/automated way to capture employee compensation and add new employees to the system would improve the overall user experience.
What problems is the product solving and how is that benefiting you?
Jellyfish is solving the way we calculate software capitalization cost without the use of timesheets. Having the platform do all the calculations for us frees time and allows management to focus on other importing problems.
Insightful & Powerful tool for self and management
What do you like best about the product?
Excellent ability to get the details about project allocation/work for self & the team, which is very easy for management to track.
Its integration with JIRA, Bitbucket, Github and other engineering tools provides the ability to get the details about both deep and high-level work.
Its integration with JIRA, Bitbucket, Github and other engineering tools provides the ability to get the details about both deep and high-level work.
What do you dislike about the product?
I feel that Metrics are not appropriately used, they can be easily abused.
It would be great if there would be some metrics in future added in jellyfish for Code commits.
It would be great if there would be some metrics in future added in jellyfish for Code commits.
What problems is the product solving and how is that benefiting you?
Integration with JIRA and other tools makes the job easier to track down day-to-day tasks and helps in improving the productivity by selecting important task/ work on priority basis.
Very useful for monitoring daily work
What do you like best about the product?
I find Jellyfish very useful when it comes to tracking all the work, it's amazing all the details it shows about what you have in Jira. In my case I use it a lot to see week by week what we have worked on, category, ticket work cycles, number of revisions, pages created in confluence. In short, it is a very necessary tool that makes it easier to control and manage your work.
Update: After more than one year since my last review I can confirm that Jellyfish continues helping me to track all the tasks managed by my team. The section I consult the most is the Team & Unit Dashboard to measure the efforts per week in detail.
Update 2:I still think it's a great tool for tracking the tasks my team performs and seeing where there is room for improvement.
Update: After more than one year since my last review I can confirm that Jellyfish continues helping me to track all the tasks managed by my team. The section I consult the most is the Team & Unit Dashboard to measure the efforts per week in detail.
Update 2:I still think it's a great tool for tracking the tasks my team performs and seeing where there is room for improvement.
What do you dislike about the product?
So far nothing serious, I don't think I have explored all the potential that Jellyfish have. Almost every time I have had a question or wanted to consult some data, a colleague or the person who manages it has helped me.
Update: I still think the same as I said more than a year ago, I still have a lot to discover about Jellyfish, but I have no complaints about what I use on a daily basis.
Update 2: Maybe I need more information about all the characteristics of the jellyfish for the moment I didn't find anything I don't like in the use I give to it
Update: I still think the same as I said more than a year ago, I still have a lot to discover about Jellyfish, but I have no complaints about what I use on a daily basis.
Update 2: Maybe I need more information about all the characteristics of the jellyfish for the moment I didn't find anything I don't like in the use I give to it
What problems is the product solving and how is that benefiting you?
Above all, it helps me to keep track of which business categories we are working on.
Clear information on engineering team spent time for different projects or maintenance
What do you like best about the product?
The main goal is accomplished: providing view on the time spent by engineering between the different projects and especially the balance between new features and support/maintenance.
We've been able in a year to categorize almost all of time to a specific project or to support and KTLO (Keep The Lights On) and that's really helpful to see how much time this support to customer or maintenance and technical debt included in KTLO are representing.
We've been able in a year to categorize almost all of time to a specific project or to support and KTLO (Keep The Lights On) and that's really helpful to see how much time this support to customer or maintenance and technical debt included in KTLO are representing.
What do you dislike about the product?
The setup and the repetitive tasks of taking screenshots could be improved.
Obviously the data needs to be accurate as well and that takes a lot of time but this part is not specific to Jellyfish.
Obviously the data needs to be accurate as well and that takes a lot of time but this part is not specific to Jellyfish.
What problems is the product solving and how is that benefiting you?
Finding the balance between time spent on new features and on support and maintenance. It helped us allocating better engineering resources and finding out where there were maybe too much customer issues impacting the engineering to develop new features.
Get good insight on productivity to set the pace and predicting time to completion
What do you like best about the product?
Good insights on the team productivity. It can help to be informed about the team's performance so we know when we are doing well or struggling completing tasks.
What do you dislike about the product?
Going to the JellyFish interface causes a great distraction from the usual dev cycle. It would be more helpful to have it at my fingertips so I don't have to switch contexts to look at the reports.
What problems is the product solving and how is that benefiting you?
Gives insight into the average cycle times for tickets and provides a cross-team relative performance. Helps to alert us to look deeper at dwindling agility which could indicate that reestimation or outside help is required to solve the problem.
showing 211 - 220