translate Automatic translation · View original
What You Need to Know About Your First 90 Days as a Scrum Master
Between the moment you study to become a Scrum Master and your first sprint on a real team, there is a distance that cannot be measured in story points.
Knowing what awaits you does not eliminate that distance, but it can keep it from catching you off guard.
What You Expect as a Scrum Master and What You Find
When you study to become a Scrum Master, you build a fairly precise mental model of how the role works: the events, the artifacts, the responsibilities, the team dynamics. You have a clear picture of what a good SM does and what a well-functioning team looks like.
The problem is that the first real team does not always resemble that model.
Not because the model is wrong, but because understanding how Scrum should work is one thing, and running into a specific organization, with its history, culture, and inertia, is another: a team that has been working one way for years, a Product Owner with twelve meetings a day, a management that approved "doing Scrum" without really grasping what that means day to day, and so on.
That gap between expectations and reality is universal. It does not depend on how you learned; a real team is simply not always a textbook case. Recognizing this is the first step to not getting frustrated when the territory does not match the map.
The Most Common Mistakes
Knowing them does not guarantee avoiding them, but it helps you spot them before they become a bigger problem.
1. Implementing Before Observing
This is the most frequent mistake. You are clear about what needs to be done, and you want to do it well. The result is that you celebrate every event, respect the timeboxes, explain the roles patiently... and get frustrated when the team does not respond the way you expected.
You probably have not yet learned to read the context you are operating in. Scrum is an intentionally incomplete framework: what works on a mature team with real autonomy may not work the same way on a team that has been under very directive management for years or that has just started with Scrum. Your first task is not to implement. It is to observe and understand.
2. Confusing Facilitating with Solving
When the team has a problem, the natural impulse is to fix it. However, there is an important difference between removing a real impediment the team cannot resolve on its own and resolving any friction before the team has the chance to handle it.
A Scrum Master who solves everything deprives the team of the opportunity to develop its own capacity for self-management. And a team that does not self-manage depends on the SM to function, which is exactly the opposite of what you are aiming for.
3. Underestimating Organizational Politics
The Scrum Master does not operate in a vacuum. They operate within an organization with interests, hierarchies, and power dynamics that do not disappear just because the team adopts an agile framework. Ignoring that reality is one of the most common reasons Scrum implementations have less impact than expected: not for lack of technical knowledge, but for lack of understanding of the organizational context in which it is applied.
Understanding who actually makes the decisions, what fears lie behind resistance to change, and how to navigate those conversations is just as important as knowing how long a Sprint Planning lasts.
4. Talking More Than You Listen
A novice Scrum Master tends to explain, justify, and teach. This is understandable: you have fresh knowledge and want to contribute it. But in the first months, listening is worth more than any explanation.
The conversations, the tensions that never reach the retrospective, the silences in the Daily Scrum... that is where the information you most need to understand what is really going on in the team lives. And that information only surfaces if you create the space for it to emerge.
Practical Advice for Your First 90 Days as a Scrum Master
Observe Before Intervening
The first 30 days are for observation. Attend the events, take notes, ask questions. Resist the urge to change things before you understand why they are the way they are. Many dynamics that look dysfunctional from the outside have a history behind them that is worth knowing before you act. Do not assume anything. Gather information, data, and evidence.
Invest in Your Relationship with the Product Owner
The relationship between the Scrum Master and the Product Owner is one of the most decisive factors in how the team functions. If that relationship does not work, the team notices. Spend time understanding their priorities, pressures, and vision for the product. Not to agree on everything, but to collaborate from a place of understanding. Again, gather information before forming ideas or assuming anything.
Make the Retrospective Your Main Tool
The Sprint Retrospective is the event where you can have the most influence in the first months. Not as the protagonist, but as the facilitator of conversations the team needs to have. A good retrospective is one that gets the team to speak honestly about what is happening.
Researcher Amy Edmondson has spent decades studying the dynamics of high-performing teams. Her work on psychological safety shows that teams do not improve when they are told how to do it, but when they feel it is safe to experiment, make mistakes, and talk about them openly. Your job in the retrospective (and in general) is to create that space and sustain it.
Learn to Influence Without Formal Authority
The Scrum Master has no formal authority over anyone. They do not assign tasks, evaluate, or decide. Their influence is lateral, based on the trust and credibility they build over time. It can feel insecure at first: how do I influence without power?
The practical answer: by asking questions, by making visible what the team does not see, and by creating the conditions for important conversations to happen. It is a kind of leadership that is learned through practice. And the first 90 days are the best time to start.
Seek Role Models and Community
Read, and talk with others who are facing the same challenges. Look for communities of practice, forums, and groups where professionals in the role share real experiences and theory. Contrasting with other realities will help you calibrate your own.
The Scrum Master in the Age of AI
Artificial intelligence is already changing how development teams work: it can generate code, suggest facilitation techniques, analyze flow metrics, take notes in retrospectives, and propose process improvements. That is a reality.
However, there is a fundamental distinction: AI is technology, not a team. It does not build trust relationships, manage the group dynamics difficulties that emerge in a team, read the silence in a tense retrospective, or build the trust that makes self-management possible.
And those are exactly the competencies that define the value of a Scrum Master who evolves with the role. An analysis by Xebia Academy on the future of agile teams positions the 2030 SM as a leader focused on transformation strategy, organizational coaching, and governance of hybrid human-AI work systems. Removed from daily operations, closer to change leadership.
The real risk is not that AI replaces the Scrum Master. The risk is that a Scrum Master whose value is defined solely as an event facilitator becomes exposed. Because AI can assist with that. What it cannot replicate is emotional intelligence, systems thinking, and the ability to guide a team through uncertainty.
There is another element that adds urgency to the role: with AI, teams can build features much faster than organizations can validate them. McKinsey found in its State of AI 2025 that AI adoption is widespread but its impact on business results remains scarce in most organizations. The differentiating factor is not the tool adopted, but having deeply redesigned workflows. Someone has to facilitate that conversation. Someone has to help the team ask not only whether they can build it, but whether they should. That someone is the Scrum Master.
Paradoxically, AI makes the first 90 days more important than ever. Because that is when you decide what kind of Scrum Master you will be: one who only applies the theory, or one who learns to read the context, facilitate complexity, and generate value where no tool can do it for you.
To Keep Learning
If you are in your first months as a Scrum Master, or preparing to become one, on our website you will find reference materials and resources (templates, interactive tools, notes, etc.). You can also access our wiki and the Open Knowledge community for free.
Become a member of the Agile Club (free the first year if you get certified with an official Scrum Manager center) to access exclusive resources, maintain your SPs, and practice your skills in different areas of agility on Skill Arena: from AI applied to agility to user stories and OKRs.
Bibliography
Edmondson, A. (1999). "Psychological Safety and Learning Behavior in Work Teams". Administrative Science Quarterly, 44 (2), 350–383.
McKinsey & Company (2025). The State of AI: How Organizations Are Rewiring to Capture Value. McKinsey QuantumBlack.
Schwaber, K. & Sutherland, J. (2020). The Scrum Guide.
Scrum Manager (2026). Guía Scrum Master. Scrummanager.com.
Xebia Academy (2025). Scrum Teams In 2030: The Future Of Agile With AI. Academy.xebia.com.
Take part in the poll
This article includes an active poll in the Scrum Manager community.
poll View the poll in the community