Launching ARTs

Before your first PI Planning, you need to define the ART's structure:

1. Define the value stream: What value does this ART deliver? To whom? Be specific. "We build the customer-facing web and mobile applications" is better than "We do frontend."

2. Identify the people: Who will be on the ART? This often means pulling people from existing teams and reorganizing them. Target 50-125 people. Include all skills needed for end-to-end delivery.

3. Form the teams: Create cross-functional teams of 5-11 people. Optimize for:

• Minimize dependencies between teams
• Maximize each team's ability to deliver end-to-end value
• Balance skills and experience across teams
• Respect existing relationships and working patterns where possible

4. Assign ART roles:

• RTE: Your best facilitator with systems-thinking ability. This role makes or breaks the ART.
• Product Management: Someone who deeply understands customer needs and can prioritize ruthlessly.
• System Architect: Your most respected technical leader who thinks about the whole system.

5. Define the cadence:

• Iteration length: 2 weeks (default, adjust only if you have strong reasons)
• PI length: 5 iterations + 1 IP iteration = 12 weeks (default)
• PI Planning: 2 days, face-to-face

Common organizing mistakes:

• Creating teams by technology layer (frontend team, backend team, database team) instead of by feature area
• Assigning the RTE role to a project manager who hasn't been trained
• Making Product Management a committee instead of a person
• Splitting people across multiple ARTs

The first PI Planning is the ART's launch event. Preparation is critical:

8 weeks before:

• Assign and train the RTE, Product Management, and System Architect
• These roles need SAFe-specific training (Leading SAFe, SAFe for Architects, etc.)
• Begin building the Program Backlog with 8-12 features for the first PI

6 weeks before:

• Train all team members (SAFe for Teams training, 2 days)
• Form the teams and assign Scrum Masters and Product Owners
• Set up the development infrastructure (repos, CI/CD, environments)

4 weeks before:

• Prepare the business context presentation (executive sponsor)
• Prepare the product/solution vision presentation (Product Management)
• Prepare the architecture vision presentation (System Architect)
• Refine the top Program Backlog features (acceptance criteria, sizing)

2 weeks before:

• Logistics: Book the room (big enough for all teams), prepare materials (boards, stickies, string), set up A/V
• Communication: Send agenda, expectations, and pre-reading to all attendees
• Dry run: RTE, PM, and SA rehearse their presentations
• Backlog readiness: Top 10-15 features are refined and ready for team decomposition

Day before:

• Set up the room. Each team gets a table/area. Program board is on the wall. Presentations are loaded and tested.
• RTE does a final walkthrough of the agenda and logistics.

Key success factor: Don't try to get the first PI Planning perfect. It will be messy. The goal is to plan together, surface dependencies, and create alignment—not to produce a flawless plan. Perfection comes with practice.

The first PI is about learning the mechanics. Don't judge the ART's performance by PI 1 results.

PI 1 — Learning the Dance

• Teams are learning new processes and roles
• PI Planning feels chaotic and runs over time
• Too many dependencies are discovered—this is good (they existed before, you just couldn't see them)
• Predictability is low (50-70% of planned objectives delivered is normal)
• Focus: Get the cadence right. Run all events. Learn from each one.

PI 2 — Finding the Rhythm

• PI Planning is smoother (teams know what to expect)
• Dependencies are better managed (some have been eliminated)
• Predictability improves (60-80%)
• Teams start self-organizing more effectively
• Focus: Improve quality practices. Start addressing systemic impediments from I&A.

PI 3 — Hitting Stride

• The cadence feels natural
• Predictability stabilizes (80%+)
• Cross-team collaboration improves (trust builds through repeated interaction)
• ART-level metrics become meaningful (trend data)
• Focus: Optimize flow. Reduce batch sizes. Address architectural constraints.

PI 4+ — Continuous Improvement

• The ART is a performing team of teams
• Improvement is incremental and data-driven
• The I&A process produces impactful changes
• Focus: Performance optimization. Innovation. Helping other ARTs learn from your experience.

The coach's role: Lean-Agile coaches should be embedded with the ART for the first 3-4 PIs. They coach RTEs, Scrum Masters, Product Owners, and leadership. Gradually reduce coaching intensity as competence builds. Don't remove coaching too early—regression is common.