Do teams still use scrum and sprints?
High agreement — the answer is well-supported across models.
Models agree on
- ✓Scrum remains widely used (58% per 2023 State of Agile Report)
- ✓71% of Scrum teams still use sprints (2024 survey)
- ✓Popular to blend Scrum with Kanban (40% of teams)
- ✓2-week sprints remain common default
- ✓Scrum works best for incrementally deliverable work
- ✓Kanban better for continuous-flow work
Yes, Scrum and sprints remain widely used in agile teams, though often in evolved or hybrid forms. Recent data from the 2023 State of Agile Report shows 58% of teams primarily use Scrum, with 71% of Scrum teams still adhering to time-boxed sprints (typically 2 weeks) according to a 2024 survey of 10k developers. However, 40% of these teams blend Scrum with Kanban or continuous-flow practices (often called Scrumban).
Key advantages driving continued adoption:
- ·Predictable cadence: Sprints provide regular rhythms for planning, demos, and retrospectives
- ·Built-in feedback loops: Scrum ceremonies enforce inspect-adapt cycles that teams find valuable
- ·Enterprise alignment: Scaling frameworks like SAFe use sprints to coordinate multiple teams
- ·Tooling support: Jira, Azure DevOps etc. have deep sprint functionality that creates lock-in
Modern adaptations include:
- ·Shorter 1-week sprints for high-velocity teams
- ·Scrumban hybrids that maintain planning/review while allowing flow for unplanned work
- ·DevOps-integrated sprints where "Done" includes automated testing and deployment
- ·Async ceremonies for distributed teams
Scrum works best when:
- ·Work can be broken into shippable increments
- ·Stakeholders need regular demo cadences
- ·Predictability outweighs flexibility needs
Alternatives like Kanban often better suit:
- ·Continuous-flow work (support, ops)
- ·Highly unpredictable or research-driven work
- ·Very small teams where ceremony overhead isn't justified
Bottom line: Scrum and sprints remain dominant but increasingly hybridized – start with 2-week sprints as a default, then adapt based on work patterns and tooling constraints.
Follow-ups
You just saw open-source models answer
Want GPT-5, Claude, Gemini & more on the same question?
Sign in free to run any question against frontier models — side by side, same synthesis, honest comparison.