What are the best practices for conducting a Retrospective?

Short answer: Best practices: Rotate formats to keep things fresh.

Explain a bit more

Foster psychological safety — no blaming. Use data and facts (velocity, defect rates) to ground discussions. Focus on 1-2 action items, not a wish list. Follow up — review actions in the next Retrospective. Popular formats: Start / Stop / Continue Mad / Sad / Glad 4Ls (Liked, Learned, Lacked, Longed for) Real-World Example: A team felt retrospectives were repetitive. The Scrum Master tried a “Team Radar” activity to visualize team health across areas like collaboration and quality. This revealed deeper issues and sparked more meaningful discussions. Scrum Artifacts:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.