The RTE needs to enforce a strict timebox for each team presentation in the plan review sessions. Click on the team on the wheel to view the dependencies on the right. The Epic and Capability toggles need to be turned off. Open the Program Board configured with View Type = Normal View to display card IDs and titlesĪn easy way to view dependencies between teams.
#WHAT IS THE GOAL OF THE PI PLANNING EVENT HOW TO#
Check out the article Creating Team Risks in Jira Align on how to do this) Tab 2 - Objectives Grid Tab 3 - Risk Gridįiltered by team (The Risk Grid is not filtered by the Team configuration. Tab 1 - Jira Backlog, Jira Align Backlog Kanban - Sprint View, or Story Map Jira Backlog The presenter should open 5 tabs in a web browser that will be shared through the web conference. To filter some of the Jira Align views by team, the presenter can select the team name in the Team configuration on the Configuration Bar.
This enables the presenter to easily switch between the views as they present without having to navigate through Jira Align or Jira.īelow are views to pre-load on multiple tabs on a web browser (Chrome or Firefox) following the SAFe Draft and Final Plan Review agendas. One way to avoid this is to have the team presenter open all of the necessary Jira Align (and Jira if used) views in multiple tabs on their web browser prior to presenting. In a virtual plan review session, valuable time can be lost if a presenter is clicking through Jira and Jira Align to load different pages on their screen when presenting the planned sprints, PI Objectives, risks, and Program Board.
TIP #3: Open Jira Align and Jira Views on Multiple Tabs
Also RTEs may provide guidance to presenters on the specific information to present and what not to present. One way to minimize this from happening is for RTEs to review the plan review agendas with the presenters on each team ahead of PI Planning. Nothing can waste more time and lose people’s attention than teams not knowing what information and artifacts they need to present during the plan reviews sessions or talking about information that isn’t required or even relevant. On the day of PI Planning reviewing the presentation order with teams again can be a helpful reminder. Posting the presentation order on Confluence or another collaboration space for all teams to see before PI Planning can help teams prepare their presentations ahead of time. The Release Train Engineer (RTE) should plan the presentation order for the plan review sessions in advance of PI Planning. TIP #1: Plan the Presentation Order In Advance This article provides several tips that can help optimize team presentations in virtual Draft and Final Plan Reviews sessions while also using Jira Align and Jira. The Jira Align and Jira views detailed in the article can also be used to present the draft and final plans virtually in the review sessions. The Atlassian Community article, Facilitating a PI Planning Team Breakout Virtually in Jira Align, provides an overview of how activities during the PI Planning Team Breakout can be facilitated virtually using Jira Align and Jira with remote team members. So team presentations in the review sessions need to be concise and efficient as not to take up valuable time. When facilitating the Draft and Final Plan Reviews virtually keeping participants attention for this amount of time presents a big challenge. For Agile Release Trains (ARTs) of 5 to 10 teams these review sessions can take anywhere from 25 to 100 minutes. Draft and Final Plan Reviews are timeboxed sessions during the Scaled Agile Framework (SAFe) PI Planning event where teams have approximately 5 to 10 minutes to present their team preliminary (Day 1) and final (Day 2) plans, PI Objectives, and risks and impediments.
0 kommentar(er)
