Sign in
Home/Scrum.org/Professional Scrum Master II (PSM II)/Free questions

Professional Scrum Master II (PSM II) — Free Practice Questions

10 free sample questions from a bank of 192, with the correct answers and explanations. No signup required — start practising right now.

1A Scrum Master is not only a servant-leader to the Scrum Team and organization, it's also considered a management position. Which three activities describe what a Scrum Master manages as reflected by the Scrum Guide? (Choose three.)
  • Reporting on the performance of the Sprint.
  • The way Scrum is understood and enacted within the organization.
  • Managing the capacity and utilization of each Development Team member.
  • Managing the process in which Scrum is applied.
  • Managing the Product Backlog items and work in the Sprint Backlog.
  • Removing organizational impediments that limits the team's progress and productivity.
Answer: B, D, F

The short version

BDF — The Scrum Master manages process, enactment and impediment removal. It is a management role for how Scrum lives in the organization, not for people utilization or backlog content.

Key concepts in this question

  • Management of process: stewarding how Scrum is applied so events, roles and rules hold in practice.
  • Understanding and enactment: coaching the organization until Scrum values and empiricism guide daily work.
  • Organizational impediments: clearing systemic blockers that teams cannot remove alone to protect productivity.
  • Not people management: capacity, utilization and task assignment remain with self-managing Developers.
  • Not content ownership: Product Backlog and Sprint Backlog decisions belong to Product Owner and Developers respectively.

Why BDF is correct

B fits because the Guide frames the Scrum Master as ensuring Scrum is understood and enacted across teams and stakeholders. D fits because managing the process of application is the explicit accountability that keeps empiricism intact. F fits because removing larger organizational impediments is central to enabling flow and is often beyond team reach. Together they describe management of the system, not of individuals.

Why the others are wrong

  • A. Sprint performance reporting is not a managed output; transparency comes from team radiators and Reviews, not status reports.
  • C. Individual capacity and utilization control contradicts self-management and confuses the role with line management.
  • E. Owning backlog items and Sprint work confuses the role with Product Owner and Developer accountabilities.

PSM-II exam tip

Scrum Master manages equals process plus enactment plus org impediments; never people utilization, reports, or backlog content.

2Steven is a Scrum Master asked to assist in creating five new Scrum Teams that will be working to build a highly anticipated product. He talks with them about the importance of being able to integrate their Increments by the end of their Sprints. This includes the first Sprints. The product is very important to both the end users and the organization. Of the choices raised by future team members, what would Steven encourage?
  • Each Scrum Team delivers Increments in its own code branch. After UAT is performed at the Sprint Review, the code branch is isolated until enough Increments are considered acceptable. All code branches will then be merged during the release phase.
  • Each Scrum Team delivers functionality at the end of each Sprint. New Product Backlog items will then be added to the next Sprint Backlog to integrate their functionality with the other teams to create a unified Increment.
  • All Scrum Teams agree on a mutual understanding of 'done' that defines all work necessary to deliver a potentially shippable Increment that includes all previous Increments delivered for the product.
  • Wait until enough of the infrastructure and architecture is in place before starting the first Sprints. This will increase the success of delivering integrated Increments in Sprint 1.
Answer: C

The short version

C — agree a shared Done for one integrated Increment. Five teams building one product must integrate from Sprint one. A mutual Definition of Done makes Done mean the same everywhere and forces additive tested work.

Key concepts in this question

  • Definition of Done: Shared quality standard deciding when work is truly complete.
  • Integrated Increment: All teams work must combine into one usable whole each Sprint.
  • Branch isolation risk: Separate branches plus late merges hide conflicts and delay learning.
  • Future integration debt: Deferring integration to later Sprints creates big bang risk.
  • Architecture runway myth: Waiting for perfect foundations delays value and feedback.

Why C is correct

C is correct because multiple Scrum Teams on one product must mutually define Done so every Increment is additive, tested and compatible, exactly as the Scrum Guide requires. Shared Done creates transparency about completeness and makes integration continuous from the first Sprint. Steven encourages this because only a common bar lets five teams deliver one potentially shippable whole instead of five fragments.

Why the others are wrong

  • A. Isolated branches until release defers integration and guarantees painful late merges.
  • B. Building separately then adding integration items next Sprint plans for disjoint work instead of integrated Done.
  • D. Waiting for infrastructure before Sprint one delays empiricism and assumes upfront design reduces risk.

PSM-II exam tip

Multiple teams, one product, means one shared Done and integrated Increment every Sprint.

3What would be typical Scrum Master activities during the Sprint?
  • Monitor the progress of the Development Team and assigning tasks.
  • Remove impediments and facilitating inspection and adaptation opportunities as requested or needed.
  • Avoiding conflicts and escalating to the line managers if conflicts occur.
