Ability to get enhanced reports into sprint metrics over the month/quarter

Sometimes tricky to drill down into how things like carryover are being labeled

It's been great so far. It was a slow start for us because we also had to transition to using Jira rather than Github issues, but as we've finalized processes, we're starting to have a nice trove of data to help with planning and facilitate discussions amongst engineering leadership and with the product organization.

I appreciate that it gives a more product-centric view to engineering output. Rather than focusing on reducing engineers down to an abstract number making opaque claims about individual impact, Jellyfish looks more holistically at what engineering is working on, how it ties back to roadmap and higher level goals, and really helps understand where time is being spent.

The individual developer metrics are not very useful. I would be fine with not having them, but as it is, we don't use them so it's kind of clutter in the interface.

Provides data and information necessary to perform my work in a convenient method

UI isn't intuitive and requires addl. research before using. Navigation isn't intuitive either.

Wonderful customer services, not only supporting our needs, but also providing their own experience to help solve our business use cases. Again, really pleased we have a solution that allows for effort tracking without requiring time tracking. Additionally to reiterate the plug and play reality of this software is wonderful. You have the option to customize to fit your business needs, yet still getting business value data right away just by looking at existing tools.

The tool allows for allocation of effort spent, allowing a business to understand effort without time tracking. Rolling that data up into business value data points. Additionally, we were able to plug this into our existing ticket tracking system, and begin to see the analytics right away.

The user experience takes time to learn. The negative is both pro and con because there is SO MUCH data available, its difficult to best know how you'd pack that into an easier UI.

It's been very good so far. It was easy to setup, easy to start using and within the first week I was using it as the basis of communications and presentations I had to give both to my group and to my leadership.

I love how Jellyfish has an opinionated view that the metrics that matter for an engineering team should be ones that help you understand what value your organization is working on and shipping, not just what individuals are doing on a given day. That allows me to use Jellyfish in a more strategic way than some of the other tools in this space I've previously tried.

It's still a somewhat new product, the UI took me a little getting use to because there were so many different types of data and ways to access it. I liked the breadth and depth of data about my organization they had, but I look forward to them tweaking how it's presented in the future.

User friendly, Good team reports, Ease to use.

Need more reports that pull the data from JIRA

Overall great experience and helpful tool for managing teams.

Easy to use dashboards that provide information to manage teams. Love the ability to drill down for details. Well organized.

Needs better documentation and online help to understand what some of the information is. Would like more features to drill down on code to know what areas of the code base are hotspots, and features to help support forecasting of work.

Jellyfish really is good at a doing a lot of things. I primarily use it to help track my own velocity and ensuring quality of stories in our backlog. It's great at visualizing those things.

There is a fairly steep learning curve. I feel as if training is vital to be able to use the product well. I also believe that having consistency across an organization is important as well.

It's good. It has all of the raw data and it's just a matter of getting alignment on using this in our company reporting.

I've long been an advocate of knowing metrics for agile practices; beyond burndown percentages. Jellyfish surfaces this data and helps me prove that teams are becoming more efficient over time.

I think a lot of this is on me, I'm not incorporating data from Jellyfish into my professional goals/OKRs. There is a long process of buy-in at my company and this is slowing a greater embrace of Jellyfish data.

Satisfied user

JIRA Issues, Epics, etc. data mining and ease of use

lack of User configuration to create custom reports

My experience has been great os far. The product is very useful and the customer support is brilliant.

This engineering analytics tool closes the gap between engineering and the executives because it makes the translation of the engineering activity into business metrics/language. That is super helpful for any company to understand its operation efficiency and where to improve.

Although the product is quite complete I would like to have more indicators (business and engineering).

Jellyfish provides visibility into almost anything that can be measured or counted about my teams' output, as recorded in Github and Jira. All these different measures have to be taken in context to be of any value, but Jellyfish supports building a picture by offering quick navigation into and across different metrics and ways of aggregating them.

It's no con on the part of Jellyfish, but these metrics could be used poorly or abused.

- The high-level project overview provides insight into where the team has been focusing their efforts - Provides a deep-dive into metrics for individual contributors paving the way for constructive feedback

- In comparison to competing products it is missing some IC metrics (risk, churn, impact etc.) - the tool is more focused on throughput metrics, and doesn't analyze code commits to determine the "fuzzier" context.

Easy to partition raw data and splice it into useful formats once you get over the initial setup hurdle.

Easy to forget that the results you get are heavily skewed by the way your teams work with Jira. You get what you put in to it, and if you don't keep that in mind, you'll make decisions based on wrong assumptions. This is more a critique of the philosophy of the product than the product itself though.

The integration into GitHub and JIRA work well to give a high level view and well as the ability to deep dive on organization work. I particularly like the ability to see allocation per projects/areas.

Sometimes the detail get too detailed too fast. High level is great but it feels like the product could do with a mid-level of insights.

Love the idea behind it. Great way to help evaluate how teams and individuals are performing in comparison to each other.

Would like easy dashboards to compare teams and team members to each other

Overall Jellyfish is a great tool to give a snapshot of various KPIs for projects, teams, and individual. I love the charts.

I like the software's intelligence to integrate various software development platforms into a single place and present it with a complete analysis of projects and teams.

There are some metrics that retrieves from a set of information that may not be enough to give complete picture of an analysis, e.g. productivity. Sometimes, offline work, e.g. meeting or offline discussion were not tracked in the system does not appear anywhere in the system.

Very helpful to track coding day, number of story points completed

Software is slow and laggy. Takes lots of time to load.