Sprint Summary: [Project Name] - Sprint [N] (YYYY-MM-DD to YYYY-MM-DD)¶
Purpose: Lightweight documentation of sprint goals, outcomes, and velocity for major projects. Delete this file when the project completes.
Sprint Goal¶
Brief description of what this sprint aimed to accomplish (1-2 sentences).
Planned vs Actual¶
Planned Work¶
- Story #123: Description (5 points)
- Story #124: Description (3 points)
- Story #125: Description (2 points)
Total Planned: 10 points
Completed Work¶
- Story #123: Description (5 points) ✅
- Story #124: Description (3 points) ✅
- Story #125: Description (2 points) - Moved to next sprint
Total Completed: 8 points
Added Work (not originally planned)¶
- Story #126: Urgent bug fix (1 point) ✅
Final Velocity: 9 points
Key Outcomes¶
What Shipped¶
- Feature X deployed to staging
- Bug fix Y deployed to production
- Technical debt Z addressed
What Changed¶
- Story #125 deferred due to dependency blocker
- Added urgent bug fix #126 mid-sprint
Blockers & Resolutions¶
| Blocker | Impact | Resolution |
|---|---|---|
| External API timeout | High - blocked Story #125 | Escalated to vendor, temporary workaround implemented |
Metrics¶
- Velocity: 9 points (planned: 10)
- Completion Rate: 80% (2 of 3 stories)
- Scope Change: +1 story added (urgent fix)
Notes for Next Sprint¶
- Continue with Story #125 (blocker should be resolved)
- Consider reducing planned capacity if interrupts continue
- Team member X on vacation next week
Related Documentation¶
- Feature Brief: [link if applicable]
- Technical Plan: [link if applicable]
- ZenHub Epic: #[epic-number]
Template Usage:
- Copy this template to
/docs/planning/{project-name}/sprint-summary-YYYY-MM-DD.md - Fill in actual sprint data
- Update after sprint review
- Delete when project completes (or archive key learnings in Feature Brief)