📖 Business
Sprint Framework
A sprint is a short, fixed-length iteration of work — typically one to four weeks — that produces a potentially shippable increment of product. At the start, the team selects items from the product backlog they commit to completing. During the sprint, they execute. At the end, they demonstrate working software and reflect on how to improve. The sprint is the heartbeat of Scrum: a recurring cycle that forces prioritization, creates urgency, and eliminates the fiction of "80% done." At the end of every sprint, either the thing works or it does not. There is no middle ground.
2
Minutes
2
Concepts
+45
XP
1
How It Works
The sprint cycle has four ceremonies:
1. Sprint Planning (start of sprint)
- Product Owner presents the top-priority backlog items
- Team discusses, asks questions, breaks items into tasks
- Team commits to what they can realistically finish this sprint
- The commitment is the team's, not management's — no one assigns work to individuals
2. Daily Standup (every day, 15 minutes, standing up)
- Three questions per person: What did I do yesterday? What will I do today? What's blocking me?
- Not a status report to management — it's a coordination tool for the team
- If it takes more than 15 minutes, you're doing it wrong
- Blockers get resolved after standup, not during
3. Sprint Review / Demo (end of sprint)
- Team demonstrates working software to stakeholders
- Stakeholders provide feedback that shapes the next sprint's priorities
- Only completed work is shown — no PowerPoint, no mockups, no "almost done"
- This is where trust between the team and the business is built
4. Sprint Retrospective (end of sprint, team only)
- What went well this sprint?
- What could we improve?
- What specific change will we commit to trying next sprint?
- The retrospective is where continuous improvement actually happens
Why time-boxing works:
- Creates natural urgency without artificial pressure
- Forces ruthless prioritization — you cannot fit everything in two weeks
- Prevents scope creep — new requests wait for the next sprint
- Generates a rhythm the team can sustain indefinitely