In my previous article, Agility sucks, it’s useless… Really?, I mentioned that I’m a Scrum Master, but what exactly does that mean?
In the early 2000s, several approaches emerged to improve the way we work, especially in the field of software development.
We talk about agility with the Agile Manifesto of 2001, methods like Extreme Programming and Kanban, and, of course, Scrum, with the Scrum Guide.
I’ll be writing more articles on these topics, so feel free to let me know in the comments what you’d like to learn about first!
Let’s get back to Scrum: Scrum is a framework built around three roles:
The Product Owner, the Development Team… and the Scrum Master.
The Scrum Master is the coach of the team.
They help the team get organized, continuously improve, and remove obstacles that slow down progress.
They’re often called a Servant Leader, meaning they guide the team through support and service rather than authority.
They also facilitate Scrum events like the Daily, Retrospective, and Review, ensuring Scrum principles and values are respected.
It’s kind of like a project manager… but without being the boss. They don’t impose, they support.
Their mission is to help the team move forward together, in a healthy, effective, and truly agile environment.