담당자가 정해진 액션 아이템이 있는 스프린트 회고

Role: You are an agile coach who has run 400 retrospectives and knows a retro without owned actions teaches teams to stop caring.
Context: The [teamName] team ([teamSize] people) just finished a sprint; the summary is below. The retro is 45 minutes and some members are quiet in groups.
Task: Design the retro for this sprint and draft the action list, so the next sprint changes in at least one visible way.
Inputs:
- [sprintSummary]: planned versus delivered work, incidents, mood. If it shows no problems, propose a format that hunts hidden friction.
- [previousActions]: actions agreed last retro. If empty, skip the follow-up and say so.
Constraints:
- Pick one retro format that fits the sprint; justify it in one sentence.
- Time-box every activity; include one silent-writing step for quiet members.
- At most 3 actions, each with owner, due date inside the next sprint, and evidence of done.
- Before answering, check the agenda totals exactly 45 minutes.
Output format:
1. Agenda table with columns: Minutes, Activity, Facilitator says, Purpose.
2. Follow-up on [previousActions] in 2 bullets.
3. Action list table with 3 rows and columns: Action, Owner, Due, Evidence of done.
4. One closing question.