What is Scrum and why should you use it?

As I previously promised in a post on Instagram, today I will return to Scrum. For those who are not yet familiar with it: Scrum is a framework that helps teams work together effectively, especially on projects where a lot of changes occur. It was developed in the early 1990s by Ken Schwaber and Jeff Sutherland and has since become a popular framework, especially within the tech and software world.

What exactly is Scrum?

Scrum is officially codified in the Scrum Guide, the latest version of which dates from November 2020. This guide describes Scrum as a lightweight framework that helps people, teams and organizations tackle complex problems and create value through adaptable solutions .

In simple terms, Scrum provides structure and flexibility to help teams achieve goals without being tied to a rigid plan. Although Scrum is mainly popular in the tech and software sector, it can be applied in many different industries.

Why use Scrum?

Scrum is ideal for projects that involve many uncertainties or changes. It enables teams to quickly adapt to new insights or circumstances, keeping them flexible. This makes it an excellent choice for projects such as product development, where innovation and continuous improvement are central.

How does Scrum work?

Scrum is based on two principles: empiricism and lean thinking.

• Empiricism means that knowledge comes from experience and decisions are made based on what is known.
• Lean thinking is about reducing waste and focusing on what really matters.

In Scrum you have a number of important roles:

• The Scrum Master: this person ensures that the team works efficiently and removes obstacles.
• The Product Owner: monitors the vision of the end product and determines the priorities within the project.
• The Development Team: the people who actually carry out the work. These are not just programmers, but everyone who contributes to the project. A Scrum team preferably consists of 10 people or less.

Sprint and Scrum events?

A Sprint is a fixed period of time (maximum one month) during which a team works on specific goals. The constant length of the sprints ensures a fixed rhythm. As soon as one sprint ends, the next one starts immediately. Within each sprint there are several events that support the process:

1. Sprint Planning: The team plans the work for the upcoming sprint and sets goals. This takes a maximum of 8 hours for a one-month sprint.
2. Daily Scrum: A daily meeting of maximum 15 minutes in which progress is discussed and any adjustments are made.
3. Sprint Review: At the end of the sprint, the team presents the results to stakeholders and discusses what went well and what can be improved.
4. Sprint Retrospective: This is the time when the team reflects on the process and looks at ways to improve quality and efficiency.

My experience with Scrum

I started Scrum in February when I wasn't sure which direction I would take after my previous job. I thought it would be useful to obtain a Scrum certificate, especially if I were to work in development again. Although I was free for a while, life – as it often does – got in the way. Sick children, being sick myself, and even a fall down the stairs didn't exactly help my focus.

Now, with my own company, Scrum may be less necessary, but I still want to complete it. I've already put time and effort into it, and it would be a shame to pass it up. So I'm taking practice exams, and once I feel confident enough, I'll take the exam and hopefully get the certificate!

Wish me luck!