Use the planning board

The planning board helps you plan the content of a release or several releases. It is typically used before a release starts, but you can also use it during the release to verify and adjust planning.

Overview

The planning board displays features according to their release or sprint, depending on the selection you made in the release/sprint context filter.

Use the planning board to:

  • Distribute features between releases, sprints, and teams to balance the work load
  • Remove features from a release/sprint
  • View dependencies between features and identify problematic dependencies

To access the planning board, select Backlog > Features, and then click the Board View button.

Select either Release Planning or Sprint Planning from the view options.

The planning board displays feature cards in release/sprint columns, depending on the view that you selected. If you selected to display a single release, the board will display sprint columns.

Features are displayed according to their target sprint. Features with no target sprint are displayed in the No sprint or No release columns.

Back to top

Move features between releases, sprints, or teams

You can distribute features between releases, sprints, and teams to load balance the work.

  1. Open the planning board in either the release or sprint view.
  2. To move features between teams, click the Group by button, and select Team.

  3. Drag and drop the features, as required.

    • Releases/sprints. The Target sprint of the feature changes accordingly. If you move a feature to the No sprint or No Release column, the Target sprint is cleared.
    • Teams. The Team field of the feature changes accordingly.

Back to top

Remove features from a release or sprint

To remove features from a release or a sprint, drag them to the No Release or No Sprint column, depending on your view.

The Target Sprint will be cleared automatically.

Note: To display the No Sprint column, select either the Show all or No Sprint options in the sprint context filter.

Back to top

View dependencies and identify problematic dependencies

Dependencies between features are reflected in the planning board. Features in a dependency relationship have a Dependencies exist icon on their card along with the number of dependencies the feature is involved in.

To see the dependencies on the board, click the Dependencies exist icon.

The following example shows the dependency relationships for feature 1015. Predecessors and successors are labeled.

Problematic dependencies are when the predecessor activity does not finish before its successor activity. For details on dependencies, see Create dependencies. In case of problematic dependencies, the Problematic dependencies exist icon appears.

Dependencies map

The dependencies map provides a comprehensive view of a feature's dependencies. While the Planning board is limited to the context of features and a specific sprint or release and displays only direct dependencies, the map displays all dependencies, regardless of the item type, sprint or release.

To open it, click the Dependencies exist icon to display the dependencies on the Planning board, and then click the dependencies map icon.

Map legend

Dependencies exist

Click to switch the focus to different items to see their dependencies.
Collapse a dependency branch.

 

The item has problematic dependencies.
Faded edge The branch of this dependency is not in focus.
Red edge The predecessor is problematic.

You can also add dependencies through the map. Select the item to which you want to add a predecessor, and then click the Add Predecessor button.

Note: When you add a predecessor to an item in the map, it does not automatically display potential issues. Click the refresh button to see problematic dependencies. This may take a few seconds.

Back to top

See also: