Hivel
HivelReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
115 reviews
from
External reviews are not included in the AWS star rating for the product.
Rich Development Metrics at Your Fingertips
What do you like best about the product?
It can give you all kind of metric that is involved in development
What do you dislike about the product?
Some flexibility to get report on repo level
What problems is the product solving and how is that benefiting you?
It can give you all kind of metric that is involved in development
Improving Productivity with Hivel
What do you like best about the product?
Hivel offers a good set of features that make managing our work more efficient. The platform is user-friendly, reliable, and helps streamline processes. I also appreciate the reliability and the quality of support provided by Hivel. The team is responsive, professional, and always willing to assist when needed.
What do you dislike about the product?
One limitation is that some advanced features or customization options are currently limited. Expanding these capabilities would make the platform even more powerful for different use cases.
What problems is the product solving and how is that benefiting you?
Hivel helps simplify our processes by providing the tools needed to manage and monitor work in one place. This reduces manual effort and helps the team stay organized, ultimately saving time and improving productivity.
Data Visibility Enhanced, Room for Performance Improvement
What do you like best about the product?
I appreciate the data-first approach of Hivel, which I find really interesting. It's very focused on data, and the fine-grained views we get are fairly good. I am a big user of the main dashboards, where we can see metrics like code time, code velocity, and lines of code, which are core to our needs. The new tool that shows how much code was written is also exciting.
What do you dislike about the product?
I think, to be honest, the performance of the website itself can be a bit here and there. I'd love to have a much more, you know, better performing website in general. That is something which can be improved. But that is not something I cannot live with right now.
What problems is the product solving and how is that benefiting you?
I use Hivel to enhance data visibility, allowing us to objectively measure developer productivity and contributions at a team and individual level. It provides insights into code quality, code reviews, and AI adoption, which are crucial for managing our large engineering team.
Essential for Understanding Engineering Metrics
What do you like best about the product?
I like using Hivel for understanding engineering metrics for the team. The cycle time and the correlation between JIRA and check-ins are standout features for me. They help me better understand why certain tasks take more time than estimates. The initial setup of Hivel was fairly straightforward.
What do you dislike about the product?
Flexibility to configure rules/exceptions to get more meaningful metrics
What problems is the product solving and how is that benefiting you?
I use Hivel to understand engineering metrics, identify areas for team improvement, and determine why tasks exceed time estimates.
From Anarchy to Data: How Hivel Gave Our Dev Productivity Real Metrics
What do you like best about the product?
Ease of Implementation & Integration: Hivel’s intuitive design minimized onboarding friction. Crucially, its integrations with GitHub, Bitbucket, Jenkins and JIRA were a game-changer. This ease of integration automatically creates a vital link between JIRA tickets and PRs, providing objective, auto-populated data for tracking DORA metrics like CFR, MTTR, Lead Time and Deployment Frequency.
Ease of Use Drives Adoption: The clean, uncluttered interface is a major factor in Hivel's success. This directly correlates to a high frequency of use; it's not a tool they are forced to use, but their natural daily hub for productivity metrics tracking.
Responsive Customer Support: During the implementation phase and beyond, the customer support has been exemplary. They are responsive, knowledgeable, and have acted on our feature suggestions, making us feel like a true partner.
Ease of Use Drives Adoption: The clean, uncluttered interface is a major factor in Hivel's success. This directly correlates to a high frequency of use; it's not a tool they are forced to use, but their natural daily hub for productivity metrics tracking.
Responsive Customer Support: During the implementation phase and beyond, the customer support has been exemplary. They are responsive, knowledgeable, and have acted on our feature suggestions, making us feel like a true partner.
What do you dislike about the product?
Non-Configurable Workflow Rules: The platform lacks the granularity to adapt to our development workflows.
Gaps in User Activity and Data Consistency: We have encountered ongoing issues where contributor activity data is missing or incomplete for certain team members.
Gaps in User Activity and Data Consistency: We have encountered ongoing issues where contributor activity data is missing or incomplete for certain team members.
What problems is the product solving and how is that benefiting you?
1. Problem: Disconnected Tool Sprawl & Context Switching
Before Hivel: Our development workflow was fragmented across multiple specialized tools. This caused lack of a single source of truth.
How Hivel Solves It: Hivel acts as a unified "Command Center" that consolidates project management, task tracking, and critically code integration into a single platform.
As a TPM, I can see the entire story from the initial task and time spent to the specific code commits and PRs in one place.
2. Problem: Anecdotal vs. Data-Driven Decision Making
Before Hivel: Our understanding of team velocity, and developer productivity was often based on manual Jira reports, spreadsheets, and stand-up updates. This was time-consuming, prone to error, and often subjective.
How Hivel Solves It: Hivel automates the collection of key engineering metrics by directly integrating with our Git repositories. It automatically links development activity (commits, PRs) to JIRA tickets, providing objective data on metrics like lead time, deployment frequency, and cycle time.
I can now move from asking "How is the project going?" to presenting data that shows, "Here is our lead time for the last sprint, and here is the trend." This shifts conversations from blame to improvement.
Before Hivel: Our development workflow was fragmented across multiple specialized tools. This caused lack of a single source of truth.
How Hivel Solves It: Hivel acts as a unified "Command Center" that consolidates project management, task tracking, and critically code integration into a single platform.
As a TPM, I can see the entire story from the initial task and time spent to the specific code commits and PRs in one place.
2. Problem: Anecdotal vs. Data-Driven Decision Making
Before Hivel: Our understanding of team velocity, and developer productivity was often based on manual Jira reports, spreadsheets, and stand-up updates. This was time-consuming, prone to error, and often subjective.
How Hivel Solves It: Hivel automates the collection of key engineering metrics by directly integrating with our Git repositories. It automatically links development activity (commits, PRs) to JIRA tickets, providing objective data on metrics like lead time, deployment frequency, and cycle time.
I can now move from asking "How is the project going?" to presenting data that shows, "Here is our lead time for the last sprint, and here is the trend." This shifts conversations from blame to improvement.
Outstanding Products That Exceed Expectations
What do you like best about the product?
Everything. The products are very good..
What do you dislike about the product?
Nothing. Everything is good and with each thing they are improving.
What problems is the product solving and how is that benefiting you?
It helps us identify where delivery slows down- whether it's in reviews, rework, or unclear specs. We now catch inefficiencies early instead of after the sprint ends.
Intuitive Task Management with Some Room for Improvement
What do you like best about the product?
I love using Hivel for its clean, fast, and super intuitive user interface which significantly reduces mental overload. The simplicity and productivity focus of Hivel mean I experience no app hopping, ensuring zero missed tasks. It aids in managing my work effectively, enhancing my productivity, and keeping me organized with its task management capabilities, reminders, and work planners. Hivel's emphasis on efficiency ensures that my routine runs smoothly without the wastage of resources, making it a key tool in my professional toolkit. The straightforward and easy setup adds to its value, allowing me to integrate it seamlessly into my daily operations.
What do you dislike about the product?
I find the limited customization options and lack of offline mode in Hivel quite challenging. These aspects restrict the flexibility and adaptability I expect in a productivity tool.
What problems is the product solving and how is that benefiting you?
I use Hivel for task management, reminders, and work planning, which simplifies juggling multiple tasks and deadlines. Its clean and intuitive UI enhances productivity by reducing mental overload and eliminating missed tasks.
Streamlines Bottleneck Identification, Needs Better Customization & GitHub co-pilot tracking
What do you like best about the product?
I find Hivel incredibly valuable for tracking team metrics related to GIT and Jira usage, as it helps to identify bottlenecks in our processes and boost developer productivity by addressing issues early. I love how easy it is to use, making it accessible for my entire team. The integrations with Jira and Git are particularly beneficial, as they play a critical role in identifying process bottlenecks swiftly. Additionally, the initial setup of Hivel was very straightforward, with significant support from Hivel’s team, which made the onboarding process smoother.
What do you dislike about the product?
I find the ability to build custom dashboards in Hivel to be fairly limited. I would like to see improvements in the platform's functionality to allow adding sections in dashboards for better grouping of KPIs and the ability to reorder KPI widgets for enhanced customization. Also, the GITHUB CoPilot integration is extremely limited.
What problems is the product solving and how is that benefiting you?
I use Hivel to track team metrics for Git and Jira, identifying process bottlenecks to boost developer productivity. It's easy to use and integrates well with Jira and Git, helping us solve issues early.
Hivel Supercharged Our Team’s Performance and Code Quality
What do you like best about the product?
I’ve been using Hivel for about a year, and over the past few months we’ve started exploring it more deeply. I began setting clear goals for my team and tracking actionable insights using the Git metrics. The results have been remarkable our throughput and code quality have significantly improved.
I’m an active user of the Goals module and several Git-metric tracking features. Hivel genuinely feels like a superpower for me as an Engineering Manager.
Hivel offers a wide range of powerful features that are extremely easy to use and highly intuitive. Their product support is exceptional. I’ve never had to wait more than 24 hours for a response.
Whenever I’ve faced an issue, the team has been quick to jump on a call and help resolve it immediately. Truly impressive support.
I’m an active user of the Goals module and several Git-metric tracking features. Hivel genuinely feels like a superpower for me as an Engineering Manager.
Hivel offers a wide range of powerful features that are extremely easy to use and highly intuitive. Their product support is exceptional. I’ve never had to wait more than 24 hours for a response.
Whenever I’ve faced an issue, the team has been quick to jump on a call and help resolve it immediately. Truly impressive support.
What do you dislike about the product?
I’m currently using the older version of Goals (not Goals Pro). In this version, goals are tracked in days and hours, but the exported reports show values in minutes, which makes it difficult to quickly identify which items met the goals and which didn’t. I often have to do additional manual calculations to interpret the data. I’m not sure if this issue is resolved in the new Goals Pro version.
What problems is the product solving and how is that benefiting you?
Hivel helps me set clear goals for my team and track actionable Git metrics, which has significantly improved our throughput and code quality. The Goals module and Git-metric insights give me better visibility into team performance, enabling more informed decisions. Additionally, the intuitive features and outstanding product support make it easier to resolve issues quickly, further enhancing team efficiency.
Intuitive Dashboards with Powerful Code Review Tools
What do you like best about the product?
I find Hivel incredibly helpful for tracking code review metrics and understanding the improvement in code quality over time. It offers me insightful dashboards that clearly show which employees are actively participating in code reviews and pushing changes as expected. This feature helps me ensure the team stays engaged and productive. More so, Hivel provides valuable analysis, allowing me to detect if team members are spending too much time on reworks, highlighting areas where code quality may need improvement. The AI-enabled code reviews are particularly impressive; while they may not always be flawless, they have proven to be a standout feature by offering firsthand reviews of PRs. This helps in giving constructive feedback to the team, either to encourage improvement where needed or to acknowledge exemplary performance. The overall setup and navigation of Hivel was also straightforward and intuitive, which made the onboarding process smooth for my team.
What do you dislike about the product?
So in some cases, like, when I want to compare employees, it just gives us a few metrics, and I'm not able to, in general, use Hivel to compare different employees or all the members in the team. The graph just lets us choose a couple of metrics, and that is something I don't really understand well. So it may be something that I don't understand well, but, yeah, that I'm not able to use efficiently to give feedback to my team.
What problems is the product solving and how is that benefiting you?
I use Hivel to track and analyze code review metrics, improve code quality, and ensure team participation, allowing for better feedback and appreciation. It highlights rework issues and PR sanities, aiding in understanding team activities and contributions.
showing 1 - 10