Jellyfish v.
Pluralsight Flow
Pluralsight Flow, surfaces git metrics into pretty dashboards to inform teams on engineering metrics. However as the needs and expectations of contemporary engineering organizations have evolved over the years Pluralsight Flow has not kept up.
Code insight without context
Pluralsight Flow focuses a lot on metrics on developer activity and collaboration, but not much on process, workflows, or delivery. In other words, Flow measures outputs and not on outcomes. They have invested a lot in code-level management and productivity measurement of engineering teams, which we believe are much lower leverage for improving engineering performance than measuring process, delivery, and resource investment.
Real data science
Our patented work model boasts analysis that factors in data from sources across engineering touchpoints; not relying solely on issue counts or story points to infer work events.
Tailored insights
Jellyfish adapts to your team’s work; accounts imperfect processes, immature hygiene, issues at scale. We bring our platform to your engineering practices, not the other way around.
Predictive analytics
Enable proactive planning and decision making for the future; not only a retrospective look at what’s happened. Leverage your data to intelligently infer future work momentum and completion.
The Breakdown