Before you can start with that you need to connect the piplanning app with your Jira instance: ALM Configuration
1. General Information
When creating a new PI Planning session in general information page, you can set the following fields.
|Start date of your PI Planning||The date when PI Planning will take place. Can be edited also after session is created. The date is then displayed in the PI planning app when selecting a session from session list.|
|Number of Iterations||max. 12|
|Duration of one Iteration in Days||This includes days on weekend. Based on the amount of days the dates under step 9 Iterations will be automatically filled in.|
Select your ALM Tool Connection
2. Add Teams (Boards)
Team Boards / Program Board Swimmlanes
While configuring a new session, you have to decide which teams will attend this session. You can do that by selecting either an ART or a Solution-Train.
Teams can only be added to a session during the session creation. You can not remove / add a team-(board) afterwards.
Selecting ART or ST
In the example of the screenshot we selected the ART "Animals" which consists of the teams listed under the ART-Name. All these teams will get their own team-board.
On this page you can:
- Delete or add teams out of other ARTs if needed
- Re-order the teams. The ordering is represented on the program-board
Attending Teams (without Board / Swimmlane)
You can add teams to a session without giving them an own board and swimmlane. This is useful for scenarios where you want to provide a Solution Level Board spanning multiple Programs. A team which is attending a session (but does not have its own Team Board in that session) can then join (see and edit) that session as well.
To add a team as a an attendee to a session:
- Go to step two in the session creation / edit session
- Click on the "Teams without boards" tab
- Add one or more teams
3. Team Boards
Configure Sticky Types for Team Boards
If you check the box, teams will be able to Move Stickies from one Team Board to another Team Board.
For the Sticky Types Configured on the Program Backlog Board and the Team Board (Origin Boards) you can configure if Teams should be allowed to visualize (Mirror) the Sticky Type on another Board.
Per default, Dependencies and Program Backlog Board Sticky Types can be mirrored to the Program Board.
There are two special sticky functions in place
A Sticky Type with function Dependency does have special attributes. Consider the standard workflow using dependencies.
- It has mirror to Program Board configured per default.
- It can be assigned to another team (to a team which supports to solve the dependency).
- In the app the receiving and producing team will be shown on the sticky.
Don't sync the dependency sticky to your ALM Tool. The dependency sticky is a "meta"-sticky used to get a simpler way to collaborate on dependency and visualize them on the Program Board (less crowded as you don't need to visualize all the dependent team level stickies.
- Sticky Types with the function Risk will have a ROAM-field available visible on all Boards
- Risk Stickies can moved to the Program Risk Board per default
Team Board Sync
If you configure the same Jira Issue Types for multiple piplanning app sticky types the color can't be differentiated anymore by the piplanning app.
4. Risk Board
Configure Sticky Types for the Risk Board
As Risk Sticky Types moved from the Team Boards on to the Risk Board will get the Sticky Type and color of the first Sticky Type, this might be a useful configuration
5. Backlog Board
Configure Sticky Types for the Program Backlog Board
Backlog Board Sync
You can add one or more sticky-type (optionally mapped to a Jira issue type) to the backlog board. As the Jira projects are already define in the ART-Mapping, you only need to specify the issue-type, label and optional WSJF field.
The name of the Sticky-type
The Jira issue-type which is mapped to this sticky-type. You will get a warning if the selected issue-type is not available in all the projects defined in ART-Mapping. You can continue with the warning - but the app will not be able to sync new stickies to this project in Jira.
This is optional. Specify the Jira field which represents the WSJF value / ranking of the stickies on the program-board. The field will be ignored if this field is not available for all the issues in all the projects defined in ART-mapping.
By default (without any Jira labels set), all Jira issues will be pulled to the backlog-board. As this is most-likely not what you want, you can specify a label.
6. Program Board
Configure Sticky Types for the Program Board
7. Collaboration Canvases
Collaboration Canvases can be provided to your teams to cover different use-cases before, during and after a PI Planning and are designed to support the whole Program Increment execution and lean-agile workshops on every level in your organization. Already in the piplanning app, check out how to Use Collaboration Canvases.
Add a new Collaboration Canvas Type
Add Canvas Type
press "Add Canvas" provide a Canvas Type Name
Choose a Canvas Background
press on the Background Preview
Choose your Background
Provide a Canvas Type Name
Your teams will see all Canvas Types you provide in the piplanning app. Provide the Collaboration Canvas Type with a meaningful name.
Define Sticky Types
For each Collaboration Canvas Type you can define what Sticky Types teams will be able to use.
Every Canvas Background comes with a pre-defined Sticky Type set adapted for the specific background.
You can add, change or delete Sticky Types.
You can sync Epic- and existing Issue-links of Jira into the piplanning app. To setup these links edit (or create) a piplanning session and navigate to the "Links" screen.
Some practical examples
Epic link from User-stories to Epics:
- Select in "From sticky type" the Sticky-type you have mapped to your Jira feature in step "Program Backlog Board"
- For "To sticky type", select the User Story sticky-type you have mapped to the Jira "Story" issue-type on the team-board screen
- The link type in between should then be "links epic to"
Issue link "relates" to between two user stories:
- Select in "From sticky type" and "To sticky type" the Sticky-type you have mapped to your Jira "Story" on the team-board screen
- Choose your desired issue-link (relates to) in "Link type"
- At the moment we only support Epic-Links and Issue-Links (no parent-child links)
- You can have only one link type between two sticky-types
For each Team you can either
- Not Sync the Iteration with Jira
- let the piplanning app create new Sprints in Jira for you
- Select an existing Jira Iteration
The Iterations shown in the dropdown are dependent on what you've configured under the general Team Mapping.
Use the Session in the piplanning app
Start the piplanning app in your browser and start planning.