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.
Valuable Sprints View for Scrum Master Coaching Teams
What do you like best about the product?
As a Scrum Master I use the Sprints View to review with my teams how our Velocity is trending. This view is more detailed than what Jira provides.
What do you dislike about the product?
I personally would appreciate views/dashboards by role in Jellyfish, for example I'm a Scrum Master and there is information I want to review with the team as a whole, but have to be careful about how the data is seen/portrayed as to not offend or cause alarms around being micro managed.
What problems is the product solving and how is that benefiting you?
Jellyfish has been a great way for us to encourage Jira & Github hygiene
- Leave a Comment |
- Mark review as helpful
An incredibly valuable tool with a couple areas for improvement
What do you like best about the product?
Jellyfish combines Git and Jira data into an easy-to-understand format that often leads to actionable insights. Compared to many alternatives, the setup is relatively straightforward, as Jellyfish comes with a lot of built-in features and opinions.
I appreciate Jellyfish's support and the new features that they have rolled out over the past few months. The team has done a good job explaining Jellyfish's philosophy and how to get the most out of the tool as possible.
I am particularly excited for the new goal setting framework that they are rolling out, as it will give teams even more value in the form of concrete operational objectives.
I appreciate Jellyfish's support and the new features that they have rolled out over the past few months. The team has done a good job explaining Jellyfish's philosophy and how to get the most out of the tool as possible.
I am particularly excited for the new goal setting framework that they are rolling out, as it will give teams even more value in the form of concrete operational objectives.
What do you dislike about the product?
Compared to a few alternatives, customizing and configuring Jellyfish is not as self-service as we would like.
One of the product's strengths is that it is opinionated. However, this comes with the trade-off of less flexibility. This is a tradeoff we were willing to accept, as it leads to standardization across teams, but Jellyfish's opinions might not align with every organization's philosophy.
In a similar vein, there are aspects of Jellyfish that require a support ticket to configure or change. Their support is responsive and it seems like they are building tools to make some configuration more self-service, but the current model can lead to configuration changes taking a day or two to be completed.
One of the product's strengths is that it is opinionated. However, this comes with the trade-off of less flexibility. This is a tradeoff we were willing to accept, as it leads to standardization across teams, but Jellyfish's opinions might not align with every organization's philosophy.
In a similar vein, there are aspects of Jellyfish that require a support ticket to configure or change. Their support is responsive and it seems like they are building tools to make some configuration more self-service, but the current model can lead to configuration changes taking a day or two to be completed.
What problems is the product solving and how is that benefiting you?
Jellyfish allows our engineering managers and leaders to understand how their teams are performing and where they can improve. It gives us insight into operational metrics beyond just DORA, with a focus on process, collaboration, and investment allocations. This allows our teams to determine if they are focusing on the right areas of investment and if there are any bottlenecks in thier processes.
Fantastic tool
What do you like best about the product?
Tracking deliverables and viewing scope creep or off-target dates is fantastic for keeping on top of goals
Team health metrics like predictability and speed are an excellent way for us to support teams in achieving velocity and flow.
Life cycle explorer has helped us identify and remove bottlenecks in our processes.
Customizable views and dashboards help us keep focused on what's most important to us
Financial reporting has been a game changer for our finance teams to easily understand capitalizable R&D work
Very responsive support team who resolves bugs and configuration requests quickly
Customer Success team are knowledgable, responsive and continuously support optimizing value
Team health metrics like predictability and speed are an excellent way for us to support teams in achieving velocity and flow.
Life cycle explorer has helped us identify and remove bottlenecks in our processes.
Customizable views and dashboards help us keep focused on what's most important to us
Financial reporting has been a game changer for our finance teams to easily understand capitalizable R&D work
Very responsive support team who resolves bugs and configuration requests quickly
Customer Success team are knowledgable, responsive and continuously support optimizing value
What do you dislike about the product?
Jellyfish has industry and company benchmarks but you can't set custom targets - would love to be able to have target metrics
No system performance metrics (eg. RUM, Downtime, Sev1 incidents) or product usage metrics which can tend to make the metrics output rather than outcomes focused. Ideally would be able to integrate with DataDog.
Unable to report on all deliverables - you can only view those in progress or complete - which makes it challenging to report on all quarterly goals (including those note yet started) for example.
No system performance metrics (eg. RUM, Downtime, Sev1 incidents) or product usage metrics which can tend to make the metrics output rather than outcomes focused. Ideally would be able to integrate with DataDog.
Unable to report on all deliverables - you can only view those in progress or complete - which makes it challenging to report on all quarterly goals (including those note yet started) for example.
What problems is the product solving and how is that benefiting you?
Identify and resolve process bottlenecks, increase speed of delivery, track deliverables & identify risks, improve sprint predictability & completion, financial reporting
Insight in your team, department and organization
What do you like best about the product?
Jellyfish brings the data from our most common development tools together and creates multiple different perspectives that allow us to monitor our operation. It aggregates from users, to teams, to departments, to organization, giving insights on any level we want.
What do you dislike about the product?
There is a fast amount of configuration possible. Not all of them are self-servicable (yet).
What problems is the product solving and how is that benefiting you?
Allowing teams to improve is hard, but it becomes easier if it can be data driven. Jellyfish gives our team insight in the metrics we value as an organization.
Great tool for tracking metrics and KPIs for the Engineering Organization
What do you like best about the product?
Jellyfish provides a great aggregate view to get insights for the organization or specific teams based on data in Jira and source code repository. The UI is simple and intuitive, and the customer success rep is great in terms of providing support and resolving issues. I consistently use Jellyfish to track progress of Initiatives, and also report KPIs to executives on a monthly basis. The DevFinOps module is a significant timesaver for doing software capitalization reports for the finance team.
What do you dislike about the product?
There could be more self-service support in the product, for example the ability to save deliverable views. The DevOps Also would be good to have an API to pull information into other tools. The DevOps metrics were a bit cludgy to set up, and didn't work well, so we're not using those.
What problems is the product solving and how is that benefiting you?
Jellyfish helps us:
* Track progress of development work
* Understand allocation for new features work vs bugfixes vs tech debt/infra
* Generate reports for the Finance team for software capitalization
* Track progress of development work
* Understand allocation for new features work vs bugfixes vs tech debt/infra
* Generate reports for the Finance team for software capitalization
Very solid platform
What do you like best about the product?
Jellyfish helps keep our focus on our key priorities by identifying just we are spending our time.
What do you dislike about the product?
Na. .
What problems is the product solving and how is that benefiting you?
Focus tracking
Roadmap alignment
Contractor efficiency and analytics
Software cap
Roadmap alignment
Contractor efficiency and analytics
Software cap
Improved Visibility and Insights
What do you like best about the product?
Time to value with Jellyfish is pretty fast. We were getting better insights into our processes within the first couple of days of turning on the connection, and it's only improved as we've added more data and addressed some data hygiene issues. I like how it's easy to see what areas the teams are investing in, what initiatives are in flight, and how groups are doing or which ones might need help.
What do you dislike about the product?
The lack of self-service configuration can be a point of friction as you're tuning your processes. They are working on it though, and have already added some capabilities that weren't there when we first started.
What problems is the product solving and how is that benefiting you?
Helping us align teams with company goals and helping us continually improve on team processes for development and delivery.
Best Engineering analytics product I've used
What do you like best about the product?
* Great single-pane-of-glass for project management and source code management insights.
* We can customize it to meet our needs
* Insights compared to competitors are much more authentic (you know what you're looking at, whereas, with competitors, you get a metric and are not quite sure how it's being computed).
* Customer enablement is very hands-on and shows commitment from the company to create value for their customers.
* We can customize it to meet our needs
* Insights compared to competitors are much more authentic (you know what you're looking at, whereas, with competitors, you get a metric and are not quite sure how it's being computed).
* Customer enablement is very hands-on and shows commitment from the company to create value for their customers.
What do you dislike about the product?
* Some data is hard to find (I end up clicking through a path that's indirect to get access to what I'm looking for)
* Sprint insights, in particular, is very buried and don't roll-up to the entire organization from the team level
* DevOps / DORA metrics are limited and non-standard and require more customization than I'd like.
* There is no ability to push reports out via email/slack at a regular basis - I have to actively come back into the product to get what I need.
* Sprint insights, in particular, is very buried and don't roll-up to the entire organization from the team level
* DevOps / DORA metrics are limited and non-standard and require more customization than I'd like.
* There is no ability to push reports out via email/slack at a regular basis - I have to actively come back into the product to get what I need.
What problems is the product solving and how is that benefiting you?
Jellyfish helps me understand how the Engineering department is spending time. This can be broken down by individual, team, or entire department. This creates actionable insights into whether our quality is sufficient (are we spending a lot of time fixing bugs) or whether our focus on generating customer value is enough (are we spending enough time on the product roadmap). Seeing this broken down by team makes the insights helpful at all levels of management.
Engineering metrics at a glance
What do you like best about the product?
Jellyfish can provide valuable insights into how the company is performing at a high level, then allows me to drill down to the team level and see where we can improve from a day-to-day level.
What do you dislike about the product?
As a new user of Jellyfish, the amount of data and information presented can be overwhelming. It takes some time to digest as it's not very intuitive. It would also be nice if the metrics could be broken down by sprints (and not just the generic month or quarters).
What problems is the product solving and how is that benefiting you?
It's difficult to quantify "how is your team performing?" and here's where Jellyfish comes in - providing metrics that the team can look upon as success metrics, then backing this up by collecting all of these data behind the scenes.
Improved Productivity, Metrics with Jellyfish
What do you like best about the product?
It is an excellent tool for self-reflecting on your progress in Sprints while also allowing you to see how your peers and the organization handle the workload in the sprints.
What helps is the visualization of these metrics.
Having the ability to have weekly and monthly comparisons can help the team/organization identify the projects that need more focus and also recognize other projects which are setting the benchmark.
What helps is the visualization of these metrics.
Having the ability to have weekly and monthly comparisons can help the team/organization identify the projects that need more focus and also recognize other projects which are setting the benchmark.
What do you dislike about the product?
The metrics do not consider the complexity of the some of the tasks.
Eg. When considering JIRA tickets, Github Pull Requests related metrics, the metrics tell us the turn around time, number of commits etc. but the values for any of these metrics are dependent on other factors i.e in case of JIRA, the ticket may have more dependencies which increase the turn around time.
Eg. When considering JIRA tickets, Github Pull Requests related metrics, the metrics tell us the turn around time, number of commits etc. but the values for any of these metrics are dependent on other factors i.e in case of JIRA, the ticket may have more dependencies which increase the turn around time.
What problems is the product solving and how is that benefiting you?
Looking at JIRA sprint wise breakdown, help improve dev. productivity across the team.
showing 71 - 80