Portfolio retrospective skill for capturing lessons learned, process improvements, and organizational learning across completed projects.
View on GitHubSelect agents to install to:
npx add-skill https://github.com/LerianStudio/ring/blob/main/pmo-team/skills/pmo-retrospective/SKILL.md -a claude-code --skill pmo-retrospectiveInstallation paths:
.claude/skills/pmo-retrospective/# PMO Retrospective Skill
Systematic capture and application of lessons learned at portfolio level.
## Purpose
This skill provides a framework for:
- Lessons learned capture
- Pattern identification
- Process improvement
- Organizational learning
- Knowledge transfer
---
## Retrospective Types
### Type 1: Project Closure Retrospective
**Trigger:** Project completion or termination
**Scope:** Single project
**Participants:** Project team, sponsor, key stakeholders
---
### Type 2: Portfolio Period Review
**Trigger:** Quarterly or annual review
**Scope:** All projects in period
**Participants:** PMO, project managers, executives
---
### Type 3: Thematic Retrospective
**Trigger:** Recurring pattern observed
**Scope:** Projects sharing the pattern
**Participants:** Affected project managers, PMO, subject matter experts
---
## Retrospective Gates
### Gate 1: Context Setting
**Objective:** Establish retrospective scope and participants
**Actions:**
1. Define retrospective type and scope
2. Identify participants
3. Gather project data
4. Schedule sessions
**Context Template:**
| Element | Value |
|---------|-------|
| Type | Project/Portfolio/Thematic |
| Scope | [Projects/Period] |
| Participants | [List] |
| Data Sources | [List] |
**Output:** `docs/pmo/{date}/retro-context.md`
---
### Gate 2: Data Collection
**Objective:** Gather objective data about performance
**Actions:**
1. Collect final project metrics
2. Gather variance explanations
3. Document scope changes
4. Compile risk/issue history
**Data Points:**
| Category | Data |
|----------|------|
| Schedule | Planned vs actual duration |
| Cost | Budget vs actual spend |
| Scope | Baseline vs final scope |
| Quality | Defects, rework |
| Risks | Risks that materialized |
| Changes | Number and impact |
**Output:** `docs/pmo/{date}/retro-data.md`
---
### Gate 3: Reflection
**Objective:** Identify what worked, what didn't, and why
**Actions:**
1. Conduct retrospective session
2. Identify