Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,035
Community Members
 
Community Events
168
Community Groups

How to handle feature carryover across PIs?

Since only one PI can be selected for a feature, what is the proper way to handle work that carries over from one PI to another PI? Currently we are asked to change the PI once it carries over. Will this cause bad data?

  • How will the work done during sprints in the previous quarters show?
  • Are the misaligned stories in the Program Room accounted for in reporting?
  • Is the percentage complete calculation my Roadmap accurate?
  • Will velocity calculations be accurate? 
  • I'm sure they are other areas impacted also.

1 answer

2 votes
Sam Tsubota Atlassian Team May 20, 2021

@Tim Young Splitting features that don't complete within a PI is a good option for handling carryover work. When you split a feature in Jira Align the feature will be split into a part 1 and part 2. The part 1 of the feature will have all the accepted stories linked to it and the part 2 of the feature will have all the stories not accepted within the PI. During the splitting process you can target the PI to assign to part 2.  After splitting the feature, a link between split part 1 and part 2 in the feature details panel will appear.

Split.png

Targeting split part 2 for a future PI

Split screen.png

Link to split part 2

Link part 2.png

 

The advantages of splitting features are vs. carrying over features:

  • The stories won't appear as misaligned in the Program Room
  • Velocity calculations will reflect the work completed in a PI
  • When carrying over a feature to the next PI the Program Board will show a planning issue for the feature that stories are in a past sprint. This is due to accepted stories in the prior PI linked to the carryover feature. By splitting features this will be avoided and the Program Board will reflect actual planning issues.

Thanks @Sam Tsubota great article and highlights why splitting features is important.  Coupling this with prioritisation and with the focus of getting stuff done it can highlight where teams need to focus. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events