Oobeya
OobeyaReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
31 reviews
from
External reviews are not included in the AWS star rating for the product.
Bringing Build and Delivery Data Together with Bitbucket and Jenkins
What do you like best about the product?
The Bitbucket and Jenkins integrations worked without much setup, and now we can see commit activity, build status, and deployment trends in one place. That visibility has helped us better understand the full delivery pipeline—from code to production.
What do you dislike about the product?
It would be helpful to have more detailed drill-downs on failed builds, but for high-level tracking and trends, it does the job well.
What problems is the product solving and how is that benefiting you?
It’s allowed us to connect engineering activity with delivery outcomes. We’re spotting bottlenecks earlier—whether in code reviews or build failures—and making more informed decisions during retros and planning sessions.
Smooth Integration with Azure DevOps, Valuable Insights Out of the Box
What do you like best about the product?
The Azure DevOps integration was straightforward, and once connected, we immediately started getting value—pull request metrics, DORA stats, work breakdowns. It’s helped make our delivery data more transparent and easier to discuss across teams.
What do you dislike about the product?
Some advanced filtering could be improved, especially when looking across multiple projects, but the essentials are already well-covered.
What problems is the product solving and how is that benefiting you?
We’ve gone from scattered reports and spreadsheets to a single place where we can track delivery, quality, and team activity. It’s been especially helpful for surfacing patterns and creating alignment across engineering and product.
Great product for development productivity
What do you like best about the product?
Oobeya helps us look at productivity beyond velocity or ticket counts. By combining delivery metrics with signals like review times, churn, and scope change, we get a more balanced view of how teams are working—not just how fast they’re shipping.
What do you dislike about the product?
There’s a bit of a learning curve in interpreting some of the metrics meaningfully, but once you align on definitions internally, it becomes very effective.
What problems is the product solving and how is that benefiting you?
It’s given us a way to track productivity that supports healthy teams and sustainable pace. We’re able to spot when people are stretched thin or when delivery is slowing for structural reasons, not just individual output.
Bringing Structure to How We Use Jira Data
What do you like best about the product?
We’ve been using Jira for years, but Oobeya helped us actually make sense of the data. Things like cycle time, issue churn, and work breakdown by type became much easier to interpret once visualized properly. It’s made our planning and retros much more grounded in reality.
What do you dislike about the product?
Some of our custom Jira workflows needed a bit of adjustment to display correctly, but once configured, everything synced smoothly.
What problems is the product solving and how is that benefiting you?
Oobeya surfaces patterns we couldn’t easily spot in Jira alone. It’s helped us identify bottlenecks, scope creep, and under-planned sprints, leading to more predictable delivery and clearer team discussions.
A Practical Way to Spot Early Delivery Risks
What do you like best about the product?
The Symptoms feature has been genuinely useful. It highlights signals we might otherwise miss—like rising review times, shifting priorities, or inconsistent delivery. These aren’t always obvious day to day, but having them flagged in context helps us respond earlier and have better conversations with teams.
What do you dislike about the product?
Some symptoms could benefit from more team-specific context, but they still serve as a helpful starting point for investigation.
What problems is the product solving and how is that benefiting you?
It gives us a structured way to monitor delivery health without relying solely on intuition. The result has been fewer surprises in planning and more timely course correction when things start to drift.
Reliable Visibility into DORA Metrics
What do you like best about the product?
Oobeya gives us a clear and automated view of key DORA metrics. It’s helped us move away from manual tracking and made it easier to have data-informed discussions about engineering performance across teams.
What do you dislike about the product?
There are a few areas where more customization could add value, but overall the platform covers our core needs well.
What problems is the product solving and how is that benefiting you?
We’re using Oobeya to track delivery performance in a consistent and structured way. It’s improved visibility across teams and made it easier to identify where we need to focus attention.
Oobeya Gives Us Actionable Insights from GitHub Activity
What do you like best about the product?
The GitHub integration worked out of the box and immediately started surfacing valuable insights—like PR cycle times, review coverage, and weekend activity. It’s helped us improve our code review process and identify patterns we would’ve missed otherwise.
What do you dislike about the product?
No real complaints. It’s been smooth so far, and the team seems to roll out improvements regularly.
What problems is the product solving and how is that benefiting you?
Oobeya helps us make sense of GitHub data without having to build custom dashboards. We’ve used it to optimize team workflows, improve feedback loops, and strengthen our engineering delivery process overall.
Oobeya Brings Clarity to Engineering Workflows
What do you like best about the product?
Oobeya’s Jira integration gave us immediate insight into how work moves through our system. We can now spot delays, track delivery speed, and understand where teams are spending their time—all without digging through tickets manually. It’s been a big win for both visibility and efficiency.
What do you dislike about the product?
Nothing major—it's been reliable and easy to use. Some fine-tuning options for dashboards would be a nice future improvement.
What problems is the product solving and how is that benefiting you?
We use Oobeya to make our delivery process transparent and measurable. It’s helped us identify bottlenecks, improve planning accuracy, and create better alignment between product and engineering.
Oobeya Helps Us Connect Engineering Metrics to Outcomes
What do you like best about the product?
The Sonar integration has been especially valuable—code quality trends are now visible alongside delivery metrics. We can easily identify when velocity comes at the cost of maintainability and adjust accordingly. It’s helped us build a more balanced and accountable engineering culture.
What do you dislike about the product?
Nothing critical so far. The platform has been intuitive and continues to improve with regular updates.
What problems is the product solving and how is that benefiting you?
Oobeya brings together multiple data sources to give us a complete view of engineering performance. It’s helped us detect quality risks early, align teams with strategic goals, and have more meaningful conversations about progress and priorities.
Oobeya Turns Azure DevOps Data into Strategic Insights
What do you like best about the product?
The Azure DevOps integration was seamless and gave us instant visibility into our delivery pipeline. We can now track work types, lead times, and bottlenecks without manual effort. It’s helped us align engineering work with company goals and bring more structure to how we measure success.
What do you dislike about the product?
So far, it’s covered our needs well. There are a few areas we’re excited to see evolve further, but nothing that’s held us back.
What problems is the product solving and how is that benefiting you?
We’re using Oobeya to extract real value from our Azure DevOps data. It’s improved our sprint planning, helped surface inefficiencies, and given leadership a much clearer view of what engineering is focused on. Communication with stakeholders is now more grounded in actual metrics.
showing 1 - 10