PI Planning Event

Requires the following solutions to be installed:

• Agile Release Trains (ARTs) (edcffe31-75d3-40b8-9b16-6fbfa380466e)
• Team and ART PI Objectives (786941ff-055a-4b1e-a9de-6d12fd35ca8d)
• ROAM Risks (c46ba698-5cee-4a7e-91af-8bbd3f9dc88b)
• WSJF Prioritization for Feature (68a76965-1ce6-4752-b82a-678d2dc6fb14)
• A Dependency instead of an Impediment (a7e3a685-8ac0-40d6-a642-3d4206604099)

It can be extended by the following solutions:

• Iteration Generation for Agile Release Train (ART) (5170cf26-77e6-4d16-96f3-c11a5b86f876)
• Confidence Vote (af7a0e53-663f-47bb-9e6f-469a258044f9)
• Planning Interval Tracking Dashboard (0e03c4f9-30a6-400a-86f7-476238af98dd)
• Feature Progress Measure Report (d72dddb4-0b21-4e17-974f-894f75427d82)

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

--------------------------------------------------------------------------------------------------------------------------------------

Solution Overview

Planning Interval (PI) Event enables teams to align their business needs and requirements to a specific timebox, typically 10-12 weeks in duration.  Leaders in the organization take part by describing the vision, roadmap, and common purpose for the team of teams called an Agile Release Train or ART.

The solution covers the Planning Interval (PI) Event  (read about it here) flow and consists of views for the following actions:

• 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 Installation

1. Create a new Planning Interval (PI)

2. Generate Team Iterations

You can use different solutions to generate PIs and Team Iterations. In the example below we use Iteration Generation for Agile Release Train (ART) solution.

Note: the End Date for the Planning Interval will be adjusted automatically based on the end date of the last Team Iteration.

3. Set Teams Capacity

4. 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.

5. Adjust the capacity plan

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

6. 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.

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

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

9. Communicate Team Risks

10. 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.

11. Review planning results on the PI Dashboard.

-----------------------

Version 2.0

Solution Enablement

The solution can be enabled from Solution Library. Please contact our Support Team to enable it on your account, if it's not available yet.