...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Introduction
Until now, in order to add a swimlane for an ART-level Feature to a Team Planning Board, at least one of the following two conditions must be met:
...
The ART roadmap is typically planned around three months in advance, meaning that Features included there may not always appear in the final prioritized list of Features before the PI Planning event.
A Feature planned in the ART roadmap for a PI automatically appears on the Team Planning Boards of all Teams within that ART, resulting in a cluttered board with an excessive number of Feature swimlanes for most Teams.
As a workaround to ensure that only the Teams contributing to a Feature have a swimlane for it on their board, Teams are required to create candidate stories upfront. However, this process is not straightforward and comes with a lot of potential pitfalls.
The new way of planning
...
To address the challenges outlined above, we will introduce a new method for adding ART-level Features to Team Planning Boards for selected PIs.
...
The Team has at least one issue planned for the selected PI that is hierarchically linked to the ART-level Feature.Status title no change
The ART-level Feature includes the fields 'Assigned Teams' and 'Assigned PIs', which are set to align with the respective parameters of the currently displayed Team Planning Board.Status colour Green title new
Transitioning from the old to the new way of planning
Once the new version of Agile Hive, which includes the 'Assigned Teams' Custom Field, is installed, a Jira Administrator must update the Screen used by ART-level projects in Agile Hive to incorporate this new field.
...