Answer: B

The short version

B — Remove impediments and enable inspection and adaptation. The Scrum Master serves the team by clearing blockers and ensuring Scrum events are productive, not by directing daily work or assigning tasks.

Key concepts in this question

  • Servant leadership: Scrum Master serves Developers, Product Owner and organization by fostering self-management rather than command and control.
  • Impediment removal: Proactively identifies and clears organizational, technical and interpersonal blockers that slow progress toward the Sprint Goal.
  • Inspection and adaptation: Protects and facilitates Daily Scrum, Sprint Planning, Review and Retrospective so the team can inspect progress and adapt its plan.
  • Self-management: Developers decide how to do the work and manage their own Sprint Backlog without task assignment from a manager figure.

Why B is correct

Scrum defines the Scrum Master as accountable for establishing Scrum and helping everyone understand its theory and practice. During the Sprint that means coaching on self-management, causing removal of impediments and ensuring productive opportunities to inspect and adapt when requested or needed. Monitoring progress for control or assigning tasks contradicts self-management and belongs to no Scrum accountability. Facilitation plus impediment removal is the enduring day to day pattern described in the Scrum Guide.

Why the others are wrong

  • A. Monitoring progress and assigning tasks replaces self-management with directive management and violates Developer autonomy.
  • C. Avoiding conflict and escalating to line managers abandons coaching and facilitation and reintroduces hierarchical control outside Scrum.

PSM-II exam tip

Remember servant over supervisor: if an answer has the Scrum Master assigning, monitoring or escalating, reject it and choose coaching plus impediment removal.

4The Scrum Master is responsible for the process in which Scrum is adopted and enacted.
  • True
  • False
Answer: A

The short version

A — True, the Scrum Master owns effectiveness of the Scrum process. This accountability covers establishing Scrum, coaching correct enactment and helping the team and organization adopt empirical control.

Key concepts in this question

  • Process accountability: Scrum Master is accountable for effectiveness of the Scrum Team and for establishing Scrum as defined in the Scrum Guide.
  • Adoption and enactment: Covers teaching, coaching and mentoring so events, artifacts and accountabilities are understood and lived, not performed mechanically.
  • Organizational change: Works with leaders and stakeholders to remove systemic impediments to agility and to foster an empirical product approach.
  • Enabling not policing: Accountability means enabling understanding and improvement, not dictating process or owning delivery outcomes alone.

Why A is correct

The Scrum Guide states the Scrum Master is accountable for establishing Scrum and for the effectiveness of the Scrum Team. That includes helping everyone understand Scrum theory and practice both within the team and the wider organization. Adoption means introducing the framework correctly, while enactment means sustaining it through coaching, impediment removal and continuous improvement. A statement assigning process responsibility to the Scrum Master therefore matches the defined accountability exactly and deserves a True verdict.

Why the others are wrong

  • B. False would deny the explicit Scrum Guide accountability and would leave no single owner for establishing and sustaining Scrum effectiveness across the team.

PSM-II exam tip

Link process to Scrum Master instantly: effectiveness of Scrum equals Scrum Master accountability, value ordering equals Product Owner, turning work into Done equals Developers.

5As a Scrum Master, you observe that the Product Owner is not collaborating with the Development Team effectively. What action would you take?
  • Send the Product Owner to training.
  • Nominate a proxy Product Owner.
  • Act as the go-between.
  • Coach the Product Owner.
Answer: D

The short version

D — Coach the Product Owner toward better collaboration. The Scrum Master improves flow by teaching Product Owner behaviours and collaboration patterns, not by replacing, bypassing or sending the person away.

Key concepts in this question

  • Coaching stance: Scrum Master coaches Product Owner on backlog management, stakeholder collaboration and working agreements with Developers.
  • Product Owner collaboration: Effective delivery needs continual clarification, feedback and joint refinement between Product Owner and Developers.
  • Proxy anti-pattern: Nominating a proxy or acting as go-between hides the real collaboration gap and weakens direct communication.
  • Training timing: Formal training may help longer term but does not address the immediate observed behaviour in context as coaching does.

Why D is correct

Scrum Masters serve the Product Owner by helping find techniques for effective Product Goal definition, backlog management and stakeholder collaboration. When collaboration with Developers is weak, the effective move is direct coaching with examples, observation and feedback during refinement, planning and review. Coaching preserves accountability while building capability and keeps communication direct. Training, proxy or messenger options avoid coaching duty and entrench dysfunction.

Why the others are wrong

  • A. Sending the Product Owner to training outsources the problem and delays practical improvement in daily collaboration habits.
  • B. Nominating a proxy fragments accountability and creates indirect communication that Scrum explicitly seeks to avoid.
  • C. Acting as go-between makes the Scrum Master a bottleneck and prevents Developers and Product Owner learning to collaborate directly.

