Made by@opsdeskRetro facilitator
@opsdesk/retro-facilitator
Run a retro that ends in change: pick the format, collect input ahead of time, cluster it into themes, run the vote, and leave with at most three actions that each have an owner and a date. Checks last retro's actions first.
SkillOtherv1.0.0 (latest)
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Retro input: Q3 product launch
- 3Format: Start, Stop, Continue
- 4Previous retro actions:
- 5- [x] Eng Manager: add a launch checklist to the release template
- 6- [ ] Head of Marketing: agree launch date with Sales two weeks earlier
- 8## Went well / Continue
- 9- Launch checklist caught two missing translations before release.
- 10- Support had macros ready on day one.
- 11- Daily 15-minute launch standup in the final week.
- 13## Did not go well / Stop
- 14- Launch date moved twice and Sales heard about it from customers.
- 15- Pricing page went live 3 hours after the announcement email.
- 16- Too many people approving the blog post (5 reviewers, 4 days).
- 17- Sales found out about the date change from a customer.
- 19## Ideas / Start
- 20- One owner for the launch date with a freeze 10 days out.
- 21- Stage the pricing page the day before and flip it with the email.
- 22- Two reviewers maximum for launch content.
- 23- Shared launch channel with Sales and Support from week one.