PI Planning Retrospective

Choose this exercise

Purpose: Collect actionable operational feedback on a large planning event so future sessions run more effectively.

Use it when: Directly after closing a multi-team or Program Increment planning session to inspect the event itself rather than plan content.

Skip it when: Do not use for general product backlog grooming or when evaluating sprint deliverable quality.

Group arrangement: Individual posting followed by whole-group clustering and review

Timing: Source specifies 20 minutes; UWT maintains 20 minutes structured across silent generation, clustering, and action agreements.

Materials and tools

• 1 shared physical whiteboard or wall space marked into 4 quadrants
• 4 pads of sticky notes in different colors or standard yellow
• 1 marker per participant
• 1 digital countdown timer

Before participants arrive

1. Draw 4 distinct columns or board sections labeled: What Went Well, What Didn't Go Well, Improvements Needed, and Thank You.
2. Distribute sticky notes and markers to each seat or workspace.

Say this to open

We are stepping back from the plans we created to look exclusively at how this planning event was run. Focus your notes on tools, prep, schedules, room layout, meals, or communication. Write one observation per note, and place it in the appropriate column. You may also write a thank you note to acknowledge colleagues who helped keep things moving.

How to run it

1. Introduce purpose and scope 2 minutes

   State the scope using the opening script. Emphasize that discussion centers on logistics and event organization, not technical sprint deliverables.

2. Silent note generation 6 minutes

   Participants work independently to write brief notes for each of the four categories: What Went Well, What Didn't Go Well, Improvements Needed, and Thank You. They post them to the shared board as they finish.

3. Cluster and review themes 7 minutes

   Group similar items aloud as a whole team. Read out high-frequency operational bottlenecks and acknowledge the Thank You contributions without prolonged debate.

4. Agree on action items 5 minutes

   Select 1 to 3 distinct logistical improvements for the next event. Assign a named owner to each action before concluding the session.

Debrief questions

• Which logistical obstacle cost our planning sessions the most time?
• What one change to our agenda or room setup should we confirm right now for the next planning session?

Finished output: A grouped feedback board and a list of 1 to 3 assigned action items for organizing the next planning event.

Remote

Set up a four-column virtual whiteboard matching the four categories. Participants draft digital notes during silent generation, drag them to the board, and use text chat or voice to select owners for the top action items.

Hybrid

In-person participants write physical sticky notes while a designated scribe mirrors them onto a shared digital board that remote participants edit directly. Display the digital board on the central in-room screen so both groups see identical clusters.

Access and participation choices

• Provide an option to dictate notes to a teammate or submit them privately to the facilitator beforehand.
• Participants may post feedback anonymously and can choose to pass on writing thank you notes.

If the session gets stuck

Participants drift into debating product architecture or project scope instead of event logistics.

Remind the room that roadmap and technical debates belong in sprint backlogs, then redirect focus back to venue, schedule, and tooling.

The board fills with generic complaints without concrete suggestions.

Prompt the room to translate each major negative note into an immediate adjustment for the 'Improvements Needed' column.

Terms used here

• PI Planning: Program Increment Planning, a cadence-based event where multiple agile teams align on shared goals, dependencies, and schedules.
• RTE: Release Train Engineer, the person who facilitates and manages the execution of multi-team planning events in the Scaled Agile Framework.