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.
Comments (8)
Log in to your Scrum Manager area to comment
Jorge Sánchez López ★★★
25 Mar 2026 14:22There 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.
Hay una imagen idílica que todos compramos cuando estudiamos para ser Scrum Master: un equipo autogestionado, pizarras llenas de notas adhesivas de colores y un flujo de trabajo perfecto.
Luego llega el primer lunes. Te encuentras con una organización que tiene prisa, un Product Owner desbordado y un equipo que te mira como si fueras un antropólogo examinando una tribu extraña.
En mis años como formador y mentor organizacional, he visto a muchos profesionales brillantes fallar no por falta de conocimiento, sino por exceso de teoría. Si quieres que tus primeros tres meses cuenten, deja de lado el manual un momento y hablemos de la realidad.
Se nos dice que los primeros 30 días son para observar. Es un consejo con trampa. Si te limitas a mirar, la organización concluirá que eres un gasto innecesario.
Tu observación debe ser estratégica y activa. No esperes un mes para aportar valor. Busca una victoria temprana o logro rápido: arregla ese acceso que el equipo lleva pidiendo semanas, elimina esa reunión que todos odian o clarifica una prioridad confusa. La autoridad no te la da tu certificado; te la da tu capacidad para despejar el camino.
Existe la creencia de que el SM nunca debe dar soluciones para no romper la autogestión del equipo. Esto es un error de bulto en entornos de crisis.
Si el equipo tiene un bloqueo externo y tú te limitas a hacer "preguntas reflexivas", estás siendo un obstáculo, no un líder. Tu trabajo es ser un rompe-muros. Elimina las piedras del camino hoy para que el equipo pueda aprender a caminar solo mañana. La fluidez del trabajo está por encima del purismo metodológico.
Muchos SM novatos se centran en los eventos y las métricas, ignorando que las decisiones reales se toman en pasillos o en reuniones de dirección a las que no están invitados.
No trabajas en un laboratorio, trabajas en una organización con jerarquías, miedos y juegos de poder(Te recomiendo el arte de la guerra, El principe...). Entender quién tiene el veto real y quién se siente amenazado por la agilidad es tan importante como saber gestionar el Backlog. Sin inteligencia política, tus propuestas de cambio morirán en un cajón.
A estas alturas, sabemos que la Inteligencia Artificial analiza las métricas de flujo y detecta cuellos de botella mejor que cualquier humano. Pero la IA no sabe leer la tensión en un silencio durante una Retrospectiva ni sabe cómo motivar a un desarrollador quemado. (Afortunadamente para tí, tienes un poder que no eres consciente, a continuación te lo explico)
No compitas con los datos; úsalos. Deja que la tecnología haga el análisis frío y dedica tu energía a lo que ninguna máquina puede replicar: la estrategia de cambio y la resolución de conflictos humanos. Ese es el terreno donde un SM de alto nivel se vuelve indispensable.
Olvida el "agilismo de salón". Los primeros 90 días son una prueba de resistencia y pragmatismo. No busques que el equipo sea perfecto; busca que sea mejor que ayer.
Duro con los problemas. Cercano con las personas. Y con la claridad suficiente para saber cuándo aplicar la teoría, cuándo adaptarla y cuándo tener el criterio de apartarla.
Porque al final, la agilidad no va de seguir un método. Va de entregar valor en organizaciones reales, con personas reales y con toda la complejidad que eso conlleva. Y eso, por mucho que lo intente, ningún examen de certificación lo va a enseñar. O puede que necesites un mentor, un estudiante de medicina hace el MIR antes de ejercer como profesional, lo has pensado.
Gracias Scrum Manager por poner estos debates sobre la mesa.
Automatic translation · View original
Canal Scrum ★
25 Mar 2026 16:02Good 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.
Buena síntesis de tensiones reales que cualquier SM reconocerá: la observación activa, la inteligencia política, saber cuándo apartar el manual.
Todo eso está en el día a día del rol.
En cuanto a lo de las certificaciones, ¿crees que el marco conceptual y la práctica se excluyen? Más bien se necesitan. El MIR que mencionas lo ilustra bien: la residencia existe porque antes hay carrera.
Gracias por participar y, sobre todo, por aportar tu experiencia.
Automatic translation · View original
Jorge Sánchez López ★★★
26 Mar 2026 00:11Thanks 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.
Gracias por la respuesta, y precisamente porque el debate merece más que un cierre amable, voy a matizar.
Nadie ha dicho que el marco y la práctica se excluyan. Lo que he dicho es algo diferente: que el peso que ponemos en la certificación como señal de competencia profesional es desproporcionado respecto a lo que esa certificación realmente acredita. Y eso tiene consecuencias en cómo llegan al rol los profesionales que formamos.
La analogía del MIR es buena, pero me sirve para lo contrario de lo que propones. El sistema MIR funciona precisamente porque nadie confunde el título de medicina con la capacidad de operar. La residencia existe, dura años y ocurre bajo supervisión real porque hay un consenso explícito de que la teoría sola no es suficiente. En nuestra profesión ese consenso no existe, o existe en el discurso pero no en la práctica de contratación ni en los itinerarios de desarrollo profesional.
La pregunta que lanzo no es si necesitamos el marco. Es si estamos siendo honestos sobre lo que la certificación garantiza y lo que no. Y si esa honestidad, o la falta de ella, está produciendo profesionales bien examinados pero mal equipados para el conflicto real.
Esa tensión no se resuelve diciendo que ambas cosas se complementan. Se resuelve diseñando mejor el puente entre las dos.
Automatic translation · View original
Canal Scrum ★
26 Mar 2026 11:26We 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.
Estamos de acuerdo en buena parte de lo que dices. La agilidad va de entregar valor en contextos reales, con personas reales, y eso no se aprende solo con un examen. Hasta ahí, totalmente contigo.
Ahora bien, conviene no confundir la parte con el todo. Una certificación académica no pretende enseñarte a lidiar con la complejidad de una organización real; lo que hace es asegurarse de que conoces las bases. Y sin las bases, es muy difícil aprender de la experiencia. Volviendo al ejemplo del MIR: nadie espera que un médico sepa operar solo por haber estudiado anatomía, pero tampoco querríamos que alguien entre en un quirófano sin haberla estudiado.
La formación académica te da el conocimiento sobre el que construir. La práctica te da el criterio. Y si lo que quieres es acreditar que además de saber la teoría estás ejerciendo con un nivel profesional contrastado y te mantienes al día, para eso existen otros mecanismos: las certificaciones profesionales, que se renuevan anualmente con valoraciones reales de clientes y compañeros, o los diplomas de evaluación de Skill Arena, que validan competencias prácticas en áreas concretas.
El puente entre las dos es complementar las dos. El conocimiento sin práctica se queda corto, pero la práctica sin conocimiento suele llevar a repetir errores que otros ya resolvieron.
Automatic translation · View original
Jorge Sánchez López ★★★
26 Mar 2026 11:31It's called SHU HA RI.
I recommend watching KARATE KID😊👌
Se llama SHU HA RI.
Recomiendo ver KARATE KID😊👌
Automatic translation · View original
Canal Scrum ★
26 Mar 2026 11:38Or read this article 😁: https://scrummanager.com/community/entre-la-adaptacin-y-la-degeneracin-la-lnea-invisible-que-decide-si-scrum-sigue-siendo-scrum
O leer este artículo 😁: https://scrummanager.com/community/entre-la-adaptacin-y-la-degeneracin-la-lnea-invisible-que-decide-si-scrum-sigue-siendo-scrum
Automatic translation · View original
Jorge Sánchez López ★★★
26 Mar 2026 11:41SHU Would it be TRAINING and CERTIFICATION?
SHU ¿Sería FORMACIÓN y CERTIFICACIÓN?
Automatic translation · View original
Canal Scrum ★
26 Mar 2026 11:44Would 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
¿Así quedaría?
Shu → Formación y certificación
Ha → Práctica y mentoría (espacios como el Club Agile, Skill Arena o la mentoría que tú ofreces)
Ri → Criterio propio
Automatic translation · View original