Back to Details

pmo-retrospective

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

PMO Retrospective Skill

PMO回顾技能

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

类型1：项目收尾回顾

Trigger: Project completion or termination Scope: Single project Participants: Project team, sponsor, key stakeholders
触发条件： 项目完成或终止 范围： 单个项目 参与人员： 项目团队、发起人、关键干系人

Type 2: Portfolio Period Review

类型2：项目组合周期评审

Trigger: Quarterly or annual review Scope: All projects in period Participants: PMO, project managers, executives
触发条件： 季度或年度评审 范围： 周期内所有项目 参与人员： PMO、项目经理、高管

Type 3: Thematic Retrospective

类型3：主题式回顾

Trigger: Recurring pattern observed Scope: Projects sharing the pattern Participants: Affected project managers, PMO, subject matter experts
触发条件： 发现重复出现的模式 范围： 存在该模式的项目 参与人员： 受影响的项目经理、PMO、主题专家

Retrospective Gates

回顾阶段门

Gate 1: Context Setting

阶段门1：环境设定

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:
ElementValue
TypeProject/Portfolio/Thematic
Scope[Projects/Period]
Participants[List]
Data Sources[List]
Output: 
docs/pmo/{date}/retro-context.md
目标： 确定回顾的范围和参与人员
行动：
  1. 定义回顾类型和范围
  2. 确定参与人员
  3. 收集项目数据
  4. 安排会议时间
环境模板：
元素值
类型项目/项目组合/主题式
范围[项目/周期]
参与人员[列表]
数据来源[列表]
输出： 
docs/pmo/{date}/retro-context.md

Gate 2: Data Collection

阶段门2：数据收集

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:
CategoryData
SchedulePlanned vs actual duration
CostBudget vs actual spend
ScopeBaseline vs final scope
QualityDefects, rework
RisksRisks that materialized
ChangesNumber and impact
Output: 
docs/pmo/{date}/retro-data.md
目标： 收集关于绩效的客观数据
行动：
  1. 收集最终项目指标
  2. 收集偏差说明
  3. 记录范围变更
  4. 整理风险/问题历史
数据点：
类别数据
进度计划 vs 实际工期
成本预算 vs 实际支出
范围基准 vs 最终范围
质量缺陷、返工
风险已发生的风险
变更数量及影响
输出： 
docs/pmo/{date}/retro-data.md

Gate 3: Reflection

阶段门3：反思

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:
CategoryQuestion
What went well?What should we keep doing?
What didn't go well?What should we stop doing?
What was confusing?What needs clarification?
What was missing?What should we start doing?
What surprised us?What assumptions were wrong?
Output: 
docs/pmo/{date}/retro-reflection.md
目标： 识别有效做法、失效做法及其原因
行动：
  1. 开展回顾会议
  2. 识别可复用的成功经验
  3. 识别需避免的失败案例
  4. 分析根本原因
反思框架：
类别问题
哪些做得好？我们应该坚持做什么？
哪些做得不好？我们应该停止做什么？
哪些地方令人困惑？哪些内容需要澄清？
哪些东西缺失了？我们应该开始做什么？
哪些情况出乎预料？哪些假设是错误的？
输出： 
docs/pmo/{date}/retro-reflection.md

Gate 4: Pattern Analysis

阶段门4：模式分析

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:
TypeIndicatorAction
SystemicSame issue in 3+ projectsProcess change required
CapabilitySame team struggle repeatingTraining/hiring needed
ToolTool-related frictionTool improvement/replacement
CommunicationStakeholder issues recurringCommunication improvement
EstimationConsistent over/under estimationEstimation process improvement
Output: 
docs/pmo/{date}/retro-patterns.md
目标： 识别跨项目/跨时间的模式
行动：
  1. 与过往回顾结果对比
  2. 识别重复出现的主题
  3. 评估系统性问题 vs 孤立问题
  4. 优先排序改进领域
