DASSM Disciplined Agile Senior Scrum Master Exam Topics and Questions

This topic establishes the foundation for how you diagnose and improve team maturity. You need to recognise the Tuckman stages on sight, connect observed behaviours to the right stage, and choose interventions that fit where the team actually is. The cost comes when you misread the stage or apply a solution that belongs somewhere else in the cycle.

How Team Development for high performance teams is tested

Fourteen percent of the exam means roughly one item in seven. Expect scenarios that describe team behaviour without naming the stage outright: low trust, conflict over process, smooth delivery, or a dip after a membership change. You must infer the stage and select the response that matches it. Items often hinge on timing. Pushing for high performance when a team is still forming wastes energy and marks. Another trap is mistaking storming for dysfunction and trying to suppress it instead of facilitating through it. The outline wants you to solve, not just label, so the correct answer usually involves an action rather than a definition.

Where the first topic focused on group stages, this one turns to the internal and interpersonal capacities that let a team reach them. Emotional intelligence underpins every difficult conversation, every moment of feedback, and every decision to speak up or stay silent. The exam tests whether you understand its components well enough to apply them and whether you can connect psychological safety and diversity to team outcomes rather than treating them as compliance goals.

How Emotional intelligence for high performance teams is tested

Ten percent means about one item in ten. Questions often describe a team interaction, then ask which component of emotional intelligence is at play or what the senior scrum master should model. You will see scenarios involving a team member who struggles to read the room, a leader who reacts defensively, or a group that avoids hard topics. The correct answer usually names the specific component, self-awareness, self-regulation, motivation, empathy, or social skill, and ties it to an outcome. Psychological safety items test whether you know why it matters, not just that it does. The trap is choosing the option that sounds supportive but does nothing to change the environment. Look for actions that reduce interpersonal risk and make dissent safer.

Scaling is where single-team practices meet organisational complexity. You move from one backlog and one retrospective to multiple teams, shared dependencies, and architecture that cannot change overnight. The exam assumes you already work in a scaled environment and wants proof that you can choose the right intervention when coordination breaks down or agility dilutes across layers. Six percent is a smaller weight, but the questions demand systems thinking.

How Tactical scaling in complex situations is tested

Six percent translates to roughly one item in seventeen, so expect two or three scaling questions in total. They often present a symptom: duplicate work across squads, a bottleneck in shared services, or a dependency that blocks three teams at once. You must identify what kind of scaling challenge it is and select the response that preserves agility instead of layering on ceremony. The wrong answers usually add process, meetings, or approval gates. The right one reduces coupling, clarifies ownership, or changes the team topology. Another common trap is choosing the option that works for a single team but ignores the wider system. The outline wants you to think beyond the team boundary.

At twenty-two percent, this is the heaviest topic on the outline. It spans two layers of the Disciplined Agile framework: DevOps, where you deliver software, and value stream, where you align that delivery to business outcomes. The breadth means you need to know both the conceptual layer and the goal diagrams well enough to pick the right decision point when a scenario lands. Most candidates lose marks by choosing answers that sound agile but ignore the toolkit structure.

– The DevOps layer and test-first thinking

The Disciplined DevOps layer covers everything from ideation through deployment and operations. Items in this area ask you to recognise when a problem sits in this layer and which part of the toolkit addresses it. Test-first is not only about unit tests. The outline treats it as a quality gate for requirements: write the acceptance criterion before you write the story, and define done before you start the work. Exam scenarios often describe vague stories, shifting scope, or rework caused by late clarification. The correct answer usually involves pulling the quality conversation earlier. Definition of done is contextual. The exam may give you a situation and ask what done should include, or present a team whose done is too narrow and ask what is missing. Watch for answers that confuse done with deployed or done with accepted by the product owner.

– The value stream layer and toolkit application

The value stream layer sits above DevOps and organises teams around end-to-end customer outcomes. Items here test whether you can distinguish a DevOps problem from a value stream problem and whether you know which goal diagram to reach for. A team struggling with build times is DevOps. A team building the wrong thing because no one validated the business case is value stream. The DA toolkit is a set of goal diagrams, each with decision points and options. The exam expects you to know the goals by name and to match a scenario to the right one. You will not be asked to recall every option on a diagram, but you must know which goal applies when coordination fails, when planning breaks down, or when governance becomes a bottleneck. The trap is choosing a response that treats the symptom instead of using the goal to surface the underlying decision.

How Removing Impediments is tested

Twenty-two percent means one item in five comes from this topic. Expect scenario-heavy items that describe an impediment, then ask you to classify it, choose the right goal diagram, or select the intervention that fits the layer. Many questions hinge on recognising whether the blockage is technical, organisational, or about unclear outcomes. Wrong answers often propose a meeting, a new role, or a process addition. Right answers usually simplify, clarify ownership, or apply a specific goal from the toolkit. Another common error is picking the option that removes the symptom without addressing the decision that caused it. The outline rewards you for knowing when to escalate, when to coach, and when to change the structure. Test-first and definition of done appear in their own items, often as the hinge between two plausible options.

