Create a Mad Sad Glad retrospective board for a sprint review with categorized team feedback
About the framework
The board has three columns with an uneven but explicit count: three Mad notes, three Sad notes, and four Glad notes. Mad covers changing requirements, scope-related delay, and meeting overload. Sad covers a teammate leaving, a growing bug backlog, and slow stakeholder feedback.
Glad records an on-time feature, team collaboration, positive UI feedback, and time saved by new tooling. These are sample reactions, and the board does not identify speakers, rank concerns, or assign remedies. A missed deadline and an on-time feature can refer to different work; add context when replacing the examples.
Use the columns to capture what happened and how it affected the team. Keep the contributor’s chosen category, then discuss specific events behind recurring themes and agree on a follow-up change.
What's included
Mad Sad Glad Retrospective
✦ Free preview · Sign in to use
Frequently asked questions
No. The example has three Mad, three Sad, and four Glad notes. The useful balance comes from honest feedback rather than filling equal quotas.
Yes. The sample places it in Sad, but the category should reflect how the contributor experienced it. Discuss the event without forcing everyone to use the same emotion label.
Choose a recurring issue, describe the behavior or constraint behind it, and agree on a change to try. Add an owner and a review point because the supplied board has neither.
Free to start. No credit card required.