nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Set Up PIs and Sync Sprints to Align Jira Software and Jira Align Sprints

Tim Keyes

Follow these best practices to setup PIs and sync sprints to align Jira Software and Jira Align sprints:

Determine program increment cadence and mapping to programs (quarterly is typical) and create program increments.
Create sync sprints for the program increment spanning the length of the PI. These will be place holder dates for future sprints in Jira until they are activated.
Publish the sync sprint cadence to Jira scrum masters to ensure proper sprint alignment between Jira Software and Jira Align.

Notes:

Jira Align pairs Jira Software sprints to Jira Align sync dates based on the end date of the sprints plus or minus the buffer day range established under Jira Align Jira Software Setup.
Jira Align predicts future sprint dates as they come over from Jira by using the active Jira sprint as a baseline and setting the start and end dates of future sprints to the subsequent sync sprint date period, because Jira does not have future dates.
All sprints created on a board in Jira mapped to Jira Align will take the date of a sync sprint placeholder. This means “bucket and planning” sprints from Jira will interfere with future sprint alignment between Jira Align and Jira Software.

Comments

Shawn Kessler

@Tim Keyes another great article--we are grateful for your knowledge of Jira-Jira Align best practices.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scaled-agile

best-practice

jira-align