During the PI planning session, teams estimate the capacity of each iteration and identify the features to be implemented. Each team iterates through each iteration, creating an iteration planning schedule that everyone can see. Teams also set and track PI goals in the Team Kanban board to ensure everyone is aligned to the goals. Potential risks to the process can also be documented and managed in the Team Kanban board, and risks can be mitigated with appropriate actions.

1、View Team Board 

1.1. After each team has claimed the features, they can go to the [Team Kanban] page to schedule the features and user stories, and visualize the management through the iteration, goal and risk columns.
1.2. Team members will enter their team's Kanban board by default, and managers can view all team's Kanban boards.
1.3. left Backlog area displays all user stories under the current PI associated project, users can drag and drop the stories into their own team's Kanban boards. the Backlog area can be stowed away.

2、Link Story

2.1. In an iteration, the team can maintain the capacity of each iteration, assigning the features and stories to be implemented to each iteration, and the system automatically calculates the workload of the team.

2.2. Link stories can also be removed.

3、Maintenance risk

On the right side of the [Team Board], goals and risk items can be maintained directly, and the team can maintain identified risks and impediments, and manage risks by ROAM classification.

4、Maintenance Objective

On the right side of the [Team Board], goals and risk items can be maintained directly, and teams can maintain their committed and uncommitted goals, scoring BV and AV.
Committed PI goals help us rationalize our work planning, and uncommitted goals improve the predictability of delivered value.

5、Start PI

After the PI planning meeting, teams need to activate the PI to execute the work committed to in the iteration plan.
5.1. You can click [Launch PI] to formalize the planned iteration to create a real iteration in Jira's project, which will automatically bring in information such as start and end time, team members, and user stories. Subsequently you can disassemble the tasks in Jira to complete the work.
5.2. Only one iteration per team can be created in Jira.