Logo
Enterprise IT & Cloud

Scrum

Scrum is the most-used agile framework: a small cross-functional team delivers in fixed sprints — usually two weeks — with defined roles (Product Owner, Scrum Master, developers) and ceremonies for planning, daily sync, review, and retrospective.

The shape of a sprint

Scrum’s core contract: the Product Owner owns a ranked backlog, the team commits to a sprint goal it can deliver as working software, and nothing changes inside the sprint. The ceremonies exist to protect that contract — planning sets the goal, dailies surface blockers, the review demos what shipped, and the retrospective adjusts how the team works.

Scrum fits work with a genuine backlog and iterative discovery — product development, evolving integrations. For interrupt-driven flow (support, ops, maintenance), Kanban’s continuous pull usually beats forcing work into sprints. Our agile-methods guide compares the frameworks head to head.

Frequently Asked Questions

What is a sprint in Scrum?

A sprint is Scrum’s fixed timebox — most commonly two weeks — in which the team turns a slice of the backlog into a working, potentially releasable product increment. Scope is protected inside the sprint: new work waits for the next planning cycle.

Related Standards

  • •Scrum Guide (2020) — the official framework definition

Need help with this?

We consult and build across all of these domains — tell us what you are working on.

Privacy & Cookie Preferences

We use cookies to enhance your experience, analyze site performance, and support our marketing efforts. Your privacy matters, and you can withdraw consent at any time.