Reviews 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.
Driving Business Alignment and transformational change within Engineering
What do you like best about the product?
All companies face several engineering challenges, with most having a root cause of 'lack of alignment'. As a CTO/CIO, we must align investments and see ROI. JellyFish has been instrumental in understanding our investment distribution and allocating team members to products. We've seen an immediate impact with alignment (are we indeed focused on Roadmap/Innovation, or is the reality "KTLO/Bugs"). Additionally, the new scenario planner will help support tactical strategies to remediate late Epics (projects). We've improved Speed, Processes, Productivity, and Collaboration.
What do you dislike about the product?
Nothing yet; however, one feature we'd like to see is scenario-based benchmarks to drive high-level organizational goals (OKRs with baseline metrics).
What problems is the product solving and how is that benefiting you?
We strategically staffed a product and aligned expectations using the investment distribution. This has helped reduce operating budgets and level-set expectations with business partners (product management + executive leadership). Additionally, we can focus on behaviors/actions that generate value.
Improved visibility into engineering efforts
What do you like best about the product?
Provides us with a data-driven way to show the business what our engineering teams are working on. The resource allocation views are configured to display our key initiatives in a single, portfolio view. Jellyfish allows us to be more thoughtful about measuring investment and enables our leaders to drill down by ticket type, FTE investment over time, and delivery status.
What do you dislike about the product?
I want more capabilities to empower developers to optimize their workflows and achieve continuous improvement through real-time notifications that integrate into day-to-day processes. The system provides helpful visual dashboards, but the data should be more actionable.
What problems is the product solving and how is that benefiting you?
Insight into what teams are working on, how efforts align with larger business goals, tracking the complete picture of development work across all engineers in the organization. Cost capitalization.
Great product and great team
What do you like best about the product?
I can answer a lot more of my questions about where the team is investing their time, the value of those investments, and the overall balance. Their team are also super engaged and helped us realize very quick wins.
What do you dislike about the product?
I can't think of anything I don't like about Jellyfish.
What problems is the product solving and how is that benefiting you?
Balancing investments, measuring ROI, and reporting on alignment with strategic direction.
Great analytics tool
What do you like best about the product?
Jellyfish's analytics is an invaluable tool for measuring engineering efficiency and providing valuable insights that allow for informed decision-making & streamlined workflows.
What do you dislike about the product?
For 2 months of active use, no disadvantages were noticed.
What problems is the product solving and how is that benefiting you?
Our business department uses Jellyfish to measure our engineering activity and no engineering side. We use a lot of different plots and graphs to see the weak sides and fix them shortly.
Provides visibility and insights team by team into the investments made and work being done
What do you like best about the product?
I can quickly see where teams are investing their time and energy in times of projects and in terms of value. I have the ability to talk to any product manager on my team and ask why we are making “this investment”. I can identify what teams need help with which aspects in the development process. We can have meaningful conversations about which investments are too big or when the “Works in Progress” load gets too high. As engineering and product leaders, we can collaborate to understand which teams need more coaching regarding their development practices. And best of all, I can quickly and easily provide clarity to the rest of the executive team and the board about where our bandwidth is being used. Simply put, it allows me to focus on the strategy and the people rather than the administration.
What do you dislike about the product?
There’s not really anything that I “dislike”. Like any tool, there are things I want to do with it that are just not completely built out, but those things tend to be stylistic like colors and ordering on graphs and charts. However, for anyone that is thinking about Jellyfish, understand that there is an investment that needs to be made in understanding the product, evaluating how you operate Jira, and determining how to make those work together. The team at Jellyfish has been great, but there’s a certain level of understanding you need to have to partner with the team to get it set up to be effective for you.
What problems is the product solving and how is that benefiting you?
It solves the visibility into project work. It helps me talk with product managers about the size of the investment relative to the value that we get from the investment. It helps me collaborate with our engineering leaders to understand where teams need additional support to be successful. It helps me explain to the organization where the team is investing their time and energy at a holistic level, which helps the conversation about what we can take on in terms of new initiatives and in what timeframes.
Great insights to help focus efficiencies
What do you like best about the product?
The level of detail at both broad (org) and granular (team) levels allows me to expose areas for improvement and track changes easily.
What do you dislike about the product?
Not much to dislike, in all honesty. Adding report exports in a more customizable way would be helpful but not a deal breaker.
What problems is the product solving and how is that benefiting you?
Jellyfish helps me uncover inefficiencies at the team and organizational levels. It also helps me track focus investment back to real-world impacts like revenue and churn.
Great tool to help your team to get more structure and check their signals
What do you like best about the product?
I am enjoying Jellyfish helping monitor our teams and giving clear metrics to help us work more efficiently. You can find great dashboards for Sprint Planning, team health, Devops metrics, and much more.
What do you dislike about the product?
At the moment, I am still missing some clear, actionable items that we could follow to improve some metrics. This would help take the best of all the metrics the tool provides and help the teams to fast onboard.
What problems is the product solving and how is that benefiting you?
Understanding how the effort of Engineering is spread in the company, team health, devops metrics, and sprint planning. The tool is helping us to become more productive and focus on what matters.
Insightful for Directors and Managers
What do you like best about the product?
As someone sitting in Director of Engineering role, Jellyfish gives me insightful data about my teams. On a weekly basis, I can identify patterns across teams in a way that I can start brainstorming experiments to address issues and reduce risk.
What do you dislike about the product?
My company uses Jellyfish data to present the "state of engineering" on team level and department level every month. As part of that, we take screenshots from charts in Jellyfish. That is a really timeconsuming process, and would be great if Jellyfish had a "presenter mode" that allows us to choose widgets with charts that we want to present.
What problems is the product solving and how is that benefiting you?
It's really the only tool that I know that gives me overview data that matters about my teams in the engineering department. Without Jellyfish, I'd have to running all sorts of complex queries in Jira, which means that I'd just not do it consistently because it's too time-consuming.
Discovering the world of JellyFish
What do you like best about the product?
It is a new tool for me. We are looking for new ways to measure information to obtain better results and make better decisions and that is how we discovered JellyFish as an innovative proposal that facilitates information management and provides innovative solutions to problems that as a company we did not even think were so relevant. I think it is a very useful tool full of attractive features for the business
What do you dislike about the product?
Beyond finding something that I don't like, I think that something that can be improved is the accessibility to courses and training to learn how the tool works. It would be very useful to have a small certification in the use of JellyFish
What problems is the product solving and how is that benefiting you?
Manage information and translate it into a friendlier environment. Incorporate the tool with the new developments that the company has to analyze the impact. We are starting to use it :)
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.
showing 231 - 240