What is our primary use case?
My main use case for Jellyfish is that it has helped us save several hours of work each month for leaders. It incorporates detailed metrics that give us an idea about how the scrums can be improved and boost team performance.
A specific example of how Jellyfish helped my team save hours or improve scrums is that it gives us a holistic picture of data collected from various systems, regardless of the tech stack teams use. It is superior to other vendor products available in terms of customization, offering organization when necessary.
Jellyfish can collect data from various development teams and provide analysis without intervention.
How has it helped my organization?
Jellyfish has positively impacted our organization as it helps us grow our team efficiency at work. The documentation is excellent to start working with the product.
It helped my team grow efficiency through its easy setup, which takes time to learn, but is overall easy to use once you get the hang of it.
What is most valuable?
In my opinion, the best features Jellyfish offers are data collection, its lightweight nature, and the wonderful Jellyfish team.
When I mention data collection, Jellyfish stands out in that it can collect data from various development teams and provide analysis without intervention, helping us to make data-driven decisions easily. It is very lightweight, easy to configure, and provides accurate intelligent predictions. The Jellyfish team is wonderful, knowledgeable, and practical in resolving our queries on time.
Jellyfish provides a very excellent and intuitive user interface that helps to understand where time is being spent across our organization and is integratable with other platforms and software we use daily.
What needs improvement?
To improve Jellyfish, I suggest adding the view on the return on investment, making it easy to identify waste within our processes. It is a great way to see engineering overall results and measure.
Sometimes understanding the metrics is not simple. I also believe they should keep improving the user interface.
The individual developer metrics are not very useful and make the interface feel cluttered, which is an improvement that Jellyfish needs.
For how long have I used the solution?
I have been using Jellyfish for five years.
What do I think about the stability of the solution?
Jellyfish is stable and has been reliable for our organization.
What do I think about the scalability of the solution?
Jellyfish's scalability is good, as it handles our growth effectively.
How are customer service and support?
The customer support is very responsive and proactive, and I have had good experiences with their support team.
Which solution did I use previously and why did I switch?
I previously used Jira software, GitHub, and GitHub.
How was the initial setup?
My experience with pricing, setup cost, and licensing is that everything was excellent, straightforward, and the cost is very cost-effective compared to other alternatives.
What was our ROI?
I have seen a return on investment as it is easy to set up and a great tool. It is a great tool because it is easy to identify waste within our process.
Which other solutions did I evaluate?
Before choosing Jellyfish, I evaluated other options such as Miro.
What other advice do I have?
My advice to others looking into using Jellyfish is that I really recommend using it. If this is something your company is looking for, definitely give it a try. The Jellyfish team is also very responsive and supportive while updating, changing, or modifying required data. Having metrics from different tools in one place is very useful, especially when you have several engineering teams. I would rate this product a 9 overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
