What happens in day 2 - during the am breakout #2?

• A. RTE leads risk workshop
• B. Business Owner adding business value to release objectives, team finalize PI plan, consolidates program risks, impediments and dependencies, and stretch objectives
• C. Architects present solution intent
• D. QA performs system integration tests

Answer: (B)

Day 2 morning breakout #2 is about closing the loop between business needs and the planned work. After teams have drafted their PI plans, this session is where Business Owners attach business value to each release objective, helping ensure the plan will deliver the intended outcomes. Teams use this time to finalize the PI plan, pulling together and agreeing on program risks, impediments, and dependencies so there’s a shared commitment. They also discuss stretch objectives—extra goals that could be pursued if capacity allows. The Release Train Engineer and other roles support by surfacing risks and dependencies, but the emphasis here is aligning business value with the plan and achieving a concrete, committed plan for the Program Increment.