Skip to content
BENIBIX Learn

Scrum Framework Basics

Level 2 Β· Scrum

What Scrum is, where it came from and what its guide asks for. Sprints of one month or less, three pillars and the five values a team works by.

Course contentsLesson 3 of 19

After this lesson you can

  • Say what Scrum is and is not
  • Name the three pillars
  • Explain what a sprint is

11 mincovers 2 glossary entries

Worth reading first: Iterations and Timeboxes

What Scrum is and how a sprint works

Scrum is a light framework that helps a small team build things in short rounds. Each round is called a sprint, and it lasts one month or less. Ken Schwaber and Jeff Sutherland made it in the early 1990s. Its rules fit in one short text, the Scrum Guide. The current version is from November 2020.

A sprint is a fixed timebox. A new one starts as soon as the last one ends, with no gap between. Most teams pick two weeks. Every other part of Scrum happens inside a sprint, and each sprint should end with a working piece that could be used.

Scrum rests on three pillars. Transparency means the work and the progress are visible to everyone. Inspection means checking the work and the progress often. Adaptation means changing course as soon as a check shows something is off. The idea is to learn from what happens, not from what was guessed.

The guide also names five values: commitment, focus, openness, respect and courage. They sound soft, but they do real work. A team that hides bad news has lost openness. Then the pillars stop working, since there is nothing true left to check.

Inside each sprint sit four meetings. One plans the sprint. A short one happens every day. One near the end shows the work to the people it is for. The last one looks at how the team worked. Each has a time limit, and later lessons cover each one.

The guide calls Scrum purposely incomplete. It sets out a team of three jobs, five events and three lists, and stops. How to write the work down, size it or track it is left to the team. That is why many teams add habits from elsewhere.

The common mistake is calling any two-week work cycle Scrum. A team with sprints but no working piece at the end of each one, and no meeting to improve, is not doing Scrum. It is doing a two-week to-do list.

One sprint, start to finish. Every Scrum event sits inside it, each with its own time limit.

Worked example

Jack's team picks two weeks

Jack's team of 7 in Toronto starts Scrum on a new app. They try one-month sprints first, but a wrong turn costs them 3 weeks of work before anyone sees it.

They move to 2-week sprints. Now each mistake costs 2 weeks at most, and users see something new 26 times a year instead of 12.

The words for this lesson2

Check yourself

How long can a sprint last in Scrum?

Finished this lesson?

Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.