iterate-retrospective

Name: iterate-retrospective
Author: product-on-purpose

486stars64forks

How to install iterate-retrospective?

product-on-purpose/pm-skills/iterate-retrospective

$npx -y skills add product-on-purpose/pm-skills --skill iterate-retrospective

Installs into the current project.

Summary

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-less

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Retrospective
3
4	A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.
5
6	## When to Use
7
8	- At the end of every sprint (for agile teams)
9	- After completing a significant project or milestone
10	- Following a major incident or outage
11	- When team dynamics feel off and need addressing
12	- At regular intervals (monthly, quarterly) even without specific triggers
13	- When onboarding new team members to establish improvement culture
14
15	## When NOT to Use
16
17	- You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it
18	- You are scoring an OKR cycle at close -> use `measure-okr-grader`
19	- The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision`
20	- You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap`
21
22	## Instructions
23
24	When asked to facilitate or document a retrospective, follow these steps:
25
26	1. Set the Context
27	Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.
28
29	2. Choose a Format
30	Select a retrospective format that fits the team's needs. Common options include:
31	- Start/Stop/Continue: Simple and direct
32	- 4Ls: Liked, Learned, Lacked, Longed for
33	- Mad/Sad/Glad: Emotion-focused
34	- Sailboat: Visual metaphor (wind=helps, anchor=holds back)
35
36	3. Gather Input
37	Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.
38
39	4. Discuss and Prioritize
40	Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.
41
42	5. Define Action Items
43	Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like "communicate better."
44
45	6. Review Previous Actions
46	Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.
47
48	7. Document for Future Reference
49	Capture the key points so they're available for future team members and for tracking patterns over time.
50
51	## Output Format
52
53	Use the template in `references/TEMPLATE.md` to structure the output. A complete retrospective fills every template section: Overview; Previous Retrospective Review; What Went Well; What to Improve; Discussion Notes; Action Items; Parking Lot; Metrics and Trends; Facilitator Notes; and Next Retrospective.
54
55	## Quality Checklist
56
57	Before finalizing, verify:
58
59	- [ ] All attendees had opportunity to contribute
60	- [ ] Both positives and improvements are captured
61	- [ ] Action items have owners and due dates
62	- [ ] Previous retrospective actions are reviewed
63	- [ ] A reader who missed the retro can tell what was decided and who owns each action from this document alone
64
65	## Examples
66
67	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type

iterate-retrospective

486stars64forks

View on GitHub

How to install iterate-retrospective?

product-on-purpose/pm-skills/iterate-retrospective

$npx -y skills add product-on-purpose/pm-skills --skill iterate-retrospective

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2	# Retrospective
3
4	A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.
5
6	## When to Use
7
8	- At the end of every sprint (for agile teams)
9	- After completing a significant project or milestone
10	- Following a major incident or outage
11	- When team dynamics feel off and need addressing
12	- At regular intervals (monthly, quarterly) even without specific triggers
13	- When onboarding new team members to establish improvement culture
14
15	## When NOT to Use
16
17	- You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it
18	- You are scoring an OKR cycle at close -> use `measure-okr-grader`
19	- The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision`
20	- You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap`
21
22	## Instructions
23
24	When asked to facilitate or document a retrospective, follow these steps:
25
26	1. Set the Context
27	Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.
28
29	2. Choose a Format
30	Select a retrospective format that fits the team's needs. Common options include:
31	- Start/Stop/Continue: Simple and direct
32	- 4Ls: Liked, Learned, Lacked, Longed for
33	- Mad/Sad/Glad: Emotion-focused
34	- Sailboat: Visual metaphor (wind=helps, anchor=holds back)
35
36	3. Gather Input
37	Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.
38
39	4. Discuss and Prioritize
40	Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.
41
42	5. Define Action Items
43	Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like "communicate better."
44
45	6. Review Previous Actions
46	Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.
47
48	7. Document for Future Reference
49	Capture the key points so they're available for future team members and for tracking patterns over time.
50
51	## Output Format
52
53	Use the template in `references/TEMPLATE.md` to structure the output. A complete retrospective fills every template section: Overview; Previous Retrospective Review; What Went Well; What to Improve; Discussion Notes; Action Items; Parking Lot; Metrics and Trends; Facilitator Notes; and Next Retrospective.
54
55	## Quality Checklist
56
57	Before finalizing, verify:
58
59	- [ ] All attendees had opportunity to contribute
60	- [ ] Both positives and improvements are captured
61	- [ ] Action items have owners and due dates
62	- [ ] Previous retrospective actions are reviewed
63	- [ ] A reader who missed the retro can tell what was decided and who owns each action from this document alone
64
65	## Examples
66
67	See `references/EXAMPLE.md` for a completed example.

People who liked this also viewed

6 picks

Type