Scrum theory and accountabilities
You revisit empirical process control, transparency, inspection, and adaptation with examples from product and internal IT contexts. Accountabilities for Scrum Master, Product Owner, and Developers are contrasted with anti-patterns such as proxy ownership or hero culture. Myth-busting clarifies that agility is not absence of planning nor constant churn; it is disciplined learning cycles with explicit commitments. Discussion forums compare Scrum with lightweight Kanban hybrids where regulation or operations demand it.
Events with strong facilitation
Each event—Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective—includes facilitation prompts, timeboxing tactics, and remote-friendly practices such as async pre-reads and structured retrospectives that avoid blame. You practice converting vague discussions into actionable outcomes and ensuring psychological safety when metrics look bad. Video labs use short simulations so participants experience facilitator neutrality.
Product backlog excellence
Lessons emphasize ordering for value, slicing work small enough to finish inside a Sprint, and definition of ready versus definition of done. Story formats stay flexible but emphasize user-centric outcomes and testability. Refinement agendas balance technical debt visibility with feature discovery. Participants draft a sample backlog slice with acceptance criteria that developers could estimate without a three-hour meeting.
Metrics, improvement, and scaling challenges
The course closes with throughput and predictability signals, healthy versus toxic uses of velocity, and improvement backlogs that capture systemic issues. Scenarios address multi-team dependencies, shared services bottlenecks, and when to escalate organizational impediments beyond the team. You leave with a retrospective facilitation plan you can run in your workplace the following week.
Continuing education and community
You receive pointers to facilitator communities, reputable agile podcasts, and advanced courses for product ownership or technical excellence without commercial hype. Reflection prompts help you identify which Scrum Master stances you want to strengthen next, such as teacher, coach, or change agent. Coaches remain available asynchronously for two weeks to comment on your first facilitated event notes. Graduates gain access to a quarterly community call focused on difficult organizational impediments.
