Sprint
A fixed time-box in Scrum methodology—typically 1-4 weeks—during which a cross-functional team commits to delivering a defined set of work items toward a sprint goal.
Full Definition
A sprint is the fundamental work unit in the Scrum framework—a fixed-duration time box (typically 1-4 weeks, with 2 weeks being the most common) during which a cross-functional development team works toward a defined sprint goal. At the start of each sprint, the team collaborates with the Product Owner in sprint planning to select work items from the backlog and commit to a sprint goal—a specific business objective that the sprint's work will achieve. During the sprint, the team conducts daily standups to synchronize and identify impediments. At the sprint end, the team demonstrates completed work in a sprint review, conducts a retrospective to improve team process, and begins planning the next sprint. This regular cycle of planning, execution, review, and adaptation is the Scrum framework's core mechanism for rapid learning and continuous delivery. The sprint commitment creates predictability and accountability that is valuable for stakeholders and for the team. When the team commits to a sprint goal and selected work items, stakeholders gain reliable visibility into when work will be completed. The team gains focus—sprint commitments protect the team from mid-sprint scope changes (scope creep that disrupts the team's ability to complete committed work), enabling the sustained deep focus that complex development work requires. The regular sprint cadence also provides a forcing function for quality: teams that rush to complete sprint work without adequate testing, documentation, or code review are trading current sprint velocity for future technical debt—a pattern that the retrospective process is designed to surface and correct. Sprint metrics provide ongoing team performance visibility. Velocity (story points completed per sprint) measures throughput and enables capacity planning for future sprints. Sprint commitment rate (percentage of committed story points completed) indicates planning accuracy—teams with consistent 80-90% completion rates are planning realistically; teams with consistent 60% completion rates are over-committing and should calibrate. Sprint goal achievement (binary: was the sprint goal met?) is the most important metric—a team that completes 90% of committed items but misses the sprint goal has failed to deliver the sprint's business value despite completing most of the planned work.
FAQs
How should a sprint goal be defined?
A sprint goal should state the business outcome the sprint will achieve, not a list of features to be delivered. 'Enable customers to configure multi-user account permissions' is a good sprint goal—it states a customer-relevant capability. 'Complete stories US-234, US-235, and US-236' is a poor sprint goal—it describes work items without articulating business value. Sprint goals framed as outcomes enable the team to make intelligent trade-offs during the sprint if unexpected complexity arises—they can adjust which specific implementation approach achieves the goal rather than mechanically completing a list.
What should happen when a critical bug is discovered mid-sprint?
Mid-sprint emergencies require explicit scope trade-off decisions rather than simply adding work to the sprint. The team and Product Owner should assess the bug's severity and decide: fix the bug and remove an equivalent work item from the sprint (maintaining the sprint's total capacity); defer the bug to the next sprint if the fix can wait two weeks; or escalate for a sprint interruption if the bug is critical enough to require immediate address regardless of sprint impact. Teams that allow continuous mid-sprint additions ultimately have no reliable commitments, which defeats the sprint planning investment.
Relevant Executive Roles
The Crimson Bench · Est. 2002 · Founded in New York City
Deploy an Executive in 48 Hours
Verified corporate accounts only. Ivy League-educated. Flat-rate pricing. 14-day no-cause cancellation.
25,000+ Ivy League Executives · 150,000+ Global Consultants · 48-Hour Deployment