Sprint

Plain English explanation

A Sprint is a short cycle of focused work, usually 1–4 weeks, where the team works together to build something useful. Think of it like a mini project with a clear goal, where the team plans, builds, reviews, and improves in a repeatable cycle.

Why it matters

The Sprint creates a regular rhythm for the team. Instead of working endlessly without checkpoints, the team delivers value frequently, gets feedback quickly, and improves continuously. This reduces risk and keeps work aligned with real needs.

How it works

Each Sprint starts with Sprint Planning, where the team decides what to build. During the Sprint, the team collaborates daily, tracks progress, and adapts as needed. At the end, they review the work with stakeholders and reflect on how to improve before starting the next Sprint.

Example

A product team working on a mobile app runs a 2-week Sprint. At the start, they decide to improve the login experience. By the end of the Sprint, they deliver a working version with faster authentication and fewer errors, ready for users to test.

Common myths

A Sprint is not just a deadline or a task list. It is a complete cycle of planning, building, reviewing, and improving. Another common mistake is treating it like a mini waterfall project instead of a flexible, collaborative process.

Key points

• A Sprint has a fixed length (usually 1–4 weeks)
• Each Sprint produces a usable Increment
• No changes are made that endanger the Sprint Goal
• The Sprint includes all Scrum events
• A new Sprint starts immediately after the previous one ends