You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
One of the main benefits of the Scaled Agile Framework (SAFe) Program Increment (PI) Planning event is face-to-face planning in a "big room" with all the teams on an Agile Release Train (ART). However, in the age of digital transformation teams are becoming more geographically distributed across multiple locations and timezones. Also unforeseen challenges such as budget and financial constraints or travel restrictions can make it difficult to bring teams together for “big room” planning.
Jira Align can help facilitate team planning virtually for developing sprint (iteration) plans and capturing risks, dependencies, PI objectives, milestones and the final PI plan. To effectively facilitate a team breakout virtually with Jira Align it is recommended that a reliable web/video conferencing software is required to share Jira Align and Jira views among team members.
Typically during PI Planning, scrum teams plan sprints on wall charts and story cards. To accomplish this virtually, teams can do this in 3 ways through: Jira Backlog, Jira Align Backlog Kanban - Sprint View, or Story Maps.
When deciding which option is best to use for planning sprints the following factors should be considered:
Do teams use Jira Align or Jira to do sprint planning?
Is it important for teams to plan using a visual radiator with color-coded story cards?
Teams that normally conduct sprint planning during a PI using the Jira backlog can use the Jira backlog for planning sprints in PI Planning.
If teams use Jira Align for sprint planning, teams can use the Backlog Kanban - Sprint View accessed through the Story Backlog. The Backlog Kanban - Sprint View is a good view if you are looking for something similar to wall charts and story cards and also enables you to view the team's velocity and load.
For information on the Backlog Kanban - Sprint View check out the Atlassian Community article by @Rob Phillips Using Jira Align’s “Backlog Kanban – Sprint View” to Visualize SAFe’s Day 1 PI Planning event.
Jira Align does not associate risks to teams which can make it difficult to filter the Risk Grid when presenting team risks for the Draft and Final Plan Reviews. To understand how to create team risks in Jira Align check out the Atlassian Community article by @Tom O_Connor Create Team Risks in Jira Align.
Jira Align enables a team to create a dependency on another team and for teams to commit to the dependency they agreed upon during the team breakout. For more information on how to use dependencies in Jira Align, check out the Dependency Overview and Dependency Type article on the Jira Align Knowledge Base.
During the team breakouts scrum teams compose and refine PI objectives in Jira Align. On Day 2, the business owner/stakeholder updates the PI objectives within Jira Align with the Planned Value (scale of 1 to 10). Critical milestones (e.g. trade show, product launch, etc.) are captured using the objectives but with Type = Roadmap Milestone. For more information on how to use objectives check out the Create Objectives article on the Jira Align Knowledge Base.
To set the final plan on the Program Board using Jira Align, teams assign a sprint to the Team Target Completion Sprints field to features on the Program Board. For more information on setting up the Program Board during PI Planning check out @Rich Sparks's article, Building a Program Board during PI Planning.
Also for more information about the Program Board, dependency management, and objectives check out Caz's article on the Atlassian Community, Jira Align for Release Train Engineers.