Sprint Management Kit
A complete sprint management system with planning templates, standup formats, retrospective frameworks, velocity tracking, and burndown chart templates. Designed for agile product teams running 1-2 week sprints.
Key Features
- Sprint Planning Template — Structured capacity-based planning with story point allocation
- Daily Standup Formats — Multiple standup formats including async-friendly options
- Retrospective Frameworks — 5 different retro formats to keep things fresh
- Velocity Tracking — Sprint-over-sprint velocity calculator with trend analysis
- Burndown Templates — Visual progress tracking for sprints and releases
- Sprint Review Template — Demo-ready sprint review with stakeholder feedback capture
What's Included
| File | Purpose |
|---|---|
src/sprint_management_kit/core.py |
Sprint velocity and burndown calculations |
src/sprint_management_kit/utils.py |
Helper functions for sprint metrics |
templates/sprint-planning.md |
Sprint planning meeting template |
templates/daily-standup.md |
Multiple standup format options |
templates/retrospective.md |
5 retrospective framework templates |
templates/sprint-review.md |
Sprint review and demo template |
templates/velocity-tracker.md |
Velocity tracking spreadsheet |
templates/burndown-template.md |
Sprint and release burndown charts |
templates/sprint-report.md |
End-of-sprint summary for stakeholders |
docs/overview.md |
Sprint management methodology guide |
config.example.yaml |
Sprint duration, capacity, and ceremony config |
Quick Start
- Set your sprint cadence in
config.example.yaml(1 or 2 weeks recommended) - Use
templates/sprint-planning.mdfor your first planning session - Choose a standup format from
templates/daily-standup.md - Run your first retrospective using
templates/retrospective.md - Begin velocity tracking with
templates/velocity-tracker.mdafter sprint 3
Template Examples
Sprint Planning Board
SPRINT 14 — "Authentication Hardening"
Dates: Mar 23 - Apr 3, 2026
Capacity: 40 story points (5 engineers x 8 pts each)
COMMITTED (32 pts):
AUTH-301 Implement MFA enrollment flow | 8 pts | @engineer1
AUTH-302 Add session timeout configuration | 5 pts | @engineer2
AUTH-303 Password strength validator | 3 pts | @engineer3
AUTH-304 Audit log for auth events | 8 pts | @engineer4
AUTH-305 Rate limiting on login endpoint | 5 pts | @engineer5
AUTH-306 Update auth error messages | 3 pts | @engineer3
STRETCH (8 pts — only if committed work completes early):
AUTH-307 SSO configuration UI | 5 pts | unassigned
AUTH-308 Remember device option | 3 pts | unassigned
Capacity Buffer: 8 pts (20%) reserved for bugs and unplanned work
Retrospective Frameworks
FORMAT 1: Start / Stop / Continue
Start doing: [New practices to adopt]
Stop doing: [Practices that hurt the team]
Continue doing: [What is working well]
FORMAT 2: Liked / Learned / Lacked / Longed For (4Ls)
Liked: [What went well]
Learned: [New insights or skills gained]
Lacked: [What was missing]
Longed For: [What would have made it better]
FORMAT 3: Sailboat
Wind (propelling us forward): [Positive forces]
Anchor (holding us back): [Impediments]
Rocks (risks ahead): [Potential problems]
Island (our goal): [What we're sailing toward]
FORMAT 4: Mad / Sad / Glad
Mad: [Frustrations]
Sad: [Disappointments]
Glad: [Celebrations]
FORMAT 5: One Word
Each team member shares one word that describes the sprint.
Discuss patterns and outliers.
Velocity Tracker
Sprint | Committed | Completed | Velocity | Trend
-------|-----------|-----------|----------|-------
S10 | 35 pts | 32 pts | 32 | --
S11 | 38 pts | 36 pts | 36 | +4
S12 | 36 pts | 34 pts | 34 | -2
S13 | 40 pts | 38 pts | 38 | +4
S14 | 40 pts | __ pts | __ | --
Rolling Average (last 4 sprints): 35 pts
Completion Rate: 93%
Recommended next sprint capacity: 35-38 pts
Usage Guide
- Planning (day 1 of sprint): Review backlog, estimate stories, commit to sprint scope. Use capacity-based planning — never commit more than 80% of theoretical capacity.
- Daily Standups (every day): 15 minutes max. Focus on blockers, not status updates. Try async standups if your team is distributed.
- Mid-Sprint Check (mid-point): Review burndown. If behind, cut scope early — don't death-march.
- Sprint Review (last day): Demo completed work to stakeholders. Capture feedback as backlog items.
- Retrospective (last day): Rotate formats every 3-4 sprints. Limit to 3 action items. Assign owners.
Best Practices
- Velocity is descriptive, not prescriptive — use it for planning, never as a performance target
- Don't change sprint scope mid-sprint — if urgent work comes in, pull something out of equal size
- Estimate in relative points, not hours — hours create false precision; points capture relative complexity
- Carry over is a signal — if stories regularly carry over, your estimates or scope are off
- Retro action items need owners — "we should communicate better" is not an action item
- Protect the sprint — a sprint that accepts every interruption is just a to-do list with a deadline
This is 1 of 11 resources in the PM Toolkit Pro toolkit. Get the complete [Sprint Management Kit] with all files, templates, and documentation for $29.
Or grab the entire PM Toolkit Pro bundle (11 products) for $129 — save 30%.
Top comments (0)