模式类型：
类型指标行动
系统性3个以上项目存在相同问题需要变更流程
能力型同一团队反复遇到相同困难需要培训/招聘
工具型工具相关的摩擦需要改进/替换工具
沟通型干系人问题重复出现需要改进沟通
估算型持续高估/低估需要改进估算流程
输出： 
docs/pmo/{date}/retro-patterns.md

Gate 5: Action Planning

阶段门5：行动计划

Objective: Create actionable improvement plan
Actions:
  1. Define specific improvements
  2. Assign owners
  3. Set timelines
  4. Define success criteria
Action Template:
ImprovementOwnerTimelineSuccess CriteriaStatus
[Improvement][Owner][Date][Criteria][Status]
Priority Framework:
Impact / EffortLow EffortHigh Effort
High ImpactDo FirstPlan Carefully
Low ImpactQuick WinsDon't Do
Output: 
docs/pmo/{date}/retro-actions.md
目标： 创建可落地的改进计划
行动：
  1. 定义具体改进措施
  2. 分配负责人
  3. 设置时间线
  4. 定义成功标准
行动模板：
改进措施负责人时间线成功标准状态
[改进措施][负责人][日期][标准][状态]
优先级框架：
影响/投入低投入高投入
高影响优先执行仔细规划
低影响快速取胜无需执行
输出： 
docs/pmo/{date}/retro-actions.md

Gate 6: Knowledge Sharing

阶段门6：知识共享

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:
ChannelAudienceContent
PMO WikiAll PMsFull lessons
NewsletterOrganizationSummary
TrainingNew PMsIncorporated
TemplatesAll projectsUpdated
PlaybooksSpecific scenariosDetailed guidance
Output: 
docs/pmo/{date}/lessons-learned.md
目标： 向全组织分发经验教训
行动：
  1. 记录经验教训
  2. 更新PMO知识库
  3. 向相关团队展示
  4. 更新模板/流程
知识共享渠道：
渠道受众内容
PMO Wiki所有项目经理完整经验教训
通讯稿全组织摘要
培训新任项目经理融入培训内容
模板所有项目更新后的模板
操作手册特定场景详细指导
输出： 
docs/pmo/{date}/lessons-learned.md

Anti-Rationalization Table

反合理化说明表

See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
通用反合理化说明请参考shared-patterns/anti-rationalization.md。

Retrospective-Specific Anti-Rationalizations

回顾特有的反合理化说明

RationalizationWhy It's WRONGRequired Action
"We're too busy for retrospectives"Learning gaps cost more than retrospective time.Schedule and conduct retrospective
"We know what went wrong"Assumptions miss root causes.Formal analysis required
"It was a unique situation"Patterns hide in "unique" situations.Document and compare
"People will be defensive"Blame-free culture enables learning.Focus on process, not people
"Lessons will be ignored anyway"Track action completion to ensure learning.Follow up on actions
合理化借口错误原因要求行动
"我们太忙了，没时间做回顾"学习缺口造成的损失远大于回顾所需时间。安排并开展回顾
"我们知道哪里出了问题"主观假设会遗漏根本原因。需要开展正式分析
"这是个独特的情况"模式往往隐藏在“独特”情况中。记录并进行对比
"人们会有抵触情绪"无指责文化才能促进学习。聚焦流程而非个人
"经验教训反正会被忽略"跟踪行动完成情况以确保学习落地。跟进行动执行

Pressure Resistance

抗压指南

See shared-patterns/pressure-resistance.md for universal pressure scenarios.
通用压力场景请参考shared-patterns/pressure-resistance.md。

Retrospective-Specific Pressures

回顾特有的压力场景

Pressure TypeRequestAgent Response
"Skip retro, team already on next project""Learning before moving on prevents repeating mistakes. Conducting abbreviated retrospective."
"Don't document that failure""Failures are learning opportunities. Documenting with constructive framing."
"Just move on, it's in the past""Past informs future. Retrospective protects future projects."
压力类型请求Agent回应
"跳过回顾，团队已经投入下一个项目了""在进入下一个项目前完成学习，可避免重复犯错。将开展简化版回顾。"
"不要记录那次失败""失败是学习的机会。将以建设性框架记录该内容。"
"别管了，都过去了""过去的经验指导未来。回顾能为未来项目保驾护航。"

