From the course: Agile Challenges Weekly Tips
Unlock the full course today
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Absentee scrum master
- Even scrum masters are allowed to take a vacation once in a while. So, when this happens, there are steps you should take to make sure the team continues to run smoothly. The first and best option is to find someone to fill in for the scrum master. Ideally, your organization has a scrum master community of practice, so your scrum master can reach out to their peer group and find a volunteer to help the team. Another option is to assign another team member to the role temporarily. This is actually harder than pulling in a seasoned scrum master to help out. Asking someone on the team to act as the scrum master is very hard because that person has to context which throughout the whole sprint. So while you can do this, I would avoid it if I could. Next, the scrum master needs to set expectations that the team should continue to hold all the scrum events while they're away. Believe it or not, some new scrum teams feel like the events only provide value to the scrum master and they'll…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
(Locked)
We don't get along2m 50s
-
(Locked)
We don't work together2m 27s
-
(Locked)
Everyone is still siloed2m 37s
-
(Locked)
No one knows what we're doing2m 47s
-
(Locked)
We can't see beyond our current sprint3m 15s
-
(Locked)
Our sprint commitments are wrong2m 55s
-
(Locked)
We don't have needed skills2m 28s
-
(Locked)
Everything gets stuck in testing2m 57s
-
(Locked)
Let's go back to waterfall3m 12s
-
(Locked)
Stand-up is dysfunctional3m 14s
-
(Locked)
No one contributes in retrospective2m 57s
-
(Locked)
The team doesn't know what to build2m 9s
-
(Locked)
Distributed team collaboration3m 19s
-
(Locked)
Clues in your burndown chart4m 1s
-
(Locked)
No one comes to sprint review2m 22s
-
(Locked)
No one speaks up in planning2m 23s
-
(Locked)
No one wants to learn a new skill2m 57s
-
(Locked)
We don't have time for new skills2m 38s
-
(Locked)
We need a specialist2m 19s
-
(Locked)
Cross-team dependencies2m 14s
-
(Locked)
What time is stand-up?2m 34s
-
(Locked)
Building open communication2m 40s
-
(Locked)
Working with remote stakeholders2m 24s
-
(Locked)
Engaging sponsors with remote teams2m 30s
-
(Locked)
Coaching the resource manager2m 45s
-
(Locked)
Building a community of practice2m 44s
-
(Locked)
Dealing with change management3m 24s
-
(Locked)
Influencing decision makers2m 38s
-
(Locked)
Scrum master speaks for the team2m 34s
-
(Locked)
What to do when no obstacles are raised2m 59s
-
(Locked)
The team always has carry over stories3m 11s
-
Maintaining architectural alignment3m 16s
-
(Locked)
The team is burned out2m 44s
-
(Locked)
Sprint zero lasts more than four weeks2m 9s
-
(Locked)
Solutioning in stand-up meeting2m 20s
-
(Locked)
Scrum master is assigning tasks2m 52s
-
(Locked)
Scrum master is a team contributor2m 50s
-
(Locked)
Projects always have a phase two2m 5s
-
(Locked)
Absentee scrum master2m 19s
-
(Locked)
Stand-up meeting is more than 15 minutes2m 25s
-
(Locked)
No one listens in the stand-up meeting2m 14s
-
(Locked)
The story is not ready for sprint planning2m 44s
-
(Locked)
Acceptance criteria are unclear2m 41s
-
(Locked)
Story sizing is inconsistent2m 16s
-
(Locked)
The team always overcommits2m 43s
-
(Locked)
The team always undercommits2m 8s
-
(Locked)
The team does not swarm2m 32s
-
(Locked)
Product owner says how to build the product2m 38s
-
(Locked)
Shifting to a more agile mindset3m 1s
-
(Locked)
The scrum master uses a commanding style3m 10s
-
(Locked)
The team finishes sprints early2m 29s
-
(Locked)
Product owner is never around2m 47s
-
(Locked)