Your First 90 Days as a Scrum Master: A Practical Plan

Congratulations, you got the role. Now the real work begins. Your first 90 days as a Scrum Master shape how your team sees you for a long time. The goal is not to change everything. It is to understand the team, earn trust, and make a few improvements people can feel.

Days 1 to 30: listen and learn

Resist the urge to fix things in week one. Every team has history you cannot see yet.

• Meet one-on-one with each team member, the Product Owner and your manager. Ask what is working, what is frustrating, and what they wish would change.
• Attend every event as an observer first: daily Scrum, planning, review and retrospective.
• Learn the tools. Find out how work flows through Jira or Azure DevOps and where it gets stuck.
• Map the stakeholders: who depends on this team, and who does the team depend on?
• Write down what you notice. Do not share conclusions yet.

Days 31 to 60: start facilitating and pick one improvement

By now you understand the team’s patterns. Start taking ownership of the events and choose one visible problem to solve together.

• Run the retrospective yourself and make sure it ends with one or two concrete actions, each with an owner.
• Work with the Product Owner so the top of the backlog is clear and ready before planning.
• Pick one recurring blocker, such as slow approvals or unclear requirements, and work to remove it.
• Keep the daily Scrum short and focused on the sprint goal.

Days 61 to 90: build habits and show progress

• Check whether the actions from your retrospectives are actually happening.
• Share a simple picture of progress with your manager: what changed, what improved, what is next.
• Coach the team to own more of the process themselves, so it does not depend on you.
• Ask for feedback on how you are doing. It shows confidence, not weakness.

Common mistakes to avoid

• Acting like the team’s manager or assigning tasks.
• Changing every process at once.
• Turning the daily Scrum into a status report for leadership.
• Skipping retrospectives when the team is busy, which is exactly when they matter most.

What success looks like at day 90

You do not need perfect metrics. Success at 90 days looks like this: the team trusts you, the events feel useful instead of routine, one or two real problems are gone, and your manager can see the difference. That foundation is what lets you grow into a senior Scrum Master, Agile coach or delivery lead.