SSM 無料問題集「Scrum SSM (6.0) - SAFe® Scrum Master」

（A）Understands and empathizes with others

（B）Thinks about the day-to-day activities

（C）Focuses on individual task metrics

（D）Uses authority rather than persuasion when necessary

（A）Reward

（B）Purpose

（C）Mastery

（D）Recognition

（E）Autonomy

（F）Responsibility

（A）throughput

（B）average WIP in the system

（C）average cycle time

（D）backlog WIP

（A）M-shaped

（B）I-shaped

（C）E-shaped

（D）T-shaped

（A）By using Cumulative Flow Diagrams which objectively measure bottlenecks and variation in the flow which could be due to systemic factors

（B）By establishing a Kanban board to visualize the flow of work within Kanban team and aligning with the Program and the rest of the teams

（C）By estimating team velocity and comparing it across Iterations for continuous improvement

（D）By creating Classes of Services and Policies to execute the work in a way that is aligned with Program and Large Solution Levels

（A）To fulfill the SAFe PI Planning requirements

（B）To provide an optional quality check

（C）To give Product Owners the opportunity to provide feedback on the team increment

（D）To enable faster feedback by integration across teams

（A）Assign to the team best suited to solve

（B）Use as direct input into the PI Planning session that follows

（C）Assign points or prioritization levels

（D）Calculate for cost before continuing

（A）To review each team's progress on its Stories

（B）To review the Agile Release Train's progress toward its PI Objectives

（C）To focus on Agile Release Train process improvement

（D）To demo Features to Product Management

（A）By establishing communication between different teams

（B）By creating a culture of shared responsibility

（C）By committing to a balance of speed and quality

（D）By identifying a collaborative approach to deployment

（A）When allocating functions to subsystems

（B）When development teams are empowered, self-organized, and allow the design to emerge

（C）When identifying the selection of common platforms

（D）When defining subsystems and interfaces

（A）Simplicity, the art of maximizing the amount of work not done, is essential

（B）The most efficient and effective method of conveying information to and within an Agile Team is face- to-face conversation

（C）The best architectures, requirements, and designs emerge from self-organizing teams

（D）Working software is the primary measure of progress

（A）Demoing the system

（B）Prioritizing the backlog

（C）Testing the system

（D）Improving flow

（A）Velocity

（B）Queue length

（C）Average WIP

（D）Code quality