After impediments comes the question of how teams work together when no single squad owns the outcome. This topic focuses on the Coordinate Activities process goal and on changing team structure to improve flow. You are expected to know when coordination is the problem and when the structure itself needs to change. The exam distinguishes between adding a sync meeting and redesigning how value moves through the organisation.

How Coordinating and collaborating across teams is tested

Ten percent gives you roughly one item in ten. Questions describe missed handoffs, duplicated effort, or delays caused by dependencies between teams. You must decide whether the answer lies in better coordination, a change to team composition, or a shift in how work is allocated. The Coordinate Activities goal appears by name in some items and by implication in others. Wrong answers often add ceremony: a new meeting, a coordination role, or a dependency board that no one updates. Right answers reduce the need to coordinate by changing boundaries, collocating skills, or aligning teams to value streams. Another trap is choosing the option that improves visibility without improving flow. The outline wants you to optimise delivery, and visibility alone does not do that.

Conflict is inevitable in high-performing teams, and this topic tests whether you can tell productive disagreement from destructive argument. You need to know the Thomas-Kilmann modes well enough to choose the right one for the situation, and you must recognise language that escalates versus language that de-escalates. Twelve percent makes this a mid-weight topic, and most of the challenge lies in reading tone and intent from written scenarios.

How Conflict management for high performance teams is tested

Twelve percent means roughly one item in eight. Expect scenarios that describe a disagreement, then ask which conflict mode applies or what the senior scrum master should say next. The Thomas-Kilmann model has five modes: competing, collaborating, compromising, avoiding, and accommodating. Items often present two modes that sound reasonable and hinge on context: is the issue worth the time, is the relationship at risk, is there a power imbalance. Healthy conflict items test whether you can distinguish challenge from attack. The wrong answer usually involves smoothing over the issue or letting the loudest voice win. The right one names the tension, invites other perspectives, and keeps the focus on the problem rather than the person. Language matters. Watch for options that include blame, sarcasm, or absolutes like always and never. Those are the unhealthy choices.

This is the heaviest topic at twenty-six percent, covering planning, scope, metrics, and governance. It asks you to balance just-enough planning with the need for predictability, and to choose measurements that drive improvement rather than theatre. The breadth is wide: you move from release planning through five levels of scope to Goal-Question-Metric and OKRs, then into the Govern Delivery Team goal. Candidates often lose marks by over-planning or by selecting vanity metrics that look good but change nothing.

– Sufficient planning and the five levels of scope

Sufficient planning means doing enough to reduce risk without pretending you can predict the future. The exam tests whether you know when to stop planning and start learning. Items describe teams that plan too much, teams that plan too little, and teams that plan the wrong things. The correct answer usually involves deferring detail, timeboxing the planning effort, or anchoring the plan to a learning milestone. The five levels of scope run from portfolio through product, release, iteration, and daily. Each level has a different audience and a different planning horizon. Exam scenarios often describe a mismatch: a product owner trying to manage portfolio scope, or a team planning three releases out in iteration-level detail. You must recognise who should focus on which level and what happens when that boundary blurs. The Release Planning goal diagram appears in problem-solving items, usually when a release is late, scope is unclear, or stakeholders expect a fixed date and fixed scope together.

– Metrics, GQM, OKRs, and what works

Metrics are where planning meets accountability, and the outline wants you to know the difference between measurement that informs and measurement that distorts. Items ask what to measure, how to choose a metric, and what goes wrong when you measure the wrong thing. Velocity, code coverage, and story points all appear in scenarios, often as examples of measures that teams game or that drive the wrong behaviour. The right answer usually focuses on outcomes, flow, or quality rather than output. Goal-Question-Metric is a framework for designing measures: start with the goal, ask what question would tell you if you are reaching it, then pick the metric that answers the question. OKRs, Objectives and Key Results, work the same way but with a cadence and a scoring model. Exam items present a performance problem and ask you to design a metric or to critique one that is already in use. The Govern Delivery Team goal appears when the question involves oversight, reporting cadence, or what governance should measure without slowing the team down.

How Pragmatic Planning and Reporting is tested

At twenty-six percent, this topic accounts for more than one question in four. Expect a mix of planning scenarios, scope-level questions, and metrics problems. Planning items often describe a team stuck in analysis or a stakeholder demanding a date before the work is understood. You must choose the response that brings planning into proportion. Scope-level items hinge on recognising who owns which level and what happens when someone operates at the wrong altitude. Metrics questions are the hardest. They describe a measure that sounds reasonable, then ask what is wrong with it or what would work better. The trap is choosing the metric that is easiest to collect rather than the one that answers the goal. GQM and OKR items expect you to reverse-engineer the goal from a proposed measure or to spot when a key result does not connect to its objective. Governance items test whether you know what the Govern Delivery Team goal covers and when oversight becomes interference.