- name
- sprint-planning
- description
- Facilitate a sprint planning session for the DreamTeam. Use when someone says "sprint planning", "plan the sprint", "what goes in the next sprint?", or "let's plan sprint [N]". Runs the full sprint planning ceremony following DreamTeam protocols: backlog review, capacity check, goal setting, and task assignment with RACI.
# Sprint Planning Facilitator
Run a DreamTeam sprint planning session (1-2 hours).
## Pre-Planning Checklist
Before starting, ensure:
- [ ] Backlog is refined and prioritised (PO responsibility)
- [ ] Team capacity is known (Project Manager)
- [ ] Previous sprint retrospective actions noted
- [ ] Any carry-over tasks from last sprint identified
## Sprint Planning Steps
### Step 1: Sprint Goal (15 min)
- PM/PO presents the **sprint goal** — one sentence describing the theme
- Team agrees on the goal
- Goal should be: specific, measurable, achievable in one sprint
### Step 2: Capacity Planning (10 min)
Calculate team capacity:
```
Sprint days: [N days]
Team members: list each + availability %
Total capacity = Σ (available_days × story_points_per_day)
Recommended load: 80% of capacity (buffer for unexpected work)
```
### Step 3: Backlog Review (30 min)
For each candidate story from the backlog:
1. PO reads the story + acceptance criteria
2. Team asks clarifying questions (max 5 min per story)
3. Developer gives effort estimate (Fibonacci: 1, 2, 3, 5, 8, 13)
4. Team votes to include or defer based on:
- Fits sprint goal?
- Estimated effort fits capacity?
- Dependencies resolved?
- AC clear enough to implement?
### Step 4: RACI Assignment (15 min)
For each accepted story, assign:
| Field | Assignment |
|---|---|
| **Responsible** | Developer / Designer / QA who does the work |
| **Accountable** | PO (features) / PM (cross-cutting) |
| **Consulted** | Designer for UX tasks, QA for test-heavy tasks |
| **Informed** | CPO, PM, CSM as needed |
### Step 5: Task Breakdown (20 min)
Break each story into tasks:
- Design task (UX Designer)
- Implementation task(s) (Developer)
- Test task (QA Specialist)
- Review/demo task (PO)
### Step 6: Sprint Board Setup
Update Kanboard:
- Move selected stories to sprint backlog column
- Assign owners to all tasks
- Set due dates within sprint window
- Add RACI tags to each task
## Sprint Planning Output
```
🚀 SPRINT [N] PLAN
Period: [Start Date] → [End Date]
🎯 SPRINT GOAL:
[One sentence goal]
📊 CAPACITY:
Total available: [N] story points
Committed: [N] story points ([X]% of capacity)
📋 SPRINT BACKLOG:
[Story title] — [X pts] — R:[role] A:[role]
→ Task: [description] — Owner: [role]
→ Task: [description] — Owner: [role]
...
⚠️ RISKS & DEPENDENCIES:
- [Risk/dependency] → Mitigation: [action]
✅ SPRINT GOAL AGREED: Yes / Pending
```
## Rules
- No story enters the sprint without clear AC
- No story larger than 8 points (must be broken down)
- QA must be assigned to every story
- RACI must be set before sprint starts
Auf GitHub ansehen