How can teams view the priority of their feature (as set out in the backlog view) when they're assigning items to their sprints from the program board view during a PI planning event. Is there a way to display this in JA?
Hi @Vera du Preez ! Great question! There isn't a specific way to view priority of the Feature Backlog while viewing the Program Board. The Program Board is more about execution planning vs. priority (e.g. if it made the cut for the upcoming Quarter / PI, our focus shifts from what's the Backlog Priority to how do we most effectively execute against that Backlog for the Quarter / PI).
A recommendation I do have is to leverage the "Sprint Target Completion" field on the Feature prior to heading into a planning event to help indicate potential priority needs from a delivery perspective. Before planning you can look to target out when work needs to be done (based on priority conversations) and then teams can see that target sprint when looking to add their team target sprint (see screenshot). If they can't complete the work by the sprint initially targeted, a conversation should occur to talk about priority.
Hope this helps!
@Mark Cruth thanks for the speedy response. They have a massive backlog - which isn't ideal but I'm wondering if it's possible to pull through the backlog priority into a field in the feature view you've got in your example there, at least if they click on the feature, they can do a quick sense check?
That's a great idea! I don't believe that's possible today, but a great enhancement opportunity. Honestly, the only way I think of to give you a view of Backlog priority and the Program Board at the same time would be to have two browser windows up next to each other...one on the Feature Backlog and the other on the Program Board.
Hopefully others have ideas they can chime in with too!
*Typically* per certain frameworks- The priority of the backlog is described/explained to the team(s) at the start of the planning event. (either by a PM or PO) the teams then decompose the features in priority order until their sprints are appropriately full. Appropriately full of course varies, by the framework and planning cadence. However, if the teams use the Feature level backlog - Program Rank for PI view, that should provide the correct view from which to start their planning/decomposition.
There is a nifty little gem of an article on using Jira Align for PI Planning somewhere in this community, that describes this process well. If I am able to locate it, I'll post the link below this response.
I would recommend, that if you do enter the enhancement to add priority as a viewable field (either on the board, the popup "short description or card) on the program board, that you stipulate the priority as the Program level PI rank. There are MULITPLE ranks in Jira Align, so that specific ask will, I think, provide the clarity the product team needs and you with the desired result.
(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events