What to Do in Your First 30 Days as a Scrum Master

Starting a new Scrum Master role is exciting and disorienting in equal measure. You have the title, the calendar invites, and the expectation that you will somehow improve how the team works - but you are also the newest person in the room, with the least context about the team, the codebase, the stakeholders, and the organizational dynamics.

The instinct for many new Scrum Masters is to come in with energy and ideas. That instinct, applied too early, is one of the most common ways to lose the team's trust before you have earned it.

Your first 30 days are not about changing things. They are about understanding things. Here is how to approach them.

---

The Mindset: Listen Before You Lead

Before getting into the week-by-week breakdown, it is worth naming the underlying principle that should guide everything in your first month: listen more than you talk, and observe more than you act.

This is harder than it sounds. You were hired because you have skills and experience. You may already see things that need to change. But the team has context you do not have yet, and the fastest way to lose credibility is to propose solutions to problems you do not fully understand.

The Scrum Master who arrives with a list of improvements on day one is rarely the one who earns the team's respect. The one who spends the first month genuinely trying to understand how the team works - and why - almost always does.

---

Week 1: Orient and Observe

Your primary job in the first week is to get oriented without getting in the way.

Attend every ceremony as a participant, not a facilitator. If there is already a Scrum Master or someone running the ceremonies, let them run them. Watch how the team interacts. Notice who speaks up and who stays quiet. Notice where there is energy and where there is friction.

Read everything you can find. The backlog, the definition of done, the team working agreements, the last few sprint retrospective notes, any documentation about the product. You are building context, not forming opinions yet.

Introduce yourself to every stakeholder. Not just the team - the Product Owner, the engineering manager, the key business stakeholders, and anyone else who interacts regularly with the team. Keep these conversations short and focused on listening: "I am new here and want to understand how you work with the team. What is going well? What would you change if you could?"

Do not reorganize, restructure, or suggest improvements yet. Even if something seems obviously broken, wait. You do not have enough context yet to know why it is the way it is.

---

Week 2: Start Building Relationships

By week two, you should have a basic orientation to the team's work and ceremonies. Now it is time to start building the individual relationships that will make you effective.

Have a 1:1 with every team member. Keep it informal - coffee, a short walk, or a 20-minute video call. The goal is not to assess them; it is to understand their perspective on the team. Ask open questions: What do you enjoy most about working on this team? What gets in your way? What would you want a new Scrum Master to know?

These conversations will tell you more about the team's real dynamics than any ceremony will. Pay attention to what people say and what they avoid saying.

Establish your relationship with the Product Owner. This is one of the most important relationships you will have as a Scrum Master. Understand how they prefer to work, what their biggest challenges are, and how they think about the team. A strong Scrum Master-Product Owner partnership makes everything easier; a weak one creates constant friction.

Start taking notes on patterns. You are not drawing conclusions yet, but you should be noticing recurring themes. What comes up in multiple conversations? What does the team seem to agree on? Where is there tension?

---

Week 3: Facilitate With a Light Touch

By week three, you should start taking a more active role in the ceremonies - but carefully.

Take over facilitation of the ceremonies you have been observing. Start with the ones where the stakes are lower: the daily standup, backlog refinement. Let the retrospective and sprint planning wait until you have a stronger read on the team.

Ask the team how they want to work with you. This is a conversation worth having explicitly. What do they want from a Scrum Master? What has worked well with previous Scrum Masters? What has not? This conversation signals respect for the team's experience and gives you useful information about expectations.

Identify one small thing you can improve. By now you should have enough context to see something that is creating unnecessary friction - a process that is unclear, a recurring confusion in the standup format, a backlog that needs some basic grooming. Pick something small, propose it as an experiment, and make it easy for the team to say no. The goal is to demonstrate that you can improve things without disrupting what is working.

Resist the urge to tackle the big problems yet. You have probably identified several significant issues by now. Resist the urge to address them all at once. Trust takes time to build, and your ability to influence the bigger issues depends on the credibility you are building right now.

---

Week 4: Reflect and Align

In your fourth week, the goal is to consolidate what you have learned and align with your manager and key stakeholders on what you are seeing.

Have a check-in with your manager. Share what you have observed - not a list of problems, but a thoughtful summary of the team's strengths, the dynamics you have noticed, and the areas where you think you can add value. Ask for their perspective on your read of the situation.

Run your first retrospective. By now you have enough trust and context to facilitate a retrospective that feels genuine rather than performative. Use a format that invites honest reflection. Be transparent that you are still learning the team's context, and frame the retrospective as a shared exploration rather than an assessment.

Write down your 60-day and 90-day intentions. Based on everything you have learned, what do you want to focus on in the next two months? What are the two or three most important things you can do to help this team? Writing this down - even just for yourself - helps you move from observation mode to intentional action.

---

What to Avoid in Your First 30 Days

A few patterns that consistently undermine new Scrum Masters:

Comparing the team to your last team. "At my last company, we did it this way" is a phrase that erodes trust quickly. Every team is different. What worked elsewhere may not work here.

Trying to fix everything at once. Prioritization is a core Scrum value. Apply it to your own work. Pick the most important thing and do it well.

Skipping the relationship-building to focus on process. Process improvements that are not grounded in trust rarely stick. The relationships you build in the first 30 days are the foundation for everything else.

Being invisible. The opposite mistake is also common - being so careful not to overstep that you become a passive observer. The team needs to know you are present, engaged, and genuinely interested in helping them succeed.

---

The 30-Day Summary

Week	Primary Focus
Week 1	Orient and observe — attend ceremonies, read everything, meet stakeholders
Week 2	Build relationships — 1:1s with every team member, establish PO partnership
Week 3	Facilitate lightly — take over ceremonies, identify one small improvement
Week 4	Reflect and align — check in with manager, run first retro, set 60/90-day intentions

The first 30 days are an investment. Done well, they give you the context, the relationships, and the credibility to do the real work of a Scrum Master: helping a team continuously improve.

---

If you are preparing to start your first Scrum Master role and want to talk through your onboarding strategy, book a free consultation. You might also find What Does a Scrum Master Do Day to Day? useful for grounding your expectations before you start.