SAFe SSM study plan

Map at least 8 distinct Scrum Master accountabilities in a SAFe environment to the Scrum framework elements they serve

Write a one-page comparison contrasting team-level Scrum events with ART-level events, citing one example of each from your own organization or a hypothetical ART

Define the three pillars of empiricism and pair each with a concrete SAFe artifact or ceremony that supports it

Draft a personal role charter stating your Scrum Master stance (servant leader, coach, facilitator, change agent) in your own words

Categorize 10 realistic impediments by type (technical, organizational, dependency, people) and assign each an escalation path (team, ART, portfolio)

Write coaching plans for three scenarios: a blocked developer, a conflict between two team members, and a disengaged team member

Contrast servant leadership with directive management by writing 5 behavioral pairs showing what you would do differently in each case

Facilitate a 15-minute stand-up or retrospective in practice and record self-observation notes against a facilitation checklist

Sequence all iteration events into a two-week calendar, listing the inputs, outputs, and Scrum Master responsibility for each

Write five facilitation scripts covering iteration planning kickoff, capacity discussion, story-point estimation, daily stand-up, and retrospective opening

Diagnose six common iteration anti-patterns (for example, stand-up as a status report) and prescribe a specific countermeasure for each

Explain how backlog refinement is scheduled and prepared so the team arrives at iteration planning with ready stories

Interpret team metrics such as velocity, predictability, and flow on a sample dataset and write three findings from the trends

Design a retrospective format that produces at least three improvement items, each with an owner and a due date

Run a 30-minute mock iteration-planning session (with a peer or self-recorded) and log every point where you deviated from the script

Differentiate when the Scrum Master facilitates versus participates across five concrete situations

Walk through the full PI Planning agenda across both days and list the Scrum Master's specific responsibility in each segment

Build a pre-PI readiness checklist with 10 verifiable items covering team backlog, capacity, dependencies, and logistics

Draft five team PI objectives and critique each against the SMART criteria and the committed-versus-uncommitted distinction

Explain the Scrum Master's role in dependency mapping and in ROAMing risks, including what to escalate to the RTE

Break down the Inspect and Adapt structure and write the Scrum Master's contribution to the system demo, the quantitative measurement, and the problem-solving workshop

Create eight retrospective prompts and a facilitation flow for the PI retrospective

Build an inspect-and-adapt action log linking five improvements to owners, due dates, and success measures

Describe how to close out a PI, including finalizing objectives, capturing carryover work, and preparing the team for the next PI

Identify six Scrum Master tasks that AI can credibly augment and three that must remain human-owned, justifying each boundary

Write and test two prompts (for example, retrospective synthesis and backlog refinement support) and evaluate the outputs against accuracy and usefulness criteria

Draft a responsible-AI checklist with five governance points covering data privacy, bias, human review, and transparency

Rework every missed item from the Domain 2 quizzes taken in weeks 1 through 4 and record the corrected reasoning

Complete two full timed practice exams and score at least 85% on the second attempt

Condense your notes into a one-page mental model of the Scrum Master role and iteration execution in SAFe

Drill 25 previously missed questions until no error type repeats

Rehearse 10 scenario-based judgment questions aloud, explaining the reasoning behind each answer choice