
Jellyfish Software Engineering Intelligence Platform
High-Level CxO Reporting Powered by JIRA and Git Insights
Portfolio visibility has improved with structured workflows, but custom metrics still need work
What is our primary use case?
I was in charge of a Jira migration, and I was also in charge of bringing a new work portfolio management process to the company at the same time. We migrated from Jira on-premise to Jira Cloud and took advantage of that moment to implement Flight Levels portfolio management. I created workflows for Flight Levels Three, Two, and One: strategic, coordination, and operational. At that moment, a colleague told me about Jellyfish. I found it really interesting, especially for the process and planning part, cycle time, and business alignment, because those were the core of what we were doing at that time. My colleague also looked at other aspects, such as DevEx.
After the migration, once we had created the workflows and migrated all the teams, my colleague and I started to hydrate Jellyfish with information from Jira. This is mainly the reason I did not spend much time using Jellyfish: Jira was already delivering everything I was looking for. Other information I was looking forward to seeing was not easy to track in the company at that moment, because people were either not filling it in correctly or the information was mostly out of date. I do not think this is a flaw of Jellyfish. I think it reflects the moment the company was in. We were migrating services, and people were getting used to the new Jira and the new process, including connecting work inside the new structure. At that moment, Jira provided the portfolio management information, and it did so more properly because it was inside Jira. I had to tweak things more in Jellyfish and do some parsing. My colleague was really looking forward to the DevEx part and kept working towards it, but I never heard anything about it again.
This is basically my story with Jellyfish. I think it is a great idea, and there are lots of cool features in the app, no doubt about that. However, I am talking about almost two years ago, so Jellyfish may be a little better now in some aspects, such as connecting with the teams or helping to connect things. At that moment, Jellyfish was a little expensive, not in price but in time, because Jira and Atlassian were providing all the information I was expecting to see. The whole Atlassian suite provided connections with Goals, Projects, priorities, strategy, and other things.
My colleague integrated Jellyfish with GitHub, I think for PRs.
What is most valuable?
Predictive capabilities were the ones I tried to use, but we did not have enough data, or the data was not as up to date as it could have been.
In terms of performance indicators, I saw a couple of them in Jellyfish, such as lead time, cycle time, and other metrics in that sense. They were helpful, but those are metrics that I could also extract from Jira. I think the UX in Jellyfish was visually better, especially the charts. We had almost 30 teams, and we could drill down into the metrics for each team, which is great. It was super helpful.
For how long have I used the solution?
I used Jellyfish for a short time. In my specific case, it was a month or two. However, I had a colleague who kept working with Jellyfish for longer afterwards.
What do I think about the stability of the solution?
I did not experience any stability issues with Jellyfish. The experience was always good. That is what left me a little heartbroken, because I saw really cool features and it was working well, but I could not manage to work with it.
What do I think about the scalability of the solution?
I do not know how Jellyfish is now, but at that moment, I felt that some of its features and metrics were market metrics, meaning they are very well known and widely spread in the market. I know there are ways to add new metrics, but I felt that if you want a custom metric, it was not easy. The UI/UX at that moment was a little bit like saying, "This is the market metrics. You can fill them in and look at them."
I am raising this under scalability because a company with a specialized process could find this a little tricky. You need to make some concessions, and in terms of process, this tends to degrade a little over time. In our case, this was not much of an issue because we were tailoring a new process.
In comparison with Jira, I think Jira is so broad that a person who does not understand the tool or its capabilities could be a little lost among the many possibilities. Jellyfish is a little more narrow, so there are pros and cons. My point about scalability is that the narrowness of Jellyfish could cause some degradation of the process over time. This is only my assumption, as I used it for just a month, but it is what I saw. Perhaps Jellyfish is more versatile than that, but this is my perception.
How was the initial setup?
My colleague was in charge of the installation and can tell you more about the initial deployment of Jellyfish. As far as I saw, it was not as tricky as it could have been.
The maintenance I did was trying to figure out a way to keep the information up to date, which I mentioned earlier, but this is not really a Jellyfish issue. In terms of maintenance on Jellyfish itself, it was super straightforward.
What's my experience with pricing, setup cost, and licensing?
My colleague and I were using the Free version of Jellyfish.
What other advice do I have?
Putting information into Jellyfish and tracking it was easy, because I think the integrations worked really well. The problem was process-wise: keeping things updated in order to take more advantage of the features. For example, for DevEx, if you want to understand whether a capability is being used, such as Code Reviews or cycle times inside the Developer Experience, you need to be more granular and have specific metrics to feed Jellyfish. At that moment, we were not mature enough for this.
My overall score for Jellyfish is a Seven out of 10. In my desire, it would be a Nine or even higher, but I gave a Seven because I could not manage to test and use all the features I wanted to. The ones I used were cool. I think a Seven is a good score for this.
Great Cross-Platform Data Consolidation
Secondly, in some weeks we’re more involved in refinement and architecture/design discussions rather than commits and coding, and it doesn’t consider that either.