Skip to main content
#3 Team Boards
Updated today

Team Board Configuration Overview

  • Every Team participating in the PI session will have their own Team Board

  • The Sticky Notes that you will configure to originate on the Team Board thus are to be Team specific

  • All 4x Sticky functions/types are available to be configured on the Team Board

  • Teams can manage their Capacity Load + Allocation, Dependencies, Team Risks, Features (from the ART Backlog Board) and Team PI Objectives on the Team Board


Configuring Sticky Types for the Team Boards

Next you can find the general configuration options for Team Boards without having the PI Session synched with your ALM-tool.
Check out the additional options for configuration further below in case you want to synch your PI Session with your ALM-tool.

1

Sticky Type Name

Give your Sticky Type a name

2

Sticky Type Color

Choose a color for the Sticky Type

3

Select an appropriate Sticky Function

4

Configure onto which other Boards the Sticky Type can be mirrored (visualized)

5

Add Sticky Type

Add another Sticky Type

Mirror Sticky Notes

All Sticky Types that are configured on the Team Board will originate on this board. This is an important concept to master, it is referred to as the Origin Boards. For all Sticky Types configured on the Team Board, you can configure if Teams should be allowed to visualize (Mirror) the Sticky type on another Board via the Mirroring menu action.

Sticky notes that have the Dependency Sticky function, are by default set to be mirrored to the ART or Solution Planning Boards. We figure, that since [significant] dependencies involve cross-Team or cross-ART coordination, then they will typically need to be visualized (mirrored) onto the ART Planning Board for ART level stakeholders.

Dependency Sticky Note Function

The Dependency sticky function is a meta-sticky; it facilitates a very simple but powerful way to collaborate and align on a dependency between Teams. Dependency sticky types are not designed to sync to an ALM tool.

Visualize them on the ART Planning Board or Solution Planning Board by selecting the appropriate mirroring setting accordingly.

Team Board Lightning Round

Q: What types of Sticky Types need to originate on the #3 Team Board?

A: Team-level type Sticky Types like User Story, Enabler Story, Tech Debt/Maintenance, Task, Defect, etc. Basically those types of work items that appear in the team-level backlog.
Additionally, you can configure Sticky Types that are not synchronized and do not represent a work item but are helpful to facilitate your PI Planning and Execution. Examples: Note, Meet-After, Impediment, etc.

Q: What is the difference between the Sticky function: Work Item vs. Dependency vs. Risk vs. Note?

A: Distinguishing between the different Sticky functions is important as these different types of Sticky Notes provide slightly different behaviors to align to the activity that happens during the PI. For further details check out Sticky Note Types (Functions)

Q: Is it good practice to add other Sticky Types in addition to the default configuration in the screenshot above?

A: Yes, absolutely. We encourage you to rename Sticky Types, or add additional types of Sticky Notes to the Team Board configuration. For example, the team might want the ability to add a Sticky Type "Impediment" to facilitate throughout the PI:

  • Click the green button +Add a new Sticky Type, and name it Impediment

  • Select the appropriate color from the Color pallet or add in HTML color code

  • Select the Sticky function = Note (from the dropdown)

  • Optional: Select the ability to Mirror this Impediment Sticky Type to the ART Planning Board.

  • Click Save


Team Board Settings

Move Sticky Notes

Checkbox: Allow to move stickies between Team Boards; check this checkbox if you want Teams to have the ability to move Sticky Notes to other Team Boards.

Generally not recommended, especially if you have mature agile teams.

Load Warning and Capacity Limit Threshold

Iteration Load Warning Threshold: Set a percentage of capacity at which the board will indicate a warning by turning yellow, signaling that the load is nearing full capacity.

Iteration Capacity Limit Threshold: Define the percentage of capacity at which the board will turn red, indicating that the load has reached or exceeded the team's set capacity.


Impacts on the Team Board config with an ALM sync

When using an ALM Connection (Sync) in a PI Session, there will be some additional Settings for the Team Board.

Team Board Config with Jira Sync

Team Board Config with ADO Sync

Team Board Config with Rally Sync

Did this answer your question?