skills.rest
staticWagomU
staticWagomUCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

scrum-event-sprint-retrospective

Guide teams through structured sprint retrospectives to surface actionable improvements.

6|Updated Dec 28, 2023
Search Tags:#agile#facilitation#root-cause-analysis#process-improvement#team-alignment#sprint-retrospective
One-click install
npx skills add https://github.com/staticWagomU/dotfiles --skill scrum-event-sprint-retrospective-staticwagomu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scrum-event-sprint-retrospective
Source: https://github.com/staticWagomU/dotfiles/tree/main/config/claude/skills/scrum-event-sprint-retrospective
Command: npx skills add https://github.com/staticWagomU/dotfiles --skill scrum-event-sprint-retrospective-staticwagomu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams through structured sprint retrospectives to surface actionable improvements that enhance value delivery, quality, and teamwork.

Core Features & Use Cases

  • Facilitated five-phase retrospective structure (Set the Stage, Gather Data, Generate Insights, Decide What to Do, Close) to ensure balanced participation and outcomes.
  • Techniques library support (Prime Directive, Timeline, 4Ls, Start/Stop/Continue, 5 Whys, Fishbone) to identify root causes and actionable improvements.
  • Action tracking and alignment with project goals by recording improvements in the team’s backlog or sprint artifacts.

Quick Start

Run a focused retrospective session using the guide to capture one concrete improvement per sprint for the next cycle.

Frequently Asked Questions about scrum-event-sprint-retrospective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a sprint retrospective to ensure actionable outcomes?▼

Structure a sprint retrospective using a five-phase format: Set the Stage, Gather Data, Generate Insights, Decide What to Do, and Close. This ensures balanced participation and surfaces concrete improvements for the next cycle.

What techniques help identify root causes during agile retrospectives?▼

Agile retrospectives use techniques like the 5 Whys and Fishbone analysis to perform root-cause analysis. Additional data gathering methods include Timeline, 4Ls, and Start/Stop/Continue to surface actionable insights.

What is the Prime Directive and when is it needed in a retrospective?▼

The Prime Directive is a facilitation principle used to set the stage in retrospectives, ensuring team alignment and a blameless environment. It is needed when gathering data and generating insights to foster balanced participation.

Can I use dot voting to prioritize process improvements in a sprint retrospective?▼

Yes, dot voting is used during the Decide What to Do phase of a sprint retrospective to prioritize process improvements. It helps teams select actionable changes that align with project goals for the next sprint.

How do I track retrospective action items for team alignment?▼

Track retrospective action items by recording improvements directly in the team’s backlog or sprint artifacts. This enforces a structured approach with clear responsibilities and aligns outcomes with team goals.

Related Skills

Explore More Software Engineering Skills→
mahg-esmahg-es
3

retrospective

Facilitate structured sprint retrospectives and generate action plans.

Official
Intermediate
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
dralgorhythmdralgorhythm
111

agile-methodology

Automate agile ceremonies and backlog management for Scrum and Kanban teams.

Community
Intermediate
dev-khoidev-khoi

kaizen

Map current state, identify TIMWOOD wastes, and standardize PDCA improvements.

Community
Advanced