Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Communication
Rewrite an update for two different readers, cutting extra lines
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
Chapter 2
Facilitation
Guide a group from complaints to actions it agrees on
What you'll learn
Session outcome
Diverge and converge
Facilitative listening
Parking lot
Practice
Run a planning-poker estimation in 15 minutes15 min
Run a Mock Retrospective with Friends30 min
Chapter 6
Metrics and measurement
Pick a success measure and define exactly how it's calculated
What you'll learn
Success metric
Guardrail metric
Vanity metric
Practice
Read a Product Dashboard and Write a Memo15 min
Chapter 6
Risk management
Write what could go wrong, rank each risk, name owners
What you'll learn
Likelihood and impact
Clear risk statement
Risk owner
Mitigation or contingency
Practice
Build a Risk Register for a Group Project20 min
Chapter 7
Process mapping
Map a real process, then check it with the team
What you'll learn
Steps, decisions, owners
Real process path
Process bottleneck
Practice
Map a Familiar Process and Find the Bottleneck15 min
4 more in the plan
Working with othersContribute to group work, ask for help and credit teammatesCh 2
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Problem solvingTest each possible cause of a problem instead of guessingCh 4
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 4
What you'll learn
The hidden assumption
Argue the other side
The base rate
Fact vs inference
Wanting it to be true
Practice
Spot the Weak Link in an Argument10 min
Change managementDraft a change announcement and name who might resist itCh 7
What you'll learn
Adoption, not delivery
The ADKAR model
Stakeholder mapping
Where resistance lives
The change story
Practice
Write a launch announcement for a process change20 min
Draft a Change Announcement Email10 min
Your plan
Chapter by chapter.
11 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a Scrum Master
StartFree
2~2 wks
Help a group reach its own answer
Skills
3~2 wks
Plan an A/B test and decision rule
Project
4~2 wks
Find the cause before you fix it
Skills
51–2 wks
Talk to two working scrum masters
People
6~2 wks
Track progress and risks with real numbers
Skills
7~2 wks
Map how the work changes for everyone
Skills
8~2 wks
Run a retrospective and close its actions
Project
91–2 wks
Answer the questions interviewers ask
Interview
101–2 wks
Decide how you will get in
Decide
11on your timeline
Send your first applications
Apply
The job
What a Scrum Master does
Helps a product or software team plan work, run meetings, and remove blockers so they deliver updates on time.
The work
Coordinate sprint planning, daily standups, reviews, and retrospectives
Coach the team on agile ways of working and continuous improvement
Remove blockers by working with other teams, leaders, and vendors
Track work progress and risks using boards, metrics, and clear status updates
Protect the team from distractions and unplanned work during a sprint
Facilitate decisions and healthy conflict so the team stays aligned
Support product and engineering to keep the backlog ready for upcoming work
A typical day
Start with a short standup, then follow up on blockers and dependencies
Facilitate planning or refinement sessions and keep notes and action items
Check the board and metrics, then share a simple status update to stakeholders
Coach 1:1 with team members and help improve team agreements and flow
Tools
Agile boards: Jira, Azure DevOps, TrelloDocs and notes: Confluence, Notion, Google DocsCommunication: Slack, Microsoft TeamsWhiteboarding: Miro, MuralSpreadsheets: Excel, Google SheetsVideo meetings: Zoom, Google Meet
Ways in
There is more than one route.
Ways to study
Bachelors degree in business, information systems, engineering, or a related field
Diploma or certificate in project management or product delivery
Agile training courses with hands-on practice and a mentor
Workshops in facilitation, coaching, and team communication
How people get their first job
Join a software team as a project coordinator, delivery coordinator, or business analyst
Volunteer to run standups and retrospectives for a student or open-source team
Earn an entry agile certification and apply it in a real team project
Build a portfolio case study showing a sprint plan, board setup, and retro outcomes
Intern in product, operations, or engineering and focus on team process support
How long does it take to become a scrum master with Welica?
The plan is 11 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelors degree in business, information systems, engineering, or a related field, diploma or certificate in project management or product delivery, agile training courses with hands-on practice and a mentor, or workshops in facilitation, coaching, and team communication.
What is free?
Chapter 1, See the work of a Scrum Master, is free for good. Premium unlocks the rest of the plan.