Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Current »

Introduction

Agile Hive allows for a flexible configuration when it comes to adding projects to the app. You can either use existing projects (and issues) or create new projects and configure them for use with Agile Hive.

Prerequisites

In general, with Agile Hive you’re able to keep using your already existing Jira projects.

However, there are some limitations in place regarding some project types and categories that are not (yet) compatible with Agile Hive:

  • Team-managed projects

  • Service Management projects

  • Product Discovery projects

Recommendations

Agile Hive comes with a predefined set of Issue Types, Issue Type Schemes, Workflows, Screens, Screen Schemes, and other templates to enable administrators to quickly prepare a large number of projects for being used with the app. Also, the templates provided can be used for a quick start by creating new projects dedicated for use within Agile Hive.

If you’re a Jira Administrator, please refer to our documentation on Agile Hive’s built-in templates and schemes that can be created during the initial app setup.

Please note, that there is no obligation to use any of the templates and schemes provided with Agile Hive for your projects. You can still stick to your established workflows, issue types, and project configurations. However, some features of Agile Hive require specific entities (e.g., Custom Fields) to be available in order to provide full functionality.

Minimum Required Project Configuration

You can find more information on the minimum required project configuration for each of the SAFe® levels of Agile Hive in the following sections.

All Custom Fields mentioned below are being shipped with Agile Hive. Please refer to Manage Agile Hive Custom Fields for a comprehensive list of fields included with the app.

Reminder: Make sure to assign the correct Issue Type Screen Scheme with all projects added to Agile Hive.

Please note that the fields listed below only represent the minimum required configuration. You can still configure more Custom Fields for any Screen associated with projects added to Agile Hive.

Portfolio Level

On the Portfolio level we strongly recommend to use company-managed projects created from the Kanban template.

Agile Hive provides functionality to projects on the Portfolio level that can be mapped to a dedicated issue type:

  • Milestones

In order to utilize the full featureset Agile Hive provides for projects on Portfolio level, make sure to provide at least the fields listed below with dedicated Screens for each of the issue types:

  • Portfolio Epic / Enabler: User Business Value, RROE, Time Criticality, Job Size, WSJF Value

  • Milestone: Milestone Date

Large Solution Level

On the Large Solution level we strongly recommend to use company-managed projects created from the Kanban template.

Agile Hive provides functionality to projects on the Large Solution level that can be mapped to a dedicated issue type:

  • Risks

  • Objectives

  • Milestones

In order to utilize the full featureset Agile Hive provides for projects on Large Solution level, make sure to provide at least the fields listed below with dedicated Screens for each of the issue types:

  • Capability / Enabler: User Business Value, RROE, Time Criticality, Job Size, WSJF Value

  • Risk: Impact, Probability, Exposure, Residual Impact, Residual Probability, Residual Exposure, Assigned PIs

  • Objective: Uncommitted Objective, Assigned PIs

  • Milestone: Milestone Date

ART Level

On the ART level we strongly recommend to use company-managed projects created from the Kanban template.

Agile Hive provides functionality to projects on the ART level that can be mapped to a dedicated issue type:

  • Risks

  • Objectives

  • Milestones

In order to utilize the full featureset Agile Hive provides for projects on ART level, make sure to provide at least the fields listed below with dedicated Screens for each of the issue types:

  • Feature / Enabler: PI Involvement, Owning Team, Teams Involved, User Business Value, RROE, Time Criticality, Job Size, WSJF Value

  • Risk: Impact, Probability, Exposure, Residual Impact, Residual Probability, Residual Exposure, Assigned PIs

  • Objective: Uncommitted Objective, Assigned PIs

  • Milestone: Milestone Date

Team Level

On the Team level Agile Hive supports company-managed projects created from one of the following templates:

  • Scrum

  • Kanban

Agile Hive provides functionality to projects on the Team level that can be mapped to a dedicated issue type:

  • Risks

  • Objectives

  • Milestones

In order to utilize the full featureset Agile Hive provides for projects on Team level, make sure to provide at least the fields listed below with dedicated Screens for each of the issue types:

  • Story: Story Points, Sprint, PI Involvement

  • Risk: Impact, Probability, Exposure, Residual Impact, Residual Probability, Residual Exposure, Assigned PIs

  • Objective: Plan Business Value, Actual Business Value, Uncommitted Objective, Assigned PIs

  • Milestone: Milestone Date

  • Sub-Task: No specific requirements

Link to this page: https://seibert.biz/ahc-prepareprojects

  • No labels