Item: Agile Hive - SAFe in Jira
Rating: 9
Author: Franz Seher

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 and Cons

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.

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.

Most Important Features

Roadmapping
Dependencies
Transparency
Various layers
Jira Integration

Return on Investment

More transparency.
Better product decisions.
Saving time and resources.
Less critical dependencies.

Key Insights

Do you think Agile Hive - SAFe in Jira delivers good value for the price?

Yes

Are you happy with Agile Hive - SAFe in Jira's feature set?

Yes

Did Agile Hive - SAFe in Jira live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Agile Hive - SAFe in Jira go as expected?

I wasn't involved with the implementation phase

Would you buy Agile Hive - SAFe in Jira again?

Yes

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.

Make product planning transparent and fun

Overall Satisfaction with Agile Hive - SAFe in Jira