Blocker Criteria - STOP and Report

阻塞判定标准 - 停止并上报

ALWAYS pause and report blocker for:
SituationRequired Action
Key participants unavailableSTOP. Incomplete retrospective misses perspectives. Reschedule.
Data unavailableSTOP. Data-free retrospective is opinion session. Get data.
Blame culture emergingSTOP. Reset to blameless framework. Not about individuals.
No action ownershipSTOP. Lessons without owners become forgotten. Assign owners.
在以下情况中，请务必暂停并上报阻塞：
场景要求行动
关键参与人员无法参与停止。不完整的回顾会缺失关键视角。重新安排时间。
数据无法获取停止。无数据的回顾只是主观意见交流会。获取数据后再进行。
出现指责文化停止。重置为无指责框架。聚焦流程而非个人。
无人负责行动停止。无负责人的经验教训会被遗忘。分配负责人。

Output Format

输出格式

Lessons Learned Report

经验教训报告

markdown
undefined
markdown
undefined

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

经验教训 - [项目/周期] - [日期]

Context

环境信息

ElementValue
Scope[Project(s)/Period]
Participants[List]
Facilitator[Name]
元素值
范围[项目/周期]
参与人员[列表]
主持人[姓名]

Performance Summary

绩效总结

MetricTargetActualVariance
DurationX monthsX months+/- X%
Budget$X$X+/- X%
ScopeX featuresX features+/- X
QualityX defectsX defects+/- X
指标目标实际偏差
工期X个月X个月+/- X%
预算$X$X+/- X%
范围X个功能X个功能+/- X
质量X个缺陷X个缺陷+/- X

What Went Well

做得好的方面

SuccessWhy It WorkedHow to Repeat
[Success][Root cause][Action to sustain]
成功点成功原因复用方式
[成功点][根本原因][持续执行的行动]

What Didn't Go Well

待改进的方面

IssueRoot CauseHow to Prevent
[Issue][Root cause][Action to prevent]
问题根本原因预防措施
[问题][根本原因][预防行动]

Patterns Identified

识别到的模式

PatternFrequencySystemic?Action
[Pattern]X occurrencesYes/No[Action]
模式出现频率是否系统性？行动
[模式]X次是/否[行动]

Improvement Actions

改进行动

#ImprovementOwnerDueStatus
1[Improvement][Owner][Date][Status]
#改进措施负责人截止日期状态
1[改进措施][负责人][日期][状态]

Key Lessons (Top 5)

核心经验（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]
  1. [经验标题]: [描述及应用指导]
  2. [经验标题]: [描述及应用指导]
  3. [经验标题]: [描述及应用指导]
  4. [经验标题]: [描述及应用指导]
  5. [经验标题]: [描述及应用指导]

Knowledge Sharing Plan

知识共享计划

AudienceChannelDateOwner
[Audience][Channel][Date][Owner]

---
受众渠道日期负责人
[受众][渠道][日期][负责人]

---

Execution Report

执行报告

Base metrics per shared-patterns/execution-report.md:
MetricValue
Analysis DateYYYY-MM-DD
Scope[Project(s)/Period]
DurationXh Ym
ResultCOMPLETE/PARTIAL/BLOCKED
基础指标请参考shared-patterns/execution-report.md:
指标值
分析日期YYYY-MM-DD
范围[项目/周期]
时长X小时 Y分钟
结果完成/部分完成/阻塞

Retrospective-Specific Details

回顾特有的详细指标

MetricValue
period_covered[Description]
projects_completedN
lessons_capturedN
process_improvementsN
指标值
period_covered[描述]
projects_completedN
lessons_capturedN
process_improvementsN
undefined