What kind of data does this skill collect?

The skill guides the collection of objective metrics including schedule variance, budget performance, scope changes, defect rates, and risk history to ensure the retrospective is data-driven rather than opinion-based.

What are the primary outputs of a PMO Retrospective session?

The skill generates a suite of documentation including a Context Report, Data Analysis, Pattern Identifications, an Action Plan with assigned owners, and a final Lessons Learned report.

Can this skill help if our organization has a blame culture?

Yes. It includes specific blocker criteria and frameworks designed to reset the environment to a blameless, process-focused perspective, ensuring that the focus remains on organizational learning.

How does this differ from a standard sprint retrospective?

While sprint retrospectives focus on team-level improvements within a single cycle, the PMO Retrospective skill is designed for portfolio-level analysis, project closures, and identifying systemic patterns across multiple teams or long time periods.

PMO Retrospective

Name: PMO Retrospective
Author: LerianStudio

byLerianStudio

•

コラボレーションツール

Facilitates systematic portfolio-level retrospectives to capture lessons learned and drive organizational process improvements.

The PMO Retrospective skill provides a rigorous framework for conducting high-level reviews across completed projects and portfolio periods. It transforms project experiences into institutional knowledge by guiding users through structured gates—from data collection and reflection to pattern analysis and action planning. By focusing on systemic issues rather than individual project incidents, this skill helps organizations identify recurring bottlenecks, optimize workflows, and ensure that successes are repeatable across the entire enterprise.

主な機能

01Priority-based action planning using impact and effort frameworks

02Automated generation of comprehensive Lessons Learned reports

03Standardized six-gate workflow from context setting to knowledge sharing

0448 GitHub stars

05Cross-project pattern analysis to identify systemic vs. isolated issues

06Built-in anti-rationalization checks to ensure objective analysis

ユースケース

01Capturing institutional knowledge during formal project closure or termination

02Conducting quarterly or annual portfolio reviews to assess organizational performance

03Analyzing recurring patterns across multiple projects to implement process improvements

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lerianstudio/ring pmo-retrospective

For use in Claude.ai and ChatGPT

Download Skill