Sprint
A fixed-length iteration (typically 1-4 weeks) in Scrum during which a team works to complete a set of backlog items and deliver a potentially releasable product increment.
In-Depth Explanation
A sprint is the heartbeat of Scrum - a time-boxed period during which the team commits to delivering a set of backlog items that produce a usable product increment. Sprints create a predictable rhythm of planning, execution, and review.
Sprint characteristics:
- Time-boxed: Fixed duration that does not change (typically 2 weeks)
- Goal-oriented: Each sprint has a sprint goal that provides focus
- Protected: Scope should not change during the sprint (within reason)
- Complete: Each sprint produces a potentially releasable increment
- Consecutive: Sprints run back-to-back with no gaps
Sprint events within each sprint:
- Sprint Planning (beginning): Select items, set the sprint goal, plan the approach
- Daily Scrum (daily): 15-minute sync on progress and impediments
- Sprint Review (end): Demonstrate completed work to stakeholders
- Sprint Retrospective (end): Reflect on process improvements
Sprint lifecycle:
- Planning: Team selects items from the product backlog and commits to a sprint goal
- Execution: Team works on selected items, collaborating daily
- Review: Team demonstrates what was built and gathers feedback
- Retrospective: Team reflects on how they worked and identifies improvements
Sprint planning considerations:
- Consider the team's historical velocity when committing
- Account for holidays, leave, and other availability constraints
- Ensure items are well-refined and ready for development
- Leave some capacity (typically 10-20%) for unexpected work
- Set a clear, value-oriented sprint goal
Sprint protection rules:
- The sprint goal should not change once the sprint starts
- Work should not be added unless the team agrees and something is removed
- The sprint length should remain consistent
- Sprint cancellation is possible but should be rare (only when the sprint goal becomes obsolete)
Business Context
Sprints create a predictable delivery cadence that enables regular stakeholder feedback, manageable commitments, and the discipline of delivering working results frequently.
How Clever Ops Uses This
Clever Ops delivers client work in sprints, providing Australian businesses with regular, predictable deliveries of working solutions. Our sprint cadence ensures clients see progress every two weeks and can provide feedback that shapes subsequent work.
Example Use Case
"A team runs a two-week sprint with the goal of "Enable customers to view and pay invoices online," delivering three user stories that collectively achieve this goal and are demonstrated to stakeholders at the sprint review."