PSM-II exam tip

When you see poor collaboration, choose coach the accountability owner in place. Never choose proxy, messenger or reassignment as the Scrum Master response.

6A Scrum Master teaches those who are interested in the Development Team's progress that progress in Scrum comes from inspecting an Increment at the Sprint Review.
  • True
  • False
Answer: A

The short version

A — True, progress is inspected via the Increment at Sprint Review. Working software measured against the Definition of Done is the primary evidence of progress, not documents or activity reports.

Key concepts in this question

  • Working software as measure: Agile thinking treats a usable Increment as the clearest proof that value and understanding are advancing.
  • Sprint Review inspection: Stakeholders and Scrum Team inspect the Increment and emerging Product Backlog together and adapt direction.
  • Transparency: An integrated Increment made visible enables honest conversation about what is Done and what remains to be done.
  • Scrum Master teaching: Helps interested parties outside the team understand empirical progress instead of status reports or percent complete.

Why A is correct

Scrum is empirical, so progress must be inspected in the form of a potentially releasable Increment at the Sprint Review. The Scrum Master correctly teaches that stakeholders should look at working functionality, give feedback and shape next steps with the Product Owner. This replaces document driven or task-count views of progress with direct inspection of Done software. The statement therefore captures both the measure and the venue where that teaching happens, making True the only consistent verdict.

Why the others are wrong

  • B. False would imply progress can be judged without inspecting working software, which contradicts empiricism and the purpose of Sprint Review.

PSM-II exam tip

Anchor progress to Increment plus Review. Any option measuring progress by documents, hours or tasks completed is a trap for PSM-II.

7What is the most appropriate action for the Scrum Master to take if the Product Owner is having difficulties managing the Product Backlog?
  • Have the Development Team order the work instead of the Product Owner.
  • Have the Product Owner order the items based on size, having the Development Team work on the smallest items first.
  • Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize the flow of value.
  • Delegate the work to the Assistant Product Owner.
  • Delay the Sprint in order for the Product Owner to have enough time to prioritize the Product Backlog.
Answer: C

The short version

C — Help the Product Owner order for maximum flow of value. Coaching on value-based ordering preserves Product Owner accountability while building lasting backlog management skill.

Key concepts in this question

  • Value ordering: Product Backlog is ordered to maximize flow of value, considering risk, learning, dependencies and economics, not only size.
  • Product Owner accountability: Only the Product Owner is accountable for ordering, though Developers and Scrum Master may help clarify and refine.
  • Coaching over doing: Scrum Master teaches techniques for ordering and refinement rather than taking over the backlog directly.
  • Flow thinking: Small items first or team-ordered backlogs can suboptimize value if they ignore customer impact and feedback speed.

Why C is correct

The Product Owner remains accountable for ordering even when struggling, so the Scrum Master response is to offer help understanding that ordering serves value flow. Coaching might include impact mapping, cost of delay, vertical slicing and frequent stakeholder feedback. Having Developers order instead, sorting by size, delegating to an assistant or delaying the Sprint all violate accountability or disrupt cadence. Sustained improvement comes from guided practice in value based decisions during refinement.

Why the others are wrong

  • A. Having Developers order instead strips Product Owner accountability and confuses technical insight with value authority.
  • B. Ordering by size alone optimizes local efficiency and can starve high value larger items that need early feedback.
  • D. Delegating to an assistant fragments the single voice of the Product Owner and obscures accountability for value.
  • E. Delaying the Sprint breaks timeboxing and cadence and treats a coaching need as a scheduling problem.

PSM-II exam tip

Struggling Product Owner means coach on value flow. Never accept take over, sort by size, delegate or delay the Sprint.

8What action should a Scrum Master take if the Development Team has decided that Retrospectives are no longer necessary?
  • Start facilitating more productive and useful Retrospectives.
  • Suggest reducing the frequency of the Retrospectives.
  • Extend the Sprint time-box in order to fit the Retrospectives.
  • Comply with the team's decision.
Answer: A

The short version

A — Make Retrospectives productive and useful again. The Scrum Master protects continuous improvement by improving facilitation and outcomes, never by dropping or diluting the event.

Key concepts in this question

  • Mandatory Retrospective: Sprint Retrospective is a required event for inspecting people, process, tools and Definition of Done.
  • Facilitation quality: Boring or blaming sessions signal a facilitation problem, not proof the event lacks lasting value.
  • Continuous improvement: Even high performing teams have systemic impediments and collaboration patterns worth improving each Sprint.
  • Scrum Master service: Coaches the team on effective techniques, psychological safety and follow-through on improvement actions.

