Agile Hive Reviews and Ratings

Rating: 7.3 out of 10

Score

7.3 out of 10

Community insights

TrustRadius Insights for Agile Hive are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Fully integrated with Jira: Users have found Agile Hive-Safe to be fully integrated with Jira, allowing them to leverage all the benefits of Jira such as issue tracking, project management, and reporting. This integration has been highly appreciated by multiple reviewers for its seamless functionality.

Better way to implement scaling: Several users liked that Agile Hive-Safe provides a better way to implement scaling with increasing teams. They have found it helpful in managing tasks effectively and providing perfect insights into work progress, making it a valuable tool for teams working on larger projects.

Simple setup and support assistance: The simple setup process and the support assistance provided by Agile Hive-Safe have been greatly appreciated by reviewers. This positive feedback highlights the ease of getting started with the software and the helpfulness of the support team in addressing any queries or issues that may arise.

Reviews

4 Reviews

Agile Hive makes your PI planning less chaotic

Rating: 7 out of 10

Incentivized

January 7, 2025

Use Cases and Deployment Scope

Agile Hive is used for our value train within a SAFe setup. Every quarter we organize a so-called Product Increment (PI) Planning, where we plan all Features and Enablers in Agile Hive. Based on the priority of the Product Manager all teams plan their Features and Enablers accordingly to the sprints that are determined by the Release Train Engineer and set up in Agile Hive. The teams then create User Stories and estimate them and based on their sprint velocity (defined in Agile Hive) Product Owners can see how many Features and Enablers are realistic in one quarter (Product Increment). Further, dependencies across teams can be defined and made visible in Agile Hive, so that the plan is feasible. Without Agile Hive it would be hard or impossible to plan across several teams within a value train and to manage all dependencies. Additionally, with Agile Hive the plan is more realistic, so what can be achieved within one quarter in product development.

Pros

manage & visualize dependencies across teams
visualize capacity within a time frame
show priorities and plan accordingly

Cons

it is not possible to plan if teams have different sprint length
zoom into one sprint and then also zoom out to have big picture
names of user stories are not good to read because of static big picture

Likelihood to Recommend

Agile Hive is used for our value train

within a SAFe setup. Every quarter we organize a so-called Product Increment

(PI) Planning, where we plan all Features and Enablers in Agile Hive.

Based on the priority of the Product Manager all teams plan their Features and

Enablers accordingly to the sprints that are determined by the Release Train

Engineer and set up in Agile Hive. The teams then create User Stories and

estimate them and based on their sprint velocity (defined in Agile Hive)

Product Owners can see how many Features and Enablers are realistic in one

quarter (Product Increment). Further, dependencies across teams can be defined

and made visible in Agile Hive, so that the plan is feasible. Without Agile

Hive it would be hard or impossible to plan across several teams within a value

train and to manage all dependencies. Additionally, with Agile Hive the plan is

more realistic, so what can be achieved within one quarter in product

development.

Verified User

Manager in Information Technology (10,001+ employees)

Vetted Review

2 years of experience

Efficient Tool For Scaled Agile Framework Implementation

Rating: 9 out of 10

Incentivized

June 30, 2022

Use Cases and Deployment Scope

We are using Agile Hive - SAFe in Jira to manage the project to simplify the implementation and the execution of Scaled Agile Framework. It is a great product by Atlassian. The core application is Enterprise Agile Planning for our project. Also, for the portfolio and resource loading within and inside the company and projects. Portfolio SAFe and Large Solution SAFe are the most used configuration in our case.

Pros

Scaled Agile Framework
Enterprise Agile Planning
API Capabilities
Customer Support
Setting up roadmaps

Cons

Probably UI but nothing else, it is already efficient in the purpose it should serve

Likelihood to Recommend

Daily activity management by using various kind of boards is very helpful to start the day with. Also, Backlog management is very good so it helps to keep track on the prioritized items. This can be used for all kind of Scrum activities by the Scrum master even for the Story management too. Also, it provides the required hierarchy levels, artifacts, boards, and workflows as an application in Jira. There is nothing to be shared as less appropriate while using SAFe.

Verified User

Team Lead in Information Technology (10,001+ employees)

Vetted Review

2 years of experience

Make product planning transparent and fun

Rating: 9 out of 10

Incentivized

May 17, 2022

Use Cases and Deployment Scope

As a product owner I use Agile Hive in a Scrum/Agile setup, but not SAFe. It is used for planning the product with the team for a specified amount of time. The most used case is roadmapping and visualizing dependencies in the team and across teams.

Pros

Roadmapping in terms of defining epics and planning them across a timeline and across teams.
Showing dependencies within teams and across teams and over time horizon.
Create transparency throughout the product organization and teams about what is planned.

Cons

Agile Hive - SAFE in Jira is heavily focused on SAFe, but it should be oriented around all other scaling Scrum frameworks.
Time horizon and iterations should be flexible.

Likelihood to Recommend

It can be used to make the agile planning process more transparent throughout all agile teams and the product organization. Roadmaps can be made visible very easily. The focus is on planning with multiple agile teams. It is not so beneficial if there is only one team. Dependencies of multiple teams can be made transparent to all relevant parties.

Franz Seher

Digital Product Owner @ Digital Strategy and Solutions in Information Technology at UNIQA Insurance Group AG (10,001+ employees)

Vetted Review

1 year of experience

View profile

My experience with Agile Hive - SAFe in Jira

Rating: 9 out of 10

Incentivized

April 26, 2022

Use Cases and Deployment Scope

The integration aspect has been very beneficial to have the work from Agile Hive - SAFe in Jira be interconnected in a fluent matter which allows artifacts/documentation, all sorts of processes and reports, and finally hierarchies to be integrated visually into Agile Hive - SAFe in Jira. This provides a shared mission and vision amongst all relevant stakeholders working towards the same goal but most importantly it drives alignment with other workstreams within the organization.

Pros

Team's progress.
Risk Management.
Visual representations - Dashboards.

Cons

I believe the training and support could be more hands on and easier.
The Agile Hive - SAFe in Jira product can be a bit robust to understand.
Having Knowledge transfer videos can help more than documentations.

Likelihood to Recommend

<ul><li>The dashboards available are great, they give great visibility on tracking/progress.</li><li>Seeing the team's progress and sprint progress with more details from different views is very helpful.</li><li>Being able to show the progress from the OKRs/Objectives representation in the same place is even better.</li><li>Managing risks within the same place is a project manager's dream and giving this visibility to the team to track and see what can potentially go wrong and how we can act before it happens is amazing.</li></ul>

Verified User

Manager in Information Technology (51-200 employees)

Vetted Review

1 year of experience

Loading Reviews List....

Home
,
Agile Development
,
Agile Hive
,
Reviews and Ratings

Agile Hive makes your PI planning less chaotic

Rating: 7 out of 10

Incentivized

January 7, 2025

Use Cases and Deployment Scope

Pros

manage & visualize dependencies across teams
visualize capacity within a time frame
show priorities and plan accordingly

Cons

it is not possible to plan if teams have different sprint length
zoom into one sprint and then also zoom out to have big picture
names of user stories are not good to read because of static big picture