How to refine planned work items for PI planning with Advanced Roadmaps

Background

• Validate ranked features and articulate descriptions, acceptance criteria, and target dates to help your team understand what the business as a whole expects of them.
• Review dependencies and risks associated with a feature to determine the team's level of confidence in delivering the feature.
• At the end of PI Planning, ensure the program is committing to work that is aligned with the objective.

Description

Navigate to "Shared PI Plan" in Advanced Roadmap

1. Review the feature plan.
   1. Verify the highest priority features.
      1. Inspect the sequencing of feature backlog listing to ensure it matches business needs with appropriate due dates and status. Where clarity is needed, open up items to review more details.
      2. Check for issue IDs in numeric order, or titles in alphabetical order, as this may indicate a lack of ranking.
   2. Make adjustments and address flagged concerns.
      1. The formalized list of feature requests initiates subsequent kickoff activities that will be highly dependent on this starting point. Now is the time to make final changes if needed as the teams will be making quarterly commitments based on the ask.
      2. Address any items flagged with yellow markers or groupings.

         

2. Manage dependencies.
   1. Review existing dependencies.
      1. To view the details of the dependencies in your plan, select the badge on either side of the schedule bar. This will bring up the dependency details window.
      2. When viewing dependencies on your timeline, the badge on either end will turn red if there are conflicting dates. To resolve this, change the start or end date of either dependency.

         

3. Create new dependencies.
   1. To add a dependency to an issue in your plan, hover on the schedule bar for the issue to which you want to add a dependency.
   2. Select the + icon. Selecting the + icon on the right will create an outgoing dependency, while the left will create an incoming dependency.
   3. Select the issue to which you want to attach the dependency.
   4. Select the check mark to confirm your choice.
   5. After adding a dependency to an issue, adjust the dates by selecting and dragging the ends of the schedule bar. The badges on either end will turn red if there are conflicting dates.

      
4. Manage risks.
   1. Navigate to your risk board in Jira.
   2. Review existing risks.
      1. Create any additional risks needed.
      2. Ensure the risk or risks are linked to the feature using the relates to link.

         
      3. Manage the risks you created during the PI planning event by dragging them into the correct ROAM status:
         • Resolved: A risk is addressed and is no longer a concern.
         • Owned: Someone takes responsibility for the risk.
         • Accepted: Nothing more can be done. If the risk occurs, the release may be compromised.
         • Mitigated: The team has a plan to adjust if necessary. 

           
5. Manage objectives.
   1. Review and confirm your features are associated with the appropriate objectives.

      

Output

• Refined and committed PI plan with ROAMed risks, committed objectives, and managed dependencies.

  

References

• View all of an issue’s dependencies on your timeline
• Add a dependency from your timeline in Advanced Roadmaps
• Displaying the dependencies map