Why A is correct

The Retrospective exists so the Scrum Team can inspect itself and create a plan for improvements to be enacted in the next Sprint. If Developers deem it unnecessary, that usually reflects poor facilitation, repetitive format or missing follow-through. The Scrum Master should vary techniques, focus on actionable experiments and ensure improvements land in the Sprint Backlog. Reducing frequency, extending the Sprint or complying removes the engine of adaptation and lets dysfunctions persist unchecked across future Sprints.

Why the others are wrong

  • B. Reducing frequency weakens inspection cadence and signals that improvement is optional when busy or comfortable.
  • C. Extending the timebox to fit Retrospectives distorts Sprint cadence and confuses event effectiveness with duration.
  • D. Complying abandons accountability for Scrum effectiveness and allows the team to discard a pillar of empiricism.

PSM-II exam tip

Team rejects Retrospective equals fix facilitation. Never accept skip, reduce or comply options on PSM-II.

9As a Scrum Master, what would you strive for if five new Scrum Teams were to work on one product?
  • There should be five Product Owners, one for each Scrum Team.
  • The product has one Product Backlog and one Product Owner.
  • There should be five Product Backlogs and one Product Owner to manage them.
  • There should be five Product Backlogs and five Product Owners.
Answer: B

The short version

B — One product means one Backlog and one Product Owner. A single value ordering voice prevents fragmentation, conflicting priorities and split accountability across five teams.

Key concepts in this question

  • Single Product Backlog: All work for one product lives in one ordered Backlog so value trade-offs are explicit and transparent.
  • Single Product Owner: One person accountable for maximizing value and ordering, even when many teams contribute work.
  • Scaled alignment: Multiple teams pull from the same Backlog and coordinate dependencies through shared goals and events.
  • Fragmentation cost: Separate backlogs or owners create local optimization, duplicate work and competing definitions of priority.

Why B is correct

Scrum states a product has one Product Backlog and one Product Owner accountable for its ordering. With five teams on one product, that structure preserves a coherent Product Goal and a single ordering of value across all teams. Teams then select items in collaboration with the Product Owner and coordinate integration each Sprint. Multiplying owners or backlogs would fracture transparency, slow decisions and undermine the ability to deliver one integrated Increment each Sprint.

Why the others are wrong

  • A. Five Product Owners institutionalize conflicting priorities and destroy single accountability for value maximization.
  • C. Five Backlogs with one Owner overloads the Owner and hides cross-team value trade-offs and dependencies.
  • D. Five Backlogs and five Owners fragments the product into silos and prevents one coherent Increment and Goal.

PSM-II exam tip

One product equals one Backlog plus one Owner. Any scaled answer multiplying either element is automatically wrong.

10Several Sprints into a project, a client is complaining to the Product Owner about the poor performance of the product. As a Scrum Master, how can you help the Product Owner?
  • Coach the Product Owner on effective ways to communicate this concern to the Development Team and encourage the Product Owner to add the performance issue to the Product Backlog.
  • Tell the Product Owner performance is defined by the Development Team.
  • Note the issue for the next Sprint Retrospective.
  • Notify the team responsible for system performance.
Answer: A

The short version

A — Coach the Product Owner to surface performance via the Backlog. The Scrum Master connects customer concern to transparent ordering and direct Developer dialogue, not side channels.

Key concepts in this question

  • Backlog transparency: Concerns become ordered Product Backlog items so value, risk and urgency are visible and negotiable.
  • Product Owner mediation: Channels stakeholder feedback into the team through refinement and planning rather than hallway pressure.
  • Coaching communication: Helps Product Owner frame non-functional concerns as outcomes and acceptance expectations Developers can act on.
  • Empirical response: Uses inspection of the Increment and data on performance instead of blame or private escalation routes.

Why A is correct

Performance complaints are product feedback that must enter the empirical loop. Coaching the Product Owner to communicate the concern directly to Developers and to add it to the Product Backlog makes the work transparent, orderable and refinable. The team can then slice improvements, agree on Done criteria and forecast them against the Sprint Goal. Telling the Owner performance is team-defined, parking it for Retrospective or notifying an outside group bypasses ordering and weakens direct collaboration and transparency.

Why the others are wrong

  • B. Declaring performance team-defined dismisses legitimate customer feedback and avoids Product Owner responsibility to represent it.
  • C. Parking the issue for Retrospective confuses product functionality with process improvement and delays value response.
  • D. Notifying an outside performance group fragments accountability and breaks the single team model for delivering Done work.

PSM-II exam tip

Customer pain becomes Backlog plus conversation. Choose coach Owner to order and communicate, never reroute or postpone.

Want the full bank of 192 questions for Professional Scrum Master II (PSM II)? See all practice exams.