What is the last activity of release planning day 2?

• A. Retrospective
• B. Demo of increments
• C. Budget approval
• D. Sprint planning

Answer: (A)

In PI planning, finishing with a retrospective emphasizes continuous improvement. After two days of aligning on goals, finalizing the plan, and addressing risks, the retrospective gives the ART a moment to reflect on how the planning process went and to capture concrete improvements for the next PI. This closing reflection helps teams learn from what worked and what didn’t, so future planning sessions run more smoothly.

The other activities aren’t the last step of release planning day two. Demonstrating increments typically occurs as part of system or program demos during the PI, not as the closing activity of the planning event. Budget approval is a governance activity that happens outside the close of PI planning, and sprint planning is an iteration-level activity that happens at the start of each sprint, not at the end of the two-day planning session.