Sprint Velocity Analysis

Analyze sprint velocity data and produce an engineering team health report covering delivery trends, capacity utilization, and improvement recommendations. Use when asked to analyze sprint velocity, review team delivery health, identify delivery risks, or produce a retrospective data analysis. Produces a velocity trend analysis, health diagnosis table, top improvement recommendations with implementation steps, and a next-sprint capacity forecast.

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

What to give it

• Sprint history — for each sprint: sprint name/number, committed story points, completed story points, and number of items carried over to next sprint; ideally 6–8 sprints minimum
• Team size and any changes — current team size and any additions or departures during the data window
• Known disruptions — holidays, company all-hands, on-call incidents, or other events that affected specific sprints
• Cycle time data (optional) (optional) — if available, p50 and p90 cycle time per sprint (time from start to done)
• Definition of Done — what "completed" means for this team (merged to main? deployed to prod? accepted by PO?)

Related skills