Definition
Scrum is the most widely used agile framework for organising product development. Work is done in sprints, fixed periods of 1 to 4 weeks, at the end of which the team delivers a usable increment. Scrum defines 3 roles: the product owner, who prioritises the backlog; the scrum master, who protects the process; and the development team, which builds. It also defines regular events: sprint planning, a short daily meeting, a sprint review and a retrospective.
In a company, Scrum gives a predictable rhythm: stakeholders know that every 2 weeks they will see working software and can influence what comes next. The product owner is the single point of prioritisation, which stops teams being pulled in 10 directions. Retrospectives create a habit of improving how the team works. Scrum is most effective for a dedicated team building one product, and it needs an empowered product owner to function.
Scrum remains the dominant framework, but many mature teams have simplified it, dropping ceremonies that add no value or moving to Kanban-style continuous flow, especially as CI/CD and AI tools make releases cheaper than a 2-week batch. The misconception is that following Scrum rules equals being agile. Scrum is a starting structure; the goal is delivering value and learning fast, and the framework should be adapted when it gets in the way.
In practice
A company's product team adopted Scrum with 2-week sprints and a single product owner. Executives stopped sending requests to individual developers and started attending the sprint review, where they could see progress and reprioritise every 2 weeks.
Why it matters
Scrum gives leadership a regular window into product progress and a single place to set priorities. If your teams use it, the sprint review is the meeting worth your time.
Frequently asked questions
- What are the roles in Scrum?
- Scrum has 3 roles. The product owner decides what to build and in which order by managing the backlog. The scrum master facilitates the process and removes obstacles. The developers, a cross-functional team, build and deliver the increment each sprint. There is no project manager role.
- How long should a sprint be?
- Between 1 and 4 weeks, with 2 weeks the most common choice. Shorter sprints give faster feedback and smaller risks; longer sprints suit work that needs more time to produce something reviewable. Consistency matters more than the exact length, because it makes planning and velocity predictable.