Agile Hive does not take anything away from you or limit you, on the contrary, you retain full flexibility. You can adapt all Issue Types, Workflows and Screens to your needs. You should only use a few Agile Hive fields here and there - that's it. Let's take a closer look.
General: If you delete an unused Agile Hive scheme, it is deleted for the time being. However, if an Agile Hive project is created via Create Project, Agile Hive automatically creates all missing schemes again.
Issue Types
The following applies to all Agile Hive projects and their issue types:
- Every Issue Type is optional
- Add as many Issue Types to every Agile Hive Scheme as you want
- The user can rename every Issue Type
- The user can remove every Issue Type from the Agile Hive Schemes
- The user can change the icon of every Issue Type
- The user can delete every Issue Type
- If you haven’t deleted the Issue Type Objective or Risk and you want to use Objective or Risk again, simply create new issue types with the name ‘Objective’ or ‘Risk’ and Agile Hive automatically uses them
- Only the Issue Types Objective & Risk are used for specific reports
Workflows
The following applies to all Agile Hive projects and their workflows:
- Use your own workflows or adapt those from Agile Hive. There are no restrictions.
Screens
The following applies to all Agile Hive projects and their screens:
- Adjust the screens according to your wishes. Add any fields & sort them as you like.
- We recommend keeping the Agile Hive fields in the various schemes in order to be able to view and edit important information directly in the issue.
Agile Hive Links
You can rename all Agile Hive Linktypes and their directions.
| Issue Types | Note | |
|---|---|---|
| Existing issue types are used by Agile Hive and are not created or changed additionally, except the Milestone Icon. Existing issue type icons, for example, would remain. | |
| Issue Type Schemes | ||
| Agile Hive - Team - Issue Type Scheme |
| |
| Agile Hive - ART - Issue Type Scheme |
| |
| Agile Hive - Solution Train - Issue Type Scheme |
| |
| Agile Hive - Portfolio - Issue Type Scheme |
| |
| Workflows | ||
| Agile Hive - Improvement Workflow | ||
| Agile Hive - Solution Train Workflow | ||
| Agile Hive - Portfolio Workflow | ||
| Agile Hive - ART Workflow | ||
| Agile Hive - Risk Workflow | ||
| Agile Hive - Team Workflow | ||
| Workflow Schemes | ||
| Agile Hive - Team Workflow Scheme | ||
| Agile Hive - ART Workflow Scheme | ||
| Agile Hive - Solution Train Workflow Scheme | ||
| Agile Hive - Portfolio Workflow Scheme | ||
| Screens | ||
| Agile Hive - Impediment Screen | ||
| Agile Hive - Improvement Screen | ||
| Agile Hive - Solution Train - Objective Screen | ||
| Agile Hive - Solution Train Screen | ||
| Agile Hive - Portfolio Screen | ||
| Agile Hive - Strategic Theme Screen | ||
| Agile Hive - ART - Objective Screen | ||
| Agile Hive - ART Screen | ||
| Agile Hive - Risk Screen | ||
| Agile Hive - Team - Bug Screen | ||
| Agile Hive - Team - Objective Screen | ||
| Agile Hive - Team - Subtask Screen | ||
| Agile Hive - Team Screen | ||
| Screen Schemes | ||
| Agile Hive - Impediment - Screen Scheme | ||
| Agile Hive - Improvement - Screen Scheme | ||
| Agile Hive - Solution Train - Objective Screen Scheme | ||
| Agile Hive - Solution Train - Screen Scheme | ||
| Agile Hive - Portfolio - Screen Scheme | ||
| Agile Hive - Strategic Theme Screen Scheme | ||
| Agile Hive - ART - Objective Screen Scheme | ||
| Agile Hive - ART - Screen Scheme | ||
| Agile Hive - Risk - Screen Scheme | ||
| Agile Hive - Team - Bug Screen Scheme | ||
| Agile Hive - Team - Objective Screen Scheme | ||
| Agile Hive - Team - Screen Scheme | ||
| Agile Hive - Team - Subtask Screen Scheme | ||
| Issue Type Screen Schemes | ||
| Agile Hive - Portfolio - Issue Type Screen Scheme | ||
| Agile Hive - Solution Train - Issue Type Screen Scheme | ||
| Agile Hive - ART - Issue Type Screen Scheme | ||
| Agile Hive - Team - Issue Type Screen Scheme | ||
| Custom Fields | ||
Actual Business Value | ||
Cost of Delay | ||
Epic Owner | ||
Exposure | ||
Impact | ||
Job Size | ||
Plan Business Value | ||
| Planned Start Date | ||
| Planned End Date | ||
| Probability | ||
Planning Interval | ||
RROE | ||
Residual Exposure | ||
Residual Impact | ||
Residual Probability | ||
Teams Involved | ||
Time Criticality | ||
Uncommitted Objective | ||
User-business Value | ||
WSJF | ||
| Milestone Date | ||
| EPP-Epic-Color | ||
| Issue Linking | ||
| Agile Hive Dependency Link | requires / is required by | |
| Agile Hive Link | Child of / Parent of | |
| Agile Hive Objective Link | Belongs to Objective / Is Objective of | |
| Agile Hive Risk Link | Treats / Is treated by | |
| Agile Hive Strategic Theme Link | Belongs to Theme / Is Theme Of | |
| Statuses | Category | |
| Owned | IN PROGRESS | |
| Mitigated | IN PROGRESS | |
| Assigned | IN PROGRESS | |
| In Review | IN PROGRESS | |
| Try | IN PROGRESS | |
| Keep | IN PROGRESS | |
| Implementation | IN PROGRESS | |
| Analysis | TO DO | |
| Funnel | TO DO | |
| Validating on Staging | IN PROGRESS | |
| Deploying to Production | IN PROGRESS | |
| Releasing | IN PROGRESS | |
| ART Backlog | IN PROGRESS | |
| Solution Train Backlog | IN PROGRESS | |
| Portfolio Backlog | TO DO | |
| Review (Portfolio) | TO DO | |
| MVP | IN PROGRESS | |
| Persevere | IN PROGRESS | |
| Project Templates | ||
| SAFe Scrum-Team Project | ||
| SAFe Kanban-Team Project | ||
| SAFe ART Project | ||
| SAFe Solution Train Project | ||
| SAFe Portfolio Project |
