Optimizing Agile PIs: How Many Sprints Should You Have?

When structuring Agile Release Trains (ARTs), a fundamental question arises: How many sprints should be in a Program Increment (PI)? To determine this, we first need to understand the length of a PI and how it impacts Agile teams.

By the way; What is a Program Increment?

A Program Increment (PI) is a dedicated timebox in which an Agile Release Train (ART) delivers value. An ART typically consists of 5 to 12 Agile teams collaborating to achieve strategic goals.

How Long is a PI?

PI duration generally falls into one of these three standard options:

• 8 weeks
• 10 weeks (default in SAFe)
• 12 weeks

Each PI length determines the number of sprints included.

Sprint Breakdown by PI Length

8-Week PI

• 3 development sprints (each 2 weeks long)
• 1 Innovation and Planning (IP) sprint

10-Week PI (Default in SAFe)

• 4 development sprints (each 2 weeks long)
• 1 Innovation and Planning (IP) sprint

12-Week PI (Common in organizations aligning with financial quarters)

• 5 development sprints (each 2 weeks long)
• 1 Innovation and Planning (IP) sprint

Choosing the Right PI Duration

While SAFe considers 10 weeks the default, many organizations prefer a 12-week cadence as it aligns with financial quarters, simplifying budgeting and reporting cycles. However, if your environment experiences frequent change and uncertainty, a shorter PI (such as 8 weeks) may be a better fit.

One important factor to consider is the frequency of PI planning. Shorter PIs mean more frequent PI planning sessions, increasing coordination efforts. An 8-week PI requires planning every two months, which can add overhead if not managed well.

The Role of the Innovation and Planning (IP) Sprint

The IP sprint is a structured two-week period dedicated to:

1. Innovation – Hackathons, R&D, learning sessions, and experimentation.
2. PI Planning Preparation – Ensuring readiness for the next PI planning session.
3. Inspect and Adapt (I&A) – Reviewing previous PI outcomes, identifying improvements, refining processes for future work, and clearing high-priority Retrospective action items.
4. Technical Debt Management – Addressing accumulated technical debt, refactoring code, optimizing system performance, and improving overall software quality.

While innovation should be ongoing, the IP sprint provides focused time for exploration, creative problem-solving, team development, and clearing high-priority Retrospective action items. Companies like Apple have thrived by incorporating structured innovation, distinguishing themselves from competitors who prioritize speed over creativity. Additionally, the IP sprint serves as an opportunity for Technical Debt Management, enabling teams to refactor code, optimize system performance, and enhance overall software quality.

Challenges in Selling the IP Sprint to Leadership

Convincing executives to dedicate an entire sprint to planning and innovation can be difficult. The key argument is that structured innovation leads to better long-term agility, quality, and efficiency. A 12-week PI structure, with 5 development sprints followed by an IP sprint, often provides an optimal balance between delivery and innovation.

Final Thoughts

Regardless of the duration, the IP sprint is a crucial component of sustainable Agile success. The right cadence depends on your organization's needs, business goals, and the level of flexibility required to adapt to change.

So, How many sprints would you do in your Program Increment (PI)? - Drop your reply and inputs.