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:

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:

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 successes to repeat
3. Identify failures to prevent
4. Analyze root causes

Reflection Framework:

Output: docs/pmo/{date}/retro-reflection.md

Gate 4: Pattern Analysis

Objective: Identify patterns across projects/time

Actions:

1. Compare with previous retrospectives
2. Identify recurring themes
3. Assess systemic vs isolated issues
4. Prioritize improvement areas

Pattern Types:

Output: docs/pmo/{date}/retro-patterns.md

Gate 5: Action Planning

Objective: Create actionable improvement plan

Actions:

1. Define specific improvements
2. Assign owners
3. Set timelines
4. Define success criteria

Action Template:

Priority Framework:

Output: docs/pmo/{date}/retro-actions.md

Gate 6: Knowledge Sharing

Objective: Distribute lessons to organization

Actions:

1. Document lessons learned
2. Update PMO knowledge base
3. Present to relevant teams
4. Update templates/processes

Knowledge Sharing Channels:

Output: docs/pmo/{date}/lessons-learned.md

Anti-Rationalization Table

See shared-patterns/anti-rationalization.md for universal anti-rationalizations.

Retrospective-Specific Anti-Rationalizations

Pressure Resistance

See shared-patterns/pressure-resistance.md for universal pressure scenarios.

Retrospective-Specific Pressures

Blocker Criteria - STOP and Report

ALWAYS pause and report blocker for:

Cannot Be Overridden

The following requirements are NON-NEGOTIABLE:

If user insists on violating these:

1. Escalate to orchestrator
2. Do NOT proceed with incomplete retrospective
3. Document the request and your refusal

Severity Calibration

When assessing retrospective findings:

Document ALL severities. Prioritize action on CRITICAL and HIGH.

Output Format

Lessons Learned Report

# Lessons Learned - [Project/Period] - [Date]

## Context

| Element | Value |
|---------|-------|
| Scope | [Project(s)/Period] |
| Participants | [List] |
| Facilitator | [Name] |

## Performance Summary

| Metric | Target | Actual | Variance |
|--------|--------|--------|----------|
| Duration | X months | X months | +/- X% |
| Budget | $X | $X | +/- X% |
| Scope | X features | X features | +/- X |
| Quality | X defects | X defects | +/- X |

## What Went Well

| Success | Why It Worked | How to Repeat |
|---------|---------------|---------------|
| [Success] | [Root cause] | [Action to sustain] |

## What Didn't Go Well

| Issue | Root Cause | How to Prevent |
|-------|------------|----------------|
| [Issue] | [Root cause] | [Action to prevent] |

## Patterns Identified

| Pattern | Frequency | Systemic? | Action |
|---------|-----------|-----------|--------|
| [Pattern] | X occurrences | Yes/No | [Action] |

## Improvement Actions

| # | Improvement | Owner | Due | Status |
|---|-------------|-------|-----|--------|
| 1 | [Improvement] | [Owner] | [Date] | [Status] |

## Key Lessons (Top 5)

1. **[Lesson Title]:** [Description and application guidance]
2. **[Lesson Title]:** [Description and application guidance]
3. **[Lesson Title]:** [Description and application guidance]
4. **[Lesson Title]:** [Description and application guidance]
5. **[Lesson Title]:** [Description and application guidance]

## Knowledge Sharing Plan

| Audience | Channel | Date | Owner |
|----------|---------|------|-------|
| [Audience] | [Channel] | [Date] | [Owner] |

Execution Report

Base metrics per shared-patterns/execution-report.md:

Retrospective-Specific Details

When Retrospective Is Not Needed

MUST: Full retrospective REQUIRED for the following conditions:

MUST: When in doubt, conduct the retrospective. Skipped retrospectives become repeated failures.