Question 1

What should a sprint retrospective message include?

Accepted Answer

Classic retro format: what went well (keep doing), what didn't go well (stop doing), and what to try next sprint (start doing). Asking people to think about this before the meeting — rather than cold in the room — leads to richer, more honest discussions.

Question 2

When should I send a sprint retrospective reminder?

Accepted Answer

2 hours before the retro meeting gives people enough time to gather their thoughts without them forgetting. Avoid sending it the day before — it gets buried. Sending it too close to the meeting means people arrive unprepared.

Question 3

How do I automate sprint retro reminders in Slack?

Accepted Answer

Use Schedule Message to set a biweekly recurring message that posts on the last day of each sprint, 2 hours before your retro time. Set it once and it runs for the rest of the quarter.

Question 4

Should retrospective feedback be shared in Slack or kept for the meeting?

Accepted Answer

Both works. Sharing in Slack before the meeting warms up quieter team members and gives everyone a chance to see themes emerge. Some teams prefer all input in the meeting for spontaneity. Either way, the reminder prompts reflection, which is the main goal.

Question 5

What if the sprint retro message is always the same?

Accepted Answer

That's fine and intentional. A consistent format builds the habit. If you want to vary it, change the emoji or add a theme ('this week: focus on communication') — but keep the core three questions stable so the team knows exactly what's expected.

Sprint Retrospective Reminder Message for Slack

Copy-paste templates (3 variants)

Frequently asked questions

Related templates

Automate this template with Schedule Message