PI Planning 1.0.0

The solution requires additional manual configuration, check the Solution Configuration section for the details.

Solution Overview

The solution facilitates views to aid in Pre-Plan and Coordinate and Deliver activities during a Solution Train PI Planning Event. The Planning Interval (PI), a cadence-based event, aligns teams and stakeholders of the ART with a unified mission and vision. The solution enables the Planning Interval (PI) Event flow or Solution Trains, ARTs, and Teams and covers the following aspects of PI Planning:

• Organizational Readiness - prepare PI and Team Iterations for each team in an ART, define PI capacity;
• Content Readiness - prioritize and prepare backlog of features for the next PI;
• Team Break-Out Session, where teams:
  • Choose features from a backlog, break them down into User Stories, and estimate
  • Plan User Stories into Team Iterations based on their available capacity,
  • Create Dependencies
  • Define Team PI Objectives
  • Discuss Risks
• Plan Review, where program management:
  • Review the ART Board to see the feature plan and existing dependencies
  • Organize Team PI Objectives into ART PI Objectives
  • Eliminate ART PI Risks
  • Check capacity load across Team Iterations

Solution Flow

1. Solution Planning Intervals, ART Planning Intervals, and Team Iterations will be automatically generated after installation. Solution Planning Intervals will be generated for all the Periods for all the Solution Trains, Agile Release Trains, and Teams in the system.

2. Set Teams Capacity

3. Rank Features by WSJF

Evaluate Features in the backlog using the WSJF method. Prioritize and assign those of the highest priority to the Planning Interval.

4. Adjust the capacity plan

Check your capacity against planned work for the next Planning Interval. Adjust accordingly from the same view.

5. Assign Features to your team and break them down into User Stories and estimate them

As a team, start taking the top-priority Features from the backlog. Stick to your team's available capacity.

6. Plan User Stories into Iterations and visualize dependencies with other teams

7. Capture Team PI Objectives. Define the planned business value of each objective

8. Communicate Team Risks

9. Review and resolve ART dependencies on an ART Planning Board

Check the ART Planning Board to review dependencies and spot planning issues. Resolve planning issues by re-planning User Stories between Team Iterations. Adjust a Feature Team Iteration by re-planning its User Stories.

10. Review planning results on the PI Dashboard.

Solution Configuration

Rename PI

The Release term in the default process should be set to Planning Interval to install the solution.

Update Detailed View

After solution installation configurable dropdown fields (Solution Planning Interval, Planning Interval (Release), and Team Iteration) will appear automatically for Epics, Features, User Stories, and Bugs. You need to update Detailed View for the mentioned entities and remove native fields. To do that:

• Open Settings -> Detailed Views
• Select Epic, Feature, User Story, and Bug individually
• Find the Release field (click anywhere in the code, press Ctrl+F, and type Release in the search field)
• Delete the default Release field
• Find the Team Iteration field (click anywhere in the code, press Ctrl+F, and type teamIteration in the search field)
• Delete the first default Team Iteration field
• Click the Apply changes button