Professional

What You Need to Know About Your First 90 Days as a Scrum Master

Automatic translation · View original

Topic illustration: What You Need to Know About Your First 90 Days as a Scrum Master

Find out what happens in your first 90 days as a Scrum Master, the most common mistakes, practical advice, and the role in the age of AI.

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.

🔒 Restricted Poll

Please log in to your Scrum Manager account to do this.

Log in
Share:

Comments (8)

Log in to your Scrum Manager area to comment


Jorge Sánchez López ★★★
25 Mar 2026 14:22

There is an idyllic picture we all buy into when we study to become a Scrum Master: a self-managing team, boards covered in colorful sticky notes, and a perfect workflow.

Then comes the first Monday. You find an organization in a hurry, a Product Owner who is overwhelmed, and a team that looks at you as if you were an anthropologist studying a strange tribe.

In my years as a trainer and organizational mentor, I have seen many brilliant professionals fail not for lack of knowledge, but from too much theory. If you want your first three months to count, set the manual aside for a moment and let's talk about reality.

We are told that the first 30 days are for observing. It's advice with a catch. If you only watch, the organization will conclude that you are an unnecessary expense.

Your observation must be strategic and active. Don't wait a month to add value. Look for an early win or quick achievement: fix that access the team has been requesting for weeks, eliminate that meeting everyone hates, or clarify a confusing priority. Authority isn't given to you by your certificate; it comes from your ability to clear the way.

There is a belief that the SM should never offer solutions so as not to break the team's self-management. This is a glaring mistake in crisis environments.

If the team faces an external blocker and you limit yourself to asking "reflective questions," you are being an obstacle, not a leader. Your job is to be a wall-breaker. Remove the stones from the path today so the team can learn to walk on its own tomorrow. The flow of work comes before methodological purism.

Many novice SMs focus on events and metrics, overlooking that the real decisions are made in hallways or in management meetings they are not invited to.

You are not working in a laboratory; you are working in an organization with hierarchies, fears, and power games (I recommend The Art of War, The Prince...). Understanding who holds the real veto and who feels threatened by agility is just as important as knowing how to manage the Backlog. Without political savvy, your proposals for change will die in a drawer.

By now, we know that Artificial Intelligence analyzes flow metrics and detects bottlenecks better than any human. But AI cannot read the tension in a silence during a Retrospective, nor does it know how to motivate a burned-out developer. (Fortunately for you, you have a power you may not be aware of; I explain it below)

Don't compete with the data; use it. Let technology do the cold analysis and devote your energy to what no machine can replicate: change strategy and resolving human conflicts. That is the ground where a high-level SM becomes indispensable.

Forget "armchair agile." The first 90 days are a test of endurance and pragmatism. Don't aim for the team to be perfect; aim for it to be better than yesterday.

Tough on problems. Close with people. And with enough clarity to know when to apply the theory, when to adapt it, and when to have the judgement to set it aside.

Because in the end, agility isn't about following a method. It's about delivering value in real organizations, with real people, and with all the complexity that entails. And that, no matter how hard it tries, no certification exam is going to teach. Or maybe you need a mentor; a medical student takes the MIR before practicing as a professional, have you thought about it?

Thanks, Scrum Manager, for putting these debates on the table.

Automatic translation · View original

Reply Reactions
Canal Scrum ★
25 Mar 2026 16:02

Good synthesis of real tensions that any SM will recognize: active observation, political intelligence, knowing when to set the manual aside.

All of that is part of the day-to-day of the role.

As for certifications, do you think conceptual framework and practice are mutually exclusive? I'd say they're complementary. The MIR you mention illustrates it well: residency exists because there's medical school first.

Thank you for taking part and, above all, for sharing your experience.

Automatic translation · View original

Reply Reactions
Jorge Sánchez López ★★★
26 Mar 2026 00:11

Thanks for your reply, and precisely because the debate deserves more than a polite closing, I'm going to clarify my position.

No one has said that the framework and practice are mutually exclusive. What I have said is something different: that the weight we give certification as a signal of professional competence is disproportionate to what that certification actually proves. And that has consequences for how the professionals we train reach the role.

The MIR analogy is a good one, but it serves the opposite of what you propose. The MIR system works precisely because no one confuses a medical degree with the ability to operate. Residency exists, lasts years, and happens under real supervision because there is an explicit consensus that theory alone is not enough. In our profession that consensus does not exist, or it exists in discourse but not in hiring practices or in professional development paths.

The question I am raising is not whether we need the framework. It is whether we are being honest about what certification guarantees and what it does not. And whether that honesty, or the lack of it, is producing professionals who are well examined but poorly equipped for real conflict.

That tension is not resolved by saying both things complement each other. It is resolved by designing a better bridge between the two.

Automatic translation · View original

Reply Reactions
Canal Scrum ★
26 Mar 2026 11:26

We agree with much of what you say. Agility is about delivering value in real contexts, with real people, and that can't be learned from an exam alone. Up to that point, I'm completely with you.

That said, it's worth not confusing the part with the whole. An academic certification doesn't aim to teach you how to deal with the complexity of a real organization; what it does is make sure you know the fundamentals. And without the fundamentals, it's very hard to learn from experience. Going back to the MIR example: nobody expects a doctor to know how to operate just because they studied anatomy, but we wouldn't want someone walking into an operating room without having studied it.

Academic training gives you the knowledge to build on. Practice gives you judgement. And if what you want is to demonstrate that, in addition to knowing the theory, you're practicing at a proven professional level and keeping up to date, there are other mechanisms for that: professional certifications, which are renewed annually with real ratings from clients and colleagues, or the Skill Arena evaluation diplomas, which validate practical competencies in specific areas.

The bridge between the two is that they complement each other. Knowledge without practice falls short, but practice without knowledge often leads to repeating mistakes that others have already solved.

Automatic translation · View original

Reply Reactions
Jorge Sánchez López ★★★
26 Mar 2026 11:31

It's called SHU HA RI.
I recommend watching KARATE KID😊👌

Automatic translation · View original

Reply Reactions
Canal Scrum ★
26 Mar 2026 11:38

Or read this article 😁: https://scrummanager.com/community/entre-la-adaptacin-y-la-degeneracin-la-lnea-invisible-que-decide-si-scrum-sigue-siendo-scrum

Automatic translation · View original

Reply
Jorge Sánchez López ★★★
26 Mar 2026 11:41

SHU Would it be TRAINING and CERTIFICATION?

Automatic translation · View original

Reply
Canal Scrum ★
26 Mar 2026 11:44

Would this look right?

Shu → Training and certification
Ha → Practice and mentoring (spaces like the Agile Club, Skill Arena, or the mentoring you offer)
Ri → Own judgement

Automatic translation · View original

Reply