← Back to all products
$29
Sprint Management Kit
Sprint planning templates, standup formats, retrospective frameworks, velocity tracking, and burndown chart generators.
Markdown
📄 Product Preview
Try the interactive reader and demo tools below, or get the full product with all content unlocked.
📖 Interactive Reader (Free Preview) ⚙ Try Demo Tools 📦 Download Free Sample📁 File Structure 24 files
sprint-management-kit/
├── LICENSE
├── README.md
├── free-sample.zip
├── guide/
│ ├── 01_agile-ceremonies-guide.md
│ ├── 02_sprint-management-kit.md
│ └── 03_what-s-inside.md
├── guides/
│ └── agile-ceremonies-guide.md
├── index.html
├── retrospectives/
│ ├── four-ls.md
│ ├── mad-sad-glad.md
│ ├── sailboat.md
│ ├── start-stop-continue.md
│ ├── timeline-retro.md
│ └── what-went-well.md
├── spreadsheets/
│ ├── burndown-data.csv
│ └── velocity-tracker.csv
├── standup-formats/
│ ├── async-standup.md
│ ├── classic-three-questions.md
│ ├── focus-and-blockers.md
│ └── walk-the-board.md
└── templates/
├── definition-of-done.md
├── definition-of-ready.md
├── sprint-planning.md
└── sprint-review.md
📖 Documentation Preview README excerpt
Sprint Management Kit
PM Toolkit Pro | $29
Everything a technical PM or scrum master needs to run effective sprints. Includes sprint planning templates, four standup formats (including async), six retrospective frameworks, velocity tracking and burndown spreadsheets, definition-of-done and definition-of-ready templates, and a comprehensive agile ceremonies guide.
What's Inside
Sprint Templates (`templates/`)
| Template | Purpose |
|---|---|
sprint-planning.md | Sprint planning meeting template with capacity calculation, goal setting, and story breakdown |
sprint-review.md | Sprint review/demo template with stakeholder feedback capture and metrics |
definition-of-done.md | Team-level DoD checklist covering code, testing, docs, and deployment |
definition-of-ready.md | Story readiness checklist to prevent "not ready" work from entering a sprint |
Standup Formats (`standup-formats/`)
| Format | Best For |
|---|---|
classic-three-questions.md | Traditional teams, new-to-agile teams, or when you need structure |
walk-the-board.md | Mature teams focused on flow; centers discussion on the work, not the people |
async-standup.md | Distributed/remote teams across time zones with structured written updates |
focus-and-blockers.md | Fast-paced teams that want a 5-minute standup focused only on what matters today |
Retrospective Frameworks (`retrospectives/`)
| Framework | Vibe | Duration |
|---|---|---|
start-stop-continue.md | Simple and direct — what to change, what to keep | 45 min |
four-ls.md | Liked, Learned, Lacked, Longed For — emotional + analytical | 60 min |
sailboat.md | Visual metaphor — wind, anchors, rocks, island destination | 60 min |
mad-sad-glad.md | Emotion-first — surfaces feelings before jumping to solutions | 45 min |
what-went-well.md | Strengths-based — amplify the good, then address gaps | 45 min |
timeline-retro.md | Event-by-event walkthrough — ideal after complex or troubled sprints | 90 min |
Spreadsheets (`spreadsheets/`)
| File | Purpose |
|---|---|
velocity-tracker.csv | 12-sprint velocity history with rolling averages and capacity forecasting |
burndown-data.csv | Daily burndown tracking for a single sprint with ideal vs actual lines |
Guide (`guides/`)
| File | Purpose |
|---|---|
agile-ceremonies-guide.md | When to run which ceremony, facilitation tips, common anti-patterns, and troubleshooting |
Features
- Complete ceremony coverage — planning, standup, review, and retrospective templates in one kit
- Four standup formats — from traditional three-questions to async standups for remote teams
- Six retro frameworks — rotate formats to keep retrospectives fresh and avoid retro fatigue
- Velocity tracking — 12-sprint history with rolling averages so you can forecast reliably
... continues with setup instructions, usage examples, and more.
📄 Content Sample guides/agile-ceremonies-guide.md
Agile Ceremonies Guide
A practical reference for planning, running, and troubleshooting agile ceremonies. No theory lectures — just what works, when to use it, and what to do when things go wrong.
Ceremony Overview
| Ceremony | Purpose | Frequency | Duration (2-wk sprint) | Key Output |
|---|---|---|---|---|
| Sprint Planning | Decide what to build and how | Start of sprint | 2 hours | Sprint backlog + sprint goal |
| Daily Standup | Sync on progress and blockers | Daily | 15 minutes | Blocker list + parking lot |
| Sprint Review | Demo completed work, collect feedback | End of sprint | 1 hour | Feedback items + backlog updates |
| Retrospective | Improve team processes | End of sprint | 45-90 minutes | 2-3 action items with owners |
| Backlog Refinement | Prepare stories for future sprints | Mid-sprint (1-2x/week) | 1 hour | Refined, estimated stories |
Ceremony Calendar (2-Week Sprint)
Week 1
├── Monday: Sprint Planning (2 hrs)
├── Tuesday: Standup (15 min)
├── Wednesday: Standup (15 min) + Refinement (1 hr)
├── Thursday: Standup (15 min)
└── Friday: Standup (15 min)
Week 2
├── Monday: Standup (15 min)
├── Tuesday: Standup (15 min) + Refinement (1 hr)
├── Wednesday: Standup (15 min)
├── Thursday: Sprint Review (1 hr) + Retrospective (45 min)
└── Friday: Buffer / prep for next sprint
Total ceremony overhead per sprint: ~8-9 hours per person out of 80 available hours (10-11%). This is normal. Teams that skip ceremonies to "save time" spend that time (and more) on miscommunication, rework, and misaligned priorities.
Sprint Length: How to Choose
| Sprint Length | Best For | Trade-offs |
|---|---|---|
| 1 week | Fast feedback cycles, volatile requirements, small teams | High ceremony overhead (20%+ of time). Stories must be very small. Planning feels constant. |
| 2 weeks | Most teams. Good balance of planning horizon and feedback speed. | Industry default for a reason. Long enough to build meaningful features, short enough to course-correct. |
| 3 weeks | Large stories, regulated environments, teams with long testing cycles | Feedback is slower. Scope creep risk is higher. Planning is harder because more can change. |
| 4 weeks | Almost never recommended | By week 3, the plan is obsolete. Sprint becomes a mini-waterfall. |
Rule of thumb: Start with 2 weeks. Switch to 1 week if you're spending too much time on the wrong things. Switch to 3 weeks only if your stories consistently can't fit in 2 weeks (which usually means your stories are too big).
... and much more in the full download.