Learn 7 case studies+project management+dealing w difficult people/challenging situations for scrum master interview
InstructorPaul Ashun
The use of short stories and 'confessions' helps illustrate practical challenges on the ground, such as handling team dynamics and specific role-based problems.
Editorial course preview
These 4 complementary views highlight concrete, legible examples from the course presentation.
This overview slide introduces seven case study confessions covering Scrum pitfalls such as tools versus people, release planning perils, and bloated bug backlogs.
This slide introduces Confession 4 regarding the difference between Stand Ups and Sprint Reviews, illustrated with cartoons of teams using Kanban boards and burndown charts.
This slide illustrates the concept of retrospective regret in Scrum, using a burn-down chart and team dialogue to highlight questions about what worked and what could be improved.
This slide outlines key topics including case studies, lessons learned to improve development methods, working with teams, and delivering your project.
Instruction provides a clear presentation of the Scrum Master role through easily understandable, real-world examples.
One sampled review suggests that the curriculum omits technical processes like measuring velocity or building detailed release plans, focusing instead on basic scenarios. Note that signals regarding these omissions come from reviews dated before the displayed update; the update label does not prove a correction has been made.
The curriculum omits technical processes like measuring velocity or building detailed release plans, focusing instead on basic scenarios. Note that signals regarding these omissions come from reviews dated before the displayed update; the update label does not prove a correction has been made.
The target audience is somewhat ambiguous, as some signals suggest it requires more base knowledge than expected for absolute beginners.