← Back to all products

Sprint Management Kit

$29

Sprint planning templates, standup formats, retrospective frameworks, velocity tracking, and burndown chart generators.

26 files
MarkdownJSON

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 26 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 ├── interactive.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/`)

TemplatePurpose
sprint-planning.mdSprint planning meeting template with capacity calculation, goal setting, and story breakdown
sprint-review.mdSprint review/demo template with stakeholder feedback capture and metrics
definition-of-done.mdTeam-level DoD checklist covering code, testing, docs, and deployment
definition-of-ready.mdStory readiness checklist to prevent "not ready" work from entering a sprint

Standup Formats (`standup-formats/`)

FormatBest For
classic-three-questions.mdTraditional teams, new-to-agile teams, or when you need structure
walk-the-board.mdMature teams focused on flow; centers discussion on the work, not the people
async-standup.mdDistributed/remote teams across time zones with structured written updates
focus-and-blockers.mdFast-paced teams that want a 5-minute standup focused only on what matters today

Retrospective Frameworks (`retrospectives/`)

FrameworkVibeDuration
start-stop-continue.mdSimple and direct — what to change, what to keep45 min
four-ls.mdLiked, Learned, Lacked, Longed For — emotional + analytical60 min
sailboat.mdVisual metaphor — wind, anchors, rocks, island destination60 min
mad-sad-glad.mdEmotion-first — surfaces feelings before jumping to solutions45 min
what-went-well.mdStrengths-based — amplify the good, then address gaps45 min
timeline-retro.mdEvent-by-event walkthrough — ideal after complex or troubled sprints90 min

Spreadsheets (`spreadsheets/`)

FilePurpose
velocity-tracker.csv12-sprint velocity history with rolling averages and capacity forecasting
burndown-data.csvDaily burndown tracking for a single sprint with ideal vs actual lines

Guide (`guides/`)

FilePurpose
agile-ceremonies-guide.mdWhen 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

CeremonyPurposeFrequencyDuration (2-wk sprint)Key Output
Sprint PlanningDecide what to build and howStart of sprint2 hoursSprint backlog + sprint goal
Daily StandupSync on progress and blockersDaily15 minutesBlocker list + parking lot
Sprint ReviewDemo completed work, collect feedbackEnd of sprint1 hourFeedback items + backlog updates
RetrospectiveImprove team processesEnd of sprint45-90 minutes2-3 action items with owners
Backlog RefinementPrepare stories for future sprintsMid-sprint (1-2x/week)1 hourRefined, 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 LengthBest ForTrade-offs
1 weekFast feedback cycles, volatile requirements, small teamsHigh ceremony overhead (20%+ of time). Stories must be very small. Planning feels constant.
2 weeksMost 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 weeksLarge stories, regulated environments, teams with long testing cyclesFeedback is slower. Scope creep risk is higher. Planning is harder because more can change.
4 weeksAlmost never recommendedBy 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.