when capturing a program vision in Jira Align, it also asks me to add one or several "priority visions" below. Why is this (I always thought there can only be one vision) and how can I proceed without creating additional priority sub-visions ? Thx
Yes, you are correct, you start with one main program vision, where Product Management provides the overall, specific program context and vision. Next, the idea is to use the priority visions to further break down the vision into smaller vision statements, or sub or supporting visions--they are completely free form. For example, define how your competitors or your company's strengths and weaknesses fit into the overall vision. See the example below.
Basically, use the priority visions to help further define the vision--so that the parts help make up the whole. If you choose not to use the priority visions, just enter dummy text for the first priority vision or TBD as a placeholder. Hope this helps.
Due to recent challenges of most companies having to move to virtual and remote PI planning events, the Jira Align Solutions Architects wanted to start to capture some best practices and FAQ Table of...
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