The first 90 days are an important period for a new Scrum Master.
The goal is not to change everything immediately, but to understand
the team, build trust and gradually improve effectiveness.
Days 1–30: Learn and Observe
Start by understanding the people, product, organization and
current way of working.
Meet the Team
Understand roles, responsibilities, concerns and expectations.
Understand the Product
Learn the product, users and Product Goal.
Observe Scrum
Observe events and how the team actually works.
Identify Impediments
Look for recurring obstacles affecting the team.
What to Avoid in the First 30 Days
- Trying to change everything immediately.
- Judging the team too quickly.
- Making promises before understanding the situation.
- Taking over the team's responsibilities.
Days 31–60: Build Trust and Improve
Once you understand the environment, start working with the
team on practical improvements.
Build Relationships
Strengthen trust with Developers, Product Owner and stakeholders.
Improve Facilitation
Help Scrum events become more useful and focused.
Address Impediments
Work with the appropriate people to remove important obstacles.
Support Improvement
Help the team identify and test practical improvements.
Focus on a Few Improvements
Avoid creating a long improvement list.
Choose a small number of issues that can make a meaningful difference.
Example:
If unclear Product Backlog Items are repeatedly causing delays,
work with the Product Owner and Developers to improve shared
understanding before the Sprint begins.
Days 61–90: Enable the Team
By this stage, the focus should gradually move from fixing
individual problems toward improving the team's ability to
solve problems itself.
Encourage Self-Management
Let the team take ownership of appropriate decisions.
Strengthen Collaboration
Encourage knowledge sharing and collective ownership.
Improve Team Effectiveness
Help the team identify patterns and improve its way of working.
Address Organizational Issues
Help escalate and address wider impediments.
90-Day Review
At the end of 90 days, review what you have learned and
what has changed.
Team
Is collaboration improving?
Scrum
Are Scrum events and practices useful?
Impediments
Are important obstacles being addressed?
Improvement
Is the team learning and adapting?
Useful Questions
Team
"What does this team need most from me?"
Product
"Do we understand the product direction?"
Impediments
"What is repeatedly slowing the team down?"
Improvement
"What should we improve next?"
Common Mistakes
Changing Too Much
Introducing many changes before understanding the context.
Trying to Impress
Focusing on appearing busy instead of creating value.
Becoming the Manager
Taking control of the team's work and decisions.
Ignoring Relationships
Focusing only on Scrum practices and tools.
Remember:
Your first 90 days are about learning, building trust and
creating sustainable improvement—not proving that you have
all the answers.
Simple 30-60-90 Plan
Days 1–30
Learn, observe and build relationships.
Days 31–60
Improve collaboration and address key impediments.
Days 61–90
Enable self-management and continuous improvement.
Key Takeaway
A successful first 90 days starts with listening and
understanding before making major changes.
Build trust, address meaningful problems and gradually help
the Scrum Team become more effective and self-managing.