borghei/Claude-Skills / project-management/scrum-master
scrum-master
VerifiedScores sprint health, forecasts velocity with Monte Carlo, analyses retros and plans capacity from sprint data. Use when facilitating sprint planning, diagnosing a velocity drop, or checking whether retro actions land.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| assets/expected_output.json | config | 3.6 KB |
| assets/expected_velocity_output.json | config | 2.0 KB |
| assets/sample_sprint_data.json | config | 24.0 KB |
| assets/sample_team_data.json | config | 1009 B |
| assets/sprint_plan_template.md | markdown | 6.4 KB |
| assets/sprint_report_template.md | markdown | 7.3 KB |
| assets/team_health_check_template.md | markdown | 9.7 KB |
| assets/user_story_template.md | markdown | 7.6 KB |
| examples/acme-sprint-health-analysis.md | markdown | 8.8 KB |
| references/metrics-troubleshooting-and-tools.md | markdown | 4.5 KB |
| references/red-flags.md | markdown | 10.3 KB |
| references/retro-formats.md | markdown | 8.0 KB |
| references/sprint-planning-guide.md | markdown | 16.7 KB |
| references/team-dynamics-framework.md | markdown | 24.0 KB |
| references/velocity-forecasting-guide.md | markdown | 13.0 KB |
| references/workflow-and-operations.md | markdown | 5.3 KB |
| scripts/retrospective_analyzer.py | script | 35.6 KB |
| scripts/sprint_capacity_calculator.py | script | 15.3 KB |
| scripts/sprint_health_scorer.py | script | 28.4 KB |
| scripts/velocity_analyzer.py | script | 21.7 KB |
references/metrics-troubleshooting-and-tools.md
View on GitHub# Key Metrics, Troubleshooting, Success Criteria & Tool Reference
Read this when setting team targets, diagnosing a sprint-analytics problem, checking whether coaching met its bar, or looking up the exact flags for any of the four Python tools.
## Key Metrics & Targets
| Metric | Target | Measurement |
|--------|--------|-------------|
| Health Score | >80/100 | Sprint-level, 6 dimensions |
| Velocity Predictability (CV) | <20% | Rolling 6-sprint window |
| Commitment Reliability | >85% | Sprint goals achieved / attempted |
| Scope Stability | <15% change | Mid-sprint scope changes |
| Blocker Resolution | <3 days avg | Time from raised to resolved |
| Action Item Completion | >70% | Retro items done by next retro |
| Ceremony Engagement | >90% | Attendance + participation quality |
| Psychological Safety | >4.0/5.0 | Monthly pulse survey |
## Troubleshooting
| Symptom | Likely Cause | Resolution |
|---------|-------------|------------|
| Velocity drops for 2+ sprints without team change | Hidden scope creep, unclear definition of done, or tech debt accumulation | Run `sprint_health_scorer.py` to check scope stability score; tighten DoD and refinement process |
| CV exceeds 30% despite stable team | Inconsistent story sizing, mid-sprint scope injection, or unplanned absences | Analyze anomalies via `velocity_analyzer.py`; introduce reference stories for estimation calibration |
| Action item completion rate below 50% | Too many action items per retro, no owners assigned, or unrealistic scope | Cap new items at 2-3 per retro based on `retrospective_analyzer.py` historical completion data |
| Health score below 60 but team feels productive | Dimension weights may not match team context, or ceremony data is incomplete | Review dimension weights in HEALTH_DIMENSIONS config; ensure ceremony attendance data is populated |
| Monte Carlo forecast has wide confidence intervals | Insufficient historical data or high velocity volatility | Accumulate 6+ sprints of data; address root causes of volatility before relying on forecasts |
| Sprint capacity calculator overestimates | Focus factor set too high or ceremony overhead not calibrated | Adjust focus factor from 0.85 to 0.80; verify ceremony durations match actual team practices |
| Retrospective themes keep recurring across sprints | Systemic issues not addressed at root cause, or action items too superficial | Use `retrospective_analyzer.py` persistent issue detection; escalate recurring themes to management |
## Success Criteria
- Sprint health score consistently above 80/100 across 6-dimension assessment
- Velocity coefficient of variation (CV) maintained below 20% over rolling 6-sprint window
- Sprint commitment reliability exceeds 85% (completed vs. planned points)
- Action item completion rate from retrospectives exceeds 70% by next retro
- Blocker average resolution time under 3 working days
- Team maturity advances at least one Tuckman stage within 3-6 months of coaching
- Psychological safety score on Edmondson scale exceeds 4.0/5.0
## Tool Reference
### velocity_analyzer.py
Analyzes sprint velocity data with trend detection, Monte Carlo forecasting, and anomaly identification.
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `data_file` | positional | (required) | Path to JSON file containing sprint data |
| `--format` | choice | `text` | Output format: `text` or `json` |
### sprint_health_scorer.py
Scores sprint health across 6 weighted dimensions with composite grading and recommendations.
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `data_file` | positional | (required) | Path to JSON file containing sprint health data |
| `--format` | choice | `text` | Output format: `text` or `json` |
### retrospective_analyzer.py
Processes retrospective data to track action item completion, identify recurring themes, and assess team maturity.
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `data_file` | positional | (required) | Path to JSON file containing retrospective data |
| `--format` | choice | `text` | Output format: `text` or `json` |
### sprint_capacity_calculator.py
Calculates sprint capacity accounting for ceremony overhead, PTO, allocation percentages, and focus factor.
| Flag | Type | Default | Description |
|------|------|---------|-------------|
| `data_file` | positional | (optional) | Path to JSON file containing team capacity data |
| `--format` | choice | `text` | Output format: `text` or `json` |
| `--demo` | flag | off | Run with built-in sample data |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |