Skip to content

borghei/Claude-Skills / project-management/scrum-master

scrum-master

Verified

Scores 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.

assets/sprint_plan_template.md

View on GitHub
# Sprint [NUMBER] Plan - [SPRINT_NAME]

**Team:** [TEAM_NAME]
**Scrum Master:** [SCRUM_MASTER_NAME]
**Product Owner:** [PRODUCT_OWNER_NAME]
**Sprint Period:** [START_DATE] to [END_DATE]
**Sprint Length:** [DAYS] working days
**Planning Date:** [PLANNING_DATE]

---

## Sprint Goal

> [One clear, concise statement of what the team aims to achieve this sprint. Should follow SMART format and align with product goals.]

### Success Criteria
- [ ] [MEASURABLE_CRITERION_1]
- [ ] [MEASURABLE_CRITERION_2]
- [ ] [MEASURABLE_CRITERION_3]

### Product Goal Alignment
**Product Goal:** [PRODUCT_GOAL_OR_OKR]
**How This Sprint Contributes:** [BRIEF_EXPLANATION]

---

## Team Capacity Summary

### Team Availability
| Member | Role | Available Days | PTO Days | Working Days | Allocation% | Net Hours |
|--------|------|---------------|----------|-------------|-------------|-----------|
| [NAME_1] | [ROLE_1] | [DAYS] | [PTO] | [WORKING] | [ALLOC]% | [HOURS]h |
| [NAME_2] | [ROLE_2] | [DAYS] | [PTO] | [WORKING] | [ALLOC]% | [HOURS]h |
| [NAME_3] | [ROLE_3] | [DAYS] | [PTO] | [WORKING] | [ALLOC]% | [HOURS]h |
| [NAME_4] | [ROLE_4] | [DAYS] | [PTO] | [WORKING] | [ALLOC]% | [HOURS]h |
| [NAME_5] | [ROLE_5] | [DAYS] | [PTO] | [WORKING] | [ALLOC]% | [HOURS]h |
| **TOTAL** | | | | | | **[TOTAL]h** |

### Capacity Allocation Breakdown
| Category | Hours | Percentage |
|----------|-------|------------|
| Total Gross Hours | [GROSS]h | 100% |
| Ceremony Overhead | -[CEREMONY]h | [CERE_PCT]% |
| Net Available Hours | [NET]h | [NET_PCT]% |
| Focus Factor (80%) | -[FOCUS_DEDUCT]h | [FOCUS_PCT]% |
| **Realistic Capacity** | **[REALISTIC]h** | **[REAL_PCT]%** |

### Velocity Reference
| Metric | Value |
|--------|-------|
| Last Sprint Velocity | [LAST_VELOCITY] points |
| 3-Sprint Rolling Average | [AVG_3] points |
| 5-Sprint Rolling Average | [AVG_5] points |
| Velocity Trend | [IMPROVING/STABLE/DECLINING] |
| **Forecasted Velocity** | **[FORECAST] points** |

---

## Committed Stories

| Priority | Story ID | Title | Points | Owner | Status |
|----------|----------|-------|--------|-------|--------|
| 1 | [ID_1] | [TITLE_1] | [PTS_1] | [OWNER_1] | Not Started |
| 2 | [ID_2] | [TITLE_2] | [PTS_2] | [OWNER_2] | Not Started |
| 3 | [ID_3] | [TITLE_3] | [PTS_3] | [OWNER_3] | Not Started |
| 4 | [ID_4] | [TITLE_4] | [PTS_4] | [OWNER_4] | Not Started |
| 5 | [ID_5] | [TITLE_5] | [PTS_5] | [OWNER_5] | Not Started |
| 6 | [ID_6] | [TITLE_6] | [PTS_6] | [OWNER_6] | Not Started |
| | | **TOTAL** | **[TOTAL_PTS]** | | |

### Carry-Over from Previous Sprint
| Story ID | Title | Points | Remaining Work | Reason for Carry-Over |
|----------|-------|--------|---------------|----------------------|
| [ID] | [TITLE] | [PTS] | [REMAINING] | [REASON] |

---

## Stretch Goals

*These stories will be pulled in only if the team completes all committed work early. They are NOT part of the sprint commitment.*

| Story ID | Title | Points | Prerequisites |
|----------|-------|--------|---------------|
| [ID_S1] | [TITLE_S1] | [PTS_S1] | [PREREQ_S1] |
| [ID_S2] | [TITLE_S2] | [PTS_S2] | [PREREQ_S2] |

---

## Dependencies

### Internal Dependencies (Within This Sprint)
| Story | Depends On | Type | Notes |
|-------|-----------|------|-------|
| [STORY_A] | [STORY_B] | Must finish first | [NOTES] |
| [STORY_C] | [STORY_D] | Shared component | [NOTES] |

### External Dependencies (Outside the Team)
| Dependency | Provider Team/Person | Expected Date | Status | Contingency |
|------------|---------------------|---------------|--------|-------------|
| [DEP_1] | [PROVIDER_1] | [DATE_1] | [STATUS_1] | [CONTINGENCY_1] |
| [DEP_2] | [PROVIDER_2] | [DATE_2] | [STATUS_2] | [CONTINGENCY_2] |

---

## Risks

| Risk | Probability | Impact | Mitigation | Owner |
|------|-------------|--------|------------|-------|
| [RISK_1] | [High/Med/Low] | [High/Med/Low] | [MITIGATION_1] | [OWNER_1] |
| [RISK_2] | [High/Med/Low] | [High/Med/Low] | [MITIGATION_2] | [OWNER_2] |
| [RISK_3] | [High/Med/Low] | [High/Med/Low] | [MITIGATION_3] | [OWNER_3] |

---

## Sprint Calendar

### Ceremony Schedule
| Day | Date | Ceremony | Time | Duration | Notes |
|-----|------|----------|------|----------|-------|
| Day 1 | [DATE] | Sprint Planning | [TIME] | 2h | Kick-off |
| Day 1 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 2 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 3 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 4 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 5 | [DATE] | Daily Standup | [TIME] | 15min | Mid-sprint check |
| Day 6 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 7 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 8 | [DATE] | Backlog Refinement | [TIME] | 1h | Next sprint prep |
| Day 8 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 9 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 10 | [DATE] | Daily Standup | [TIME] | 15min | |
| Day 10 | [DATE] | Sprint Review | [TIME] | 1h | Demo to stakeholders |
| Day 10 | [DATE] | Sprint Retrospective | [TIME] | 1h | Team improvement |

### Key Dates
- **Mid-Sprint Check:** [DATE] - Assess progress against sprint goal
- **Code Freeze:** [DATE] (if applicable)
- **QA Window:** [START_DATE] to [END_DATE]
- **Release Date:** [DATE] (if applicable)

### Team PTO / Out-of-Office
| Member | Dates | Notes |
|--------|-------|-------|
| [NAME] | [DATES] | [NOTES] |

---

## Definition of Done Reminder

Every story must meet the Definition of Done before it is considered complete:

- [ ] Code is written and follows team coding standards
- [ ] Unit tests written and passing
- [ ] Code reviewed and approved by at least one peer
- [ ] Integration tests passing
- [ ] Documentation updated (if applicable)
- [ ] Acceptance criteria verified by Product Owner
- [ ] No known defects or regressions
- [ ] Deployed to staging environment

---

## Notes from Sprint Planning

### Decisions Made
- [DECISION_1]
- [DECISION_2]

### Open Questions
| Question | Owner | Due Date |
|----------|-------|----------|
| [QUESTION_1] | [OWNER_1] | [DATE_1] |
| [QUESTION_2] | [OWNER_2] | [DATE_2] |

### Parking Lot Items
- [ITEM_1] - To be discussed in [MEETING/CHANNEL]
- [ITEM_2] - Deferred to next refinement

---

**Plan created by:** [SCRUM_MASTER_NAME]
**Plan confirmed by team:** [YES/NO] on [DATE]
**Distribution:** Development Team, Product Owner, Stakeholders

---
*Use this plan as the single source of truth for the sprint. Update story status daily. Review capacity and progress at mid-sprint. Refer to the sprint goal when making scope decisions.*
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall
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: 108kUpdated Claude CodeCodexVerifiedInstall