When we go to the Program icon on the blue Nav bar and select "Backlog" under Program, then select the correct Program and PI while we ensure "Viewing" is set to "Feature (Jira Epic)". We then see a list of all Features (Jira Epics) and we take time to drag and drop all Features (Jira Epics) into the correct prioritized order.
I "thought" when I would go into the Project in Jira and look at the backlog of the Jira Epics the prioritized order would be the same but the Epics are not in the same order as the Feature (Jira Epics) in Jira Align. I thought this is why they were synced so Product Owner in Jira Align could prioritize work and Scrum Team in Jira could see work prioritized.
Appreciate any assistance here.
Thanks - Tom
First I want to say I appreciate your help! As the Admin, I was able to get this working. I used 10019 as the field number. However, this appears to be a bit of a fail as it cannot push to Jira at the team level, only the program level. Meaning, if we want to use this feature, the three team belonging to a program need to all agree on prioritization of program backlog prior to pushing to Jira.
Follow-up question: If we do push at the program level to the three teams (projects in Jira), the rank for the Epics in Jira will be the same as the rank for the Jira Align Features correct?
Thanks again, Tom
The key to syncing the story level is:
1) You must be in the Story backlog
2) you must have teams and sprints selected (don't forget to include Unassigned)
3) you must "Push Rank to External system" for EACH SPRINT (including Unassigned)
As a general rule - I train and coach the use of team level sync in the following manner - For simplicity sake, I am describing using SAFe "norms":
Product Owner for each team should discuss & set rank for stories in Jira Align starting with Unassigned backlog (generally done prior to a PI Event or before/during the any one of the breakout sessions prior to wrap up.
Next the Product Owner for each team should discuss & set rank for stories in Jira Align for individual sprints - focusing on the 80/50/20/10 rule for sprint order.
Hope this helps!
Lean Portfolio Management (LPM) is a relatively newer management methodology which draws from lean and systems thinking approaches to drive value-based outcomes, as opposed to more traditional techni...
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