Introduction

Agile Hive comes with predefined statuses for workflows in projects on all SAFe® layers. To easily make your Jira projects SAFe®-friendly, you will need to add the statuses provided by Agile Hive as they adhere to the official framework methodology.

Prerequisites

Make sure you’re logged in with a Jira user holding at least Jira Administrator permission.

Overview of Agile Hive Statuses

Agile Hive comes with the work types listed below for the respective status categories.

todo Status Category

Analysis - The Analysis status represents work items that are in a very early stage, where the team analyzes, defines, and refines the backlog items to prepare them for prioritization and further development.

Funnel - The Funnel status represents work items that are identified and captured as potential business opportunities. They are not yet prioritized, and no resources have been allocated for further analysis or development.

Portfolio Backlog - The Portfolio Backlog status represents work items that have been identified as potential initiatives that could deliver significant business value. They have been prioritized, but no resources have been allocated for further development.

ART Backlog - The ART Backlog status represents work items that have been prioritized and allocated resources for further analysis, design, and development. They are ready for the next level of refinement and planning.

Solution Train Backlog - The Solution Train Backlog status represents work items that have been identified as potential topics that could deliver significant value. They have been prioritized, but no resources have been allocated for further analysis or development.

Review (Portfolio) - The Review (Portfolio) status represents work items that have completed the analysis, design, and planning stages. They are ready for review and prioritization.

in progress Status Category

Owned - The Owned status represents risk items that are assigned to a specific team member, and they are managing them actively.

Mitigated - The Mitigated status represents work items that have identified risks, and the team has taken actions to mitigate them.

Accepted - The Accepted status represents a risk that cannot be resolved, so it must be accepted as-is and dealt with as necessary.

In Review - The In Review status represents work items that have completed development and are being reviewed for quality assurance and adherence to standards.

Try - The Try status represents improvements that are tried out in the team as part of experiments and retained if successful.

Keep - The Keep status represents improvements that the team has successfully tried out and is currently implementing on a long-term basis.

Implementation - The Implementation status represents work items that are in the process of being developed and implemented.

Validating on Staging - The item is currently being tested on a staging environment to ensure that it works as expected before being deployed to production.

Deploying to Production - The item is in the process of being deployed to the production environment.

Releasing - The item is being prepared for release to the end users or customers.

MVP - The item is currently being developed as part of the Minimum Viable Product (MVP) to test and validate the product or feature.

Persevere - The Persevere status represents work items that will continue to be pursued after MVP implementation, as additional value can be created for the customer.

Create Agile Hive Statuses

Navigate to the ‘Apps’ section of global Jira Administration:

Open

Select ‘Agile Hive Administration’ from the left hand sidebar and navigate to the ‘Statuses’ tab.

Since Agile Hive does not automatically generate any Jira entities in your site, you have to explicitly tell the app to generate the built-in statuses. Click the ‘Create Statuses’ button in order to generate all of the statuses in your Jira site.

You will then receive a notification that the statuses were created and the status for each status category should be updated from missing to ready.

Troubleshooting

In case one or more statuses cannot be created please make sure that no other status with the same name already exists in your Jira site.