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

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

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

1When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
  • Yes, but only for Scrum Teams whose work has dependencies.
  • Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
  • No, each Scrum Team stands alone.
  • No, that is far too hard and must be done in a hardening Sprint.
Answer: B

The short version

B — Yes, integrate every Sprint so Done can be inspected. Scrum requires a single integrated Increment each Sprint when many teams share one product, otherwise inspection of what is truly Done becomes unreliable and ordering decisions rest on guesswork.

Key concepts in this question

  • Integrated Increment: the sum of all completed Product Backlog items from all teams, merged and verified to work together as one releasable whole each Sprint.
  • Inspection and transparency: Scrum pillars that require stakeholders and Product Owner to see real working product behavior.
  • Scaled Scrum with one product: multiple teams share one Product Backlog, one Product Owner and one Definition of Done.
  • Dependency risk: partial integration only where dependencies are obvious still allows hidden integration debt to accumulate.

Why B is correct

Scrum defines Done as integrated, tested and potentially releasable, and with many teams that definition can only be met if all work is integrated every Sprint. Only a fully integrated Increment lets the Product Owner and stakeholders accurately inspect progress at Sprint Review and make sound ordering and release choices.

Why the others are wrong

  • A. Conditioning integration on known dependencies ignores unknown interfaces and lets hidden incompatibility grow until it is expensive to resolve.
  • C. Teams are not standalone when they build one product, because value is judged at product level and fragmentation destroys transparency.
  • D. Difficulty never justifies a hardening Sprint in Scrum, since hardening Sprints add non-value delay and violate the rule that each Sprint must yield a Done Increment.

PSM-I exam tip

Think one product equals one integrated Increment per Sprint, no exceptions for scale, and eliminate any answer that proposes partial integration or a hardening Sprint.

2Who can cancel a Sprint?
  • The Scrum Team.
  • The Scrum Master.
  • The Product Owner.
  • The Stakeholders.
Answer: C

The short version

C — Product Owner alone may cancel a Sprint. Cancellation happens only when the Sprint Goal becomes obsolete, and only the Product Owner has authority to declare that, usually because of a major change in business direction or market conditions.

Key concepts in this question

  • Sprint cancellation authority: Scrum Guide reserves cancellation exclusively for the Product Owner, reflecting ownership of value and Product Goal alignment.
  • Sprint Goal obsolescence: the sole legitimate trigger, meaning continued work would waste effort because the objective no longer matters to the business.
  • Product Owner accountability: maximizing product value includes stopping work that no longer delivers value, even mid-Sprint.
  • Stability of Sprint: cancellation is intentionally rare and is treated as disruptive, so no other role is empowered to interrupt the timebox.

Why C is correct

The Scrum Guide states that only the Product Owner has the authority to cancel a Sprint, and does so when the Sprint Goal becomes obsolete due to shifting company direction, technology change, or market feedback. This rule protects focus: Developers, Scrum Masters, and stakeholders may raise concerns, but the value decision belongs to one accountable owner. Cancellation consumes sunk cost and forces replanning, so centralizing the call prevents casual interruption.

Why the others are wrong

  • A. Scrum Team as a whole has no joint cancellation power; authority is singular, not collective.
  • B. Scrum Master protects process and removes impediments but holds no authority over scope value or release decisions.
  • D. Stakeholders influence through feedback and Product Backlog input, yet cannot direct the team or end a Sprint.

PSM-I exam tip

Remember cancel equals value obsolete equals Product Owner only; if an option spreads this power to the team or Scrum Master, eliminate it immediately.

3The Sprint Goal is a result of Sprint Planning, as is the Sprint Backlog.
  • True
  • False
Answer: A

The short version

A — True, Sprint Planning produces both the Sprint Goal and the Sprint Backlog. Sprint Planning commits the Scrum Team to a single objective and to the plan for reaching it, so both artifacts emerge together from that one event.

Key concepts in this question

  • Sprint Planning: the timeboxed event that starts the Sprint, answering why the Sprint is valuable, what can be Done, and how the work will get done.
  • Sprint Goal: the single objective that gives coherence and focus to the Sprint, created collaboratively and fixed for the Sprint unless it becomes obsolete.
  • Sprint Backlog: the Developers plan composed of the Sprint Goal, selected Product Backlog items, and the actionable plan to deliver them as one Increment.
  • Commitment and flexibility: scope may be clarified or renegotiated during the Sprint, but the Goal provides the stable purpose against which trade-offs are judged.

Why A is correct

The Scrum Guide explicitly lists the Sprint Goal and the Sprint Backlog as the two complementary outcomes of Sprint Planning. The Product Owner proposes value and ordering, Developers select what they believe is feasible, and together they craft the Goal that binds the selection into a coherent forecast. No other event creates these artifacts, so stating that both result from Sprint Planning is accurate and complete.

Why the others are wrong

  • B. Denying the statement contradicts the Scrum Guide flow, because Sprint Planning is defined as the origin of both the Goal and the Backlog and no alternative source exists.

PSM-I exam tip

Link Planning to two outputs every time: Goal plus Backlog, and remember Review yields inspection, Retrospective yields improvement, never confuse their outputs.

4Which two of the following are appropriate topics for discussion during a Sprint Retrospective? (Choose two.)
  • Identifying high priority process improvements for the next Sprint.
  • The order of items in the Product Backlog.
  • How the team collaborates.
  • Documenting acceptance criteria for items in the next Sprint.
Answer: A, C

The short version

AC — Process and people, not backlog order. The Retrospective looks inward at how the team works together and which process fix matters most next, leaving product ordering and refinement to other events.

Key concepts in this question

  • Retrospective purpose: plan ways to increase quality and effectiveness by inspecting people, interactions, processes, tools and Done.
  • Process improvements: identify the most helpful change and address the most impactful ones as soon as possible.
  • Collaboration inspection: how the team collaborates is explicitly in scope, including communication, trust and flow.
  • Product vs process split: Product Backlog order and acceptance details belong to refinement, planning and review, not to the improvement forum.

Why AC is correct

Scrum Guide frames the Retrospective as the team inspecting its own effectiveness and naming improvements to apply in the next Sprint, even adding them to the next Sprint Backlog. A is correct because selecting high priority process improvements is the core output of that inspection. C is correct because collaboration quality directly shapes effectiveness, so discussing how members interact, swarm, or resolve friction is central. Together they keep the event focused on the system of work rather than the content of the product.

Why the others are wrong

  • B. Ordering the Product Backlog is Product Owner accountability with Developer input and happens through ongoing refinement and planning, not through a process retro.
  • D. Documenting acceptance criteria for upcoming items is refinement work to make items ready, which improves transparency of requirements but does not improve the team system itself.

PSM-I exam tip

If the stem asks what to discuss in a Retrospective, pick the people and process answers and push any backlog ordering or writing choices out to refinement or planning.

5When should a Sprint Goal be created?
  • It should have been created in the previous Sprint during Product Backlog refinement.
  • It must be established before Sprint Planning in order to begin planning.
  • A Sprint Goal is not mandatory in Scrum.
  • At any time during the Sprint.
  • During Sprint Planning.
Answer: E

The short version

E — Sprint Goal is crafted during Sprint Planning. The whole Scrum Team collaborates in that event to define a single coherent objective that guides selection of Product Backlog items and the plan for delivering them.

Key concepts in this question

  • Sprint Planning purpose: first event in the Sprint where What can be done, How it will be done, and Why it matters converge into a plan.
  • Sprint Goal character: a concise commitment expressing the value and focus of the Sprint, owned collectively once agreed.
  • Collaborative creation: Product Owner proposes direction from Product Goal, Developers assess capacity and technique, Scrum Master facilitates focus.
  • Flexibility before commitment: refinement may suggest candidates, but the formal Goal is fixed only in Planning when capacity and scope are known.

Why E is correct

Scrum Guide places Sprint Goal creation inside Sprint Planning because only there do current velocity, capacity, Product Backlog readiness, and business priority meet. The team inspects the Product Goal, selects items, and articulates why this Sprint matters. Creating it earlier would prejudge capacity, while creating it later would leave the Sprint aimless. Hence Planning is the decisive moment.

Why the others are wrong

  • A. Refinement clarifies items and estimates but does not commit the team to a Sprint objective.
  • B. Requiring the Goal before Planning reverses flow; Planning input includes vision, but the Goal itself emerges through negotiation in the event.
  • C. Sprint Goal is mandatory as one of three Sprint commitments alongside Product Goal and Definition of Done.
  • D. Creating a Goal at any time during the Sprint defeats purpose; it must guide the Sprint from its start.

PSM-I exam tip

Link Goal to Planning in memory: Planning answers Why plus What plus How, and Why equals the freshly written Sprint Goal.

6During a Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master? (Choose two.)
  • Consider the request and decide on which days the Daily Scrum should occur.
  • Coach the team on why the Daily Scrum is important as an opportunity to update the plan.
  • Have the developers vote
  • Learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum.
  • Acknowledge and support the self-organizing team's decision.
Answer: B, D

The short version

BD — Coach on Daily Scrum purpose and dig into the underlying problem. Reducing the Daily Scrum to twice weekly breaks its inspect-and-adapt rhythm, so the Scrum Master serves the team by teaching and by uncovering why the event feels unhelpful.

Key concepts in this question

  • Daily Scrum purpose: a fifteen minute event for Developers to inspect progress toward the Sprint Goal and adapt the next twenty four hour plan.
  • Scrum Master service: coaching in self-management and Scrum theory plus causing removal of impediments.
  • Self-management with boundaries: Developers decide how to do the work, but within the framework rules, so frequency of required events is not optional or voteable.
  • Retrospective improvement: surface pain points openly, find root causes such as status reporting or overlong discussions.

Why BD is correct

Daily frequency is what makes the plan current and impediments visible quickly, which is why coaching on that purpose restores understanding of the cost of skipping days. Investigating why the team wants fewer meetings uncovers the real impediment, such as poor facilitation or treating it as status to outsiders, and lets the Scrum Master work with them to improve outcomes.

Why the others are wrong

  • A. Deciding the schedule for the team replaces coaching with command and undermines self-management by taking ownership away from Developers.
  • C. Voting treats framework rules as preference and risks legitimizing a Scrum violation without addressing why the event is painful.
  • E. Blindly supporting a decision that breaks daily inspection confuses self-organization with freedom to ignore Scrum, which harms transparency.

PSM-I exam tip

When Developers propose fewer Daily Scrums, pick coach plus investigate, never vote, decide for them, or endorse breaking the daily cadence.

7As the Development Team starts work during the Sprint, it realizes it has selected too much work to finish in the Sprint. What should it do?
  • Inform the Product Owner at the Sprint Review, but prior to the demonstration.
  • Find another Scrum Team to give the excess work to.
  • As soon as possible in the Sprint, work with the Product Owner to remove some work or Product Backlog items.
  • Reduce the definition of ג€Doneג€ and get all of the Product Backlog items ג€Doneג€ by the new definition.
Answer: C

The short version

C — Renegotiate scope with the Product Owner as soon as overcommitment is clear. Sprint scope is forecast, not a fixed contract, so early collaboration to remove or re-split items protects the Sprint Goal without lowering quality.

Key concepts in this question

  • Forecast versus commitment: Developers pull what they believe is feasible, but discovery during the Sprint can prove the forecast optimistic and requires transparent replanning.
  • Scope renegotiation: Sprint Goal stays fixed where possible while the Sprint Backlog scope may be adjusted in collaboration with the Product Owner as more is learned.
  • Definition of Done integrity: quality standards are never diluted to claim completion, because faking Done destroys trust and creates hidden rework.
  • Early transparency: raising the issue immediately maximizes options for ordering, stakeholder expectation management, and orderly replanning.

Why C is correct

Scrum expects Developers and Product Owner to collaborate when the plan proves infeasible, trimming lower value items so the team can still deliver a coherent Increment toward the Goal. Acting early preserves focus, avoids a last-minute surprise at Review, and keeps quality intact by refusing to cut corners on Done.

Why the others are wrong

  • A. Waiting until Review to disclose the shortfall hides information, wastes Sprint time, and denies stakeholders timely adaptation.
  • B. Offloading excess to another team ignores that teams pull their own work, disrupts the other team plan, and avoids the needed Product Owner conversation.
  • D. Weakening Done to appear complete fakes progress and violates Scrum transparency, trading short term optics for long term debt.

PSM-I exam tip

Over-selected means talk to the Product Owner immediately and trim scope, never wait, dump work elsewhere, or water down Done.

8In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?
  • Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.
  • It doesn't really matter because you can rotate the teams every Sprint to spread knowledge.
  • Check with the allocation department to see who has worked together before and make these the first teams.
  • Create a matrix of skills, seniority, and level of experience to assign people to teams.
Answer: A

The short version

A — Informed people self-organize into teams around product and Scrum rules. Small cross-functional groups form best when those doing the work use product vision and framework constraints to design collaboration, not imposed assignment.

Key concepts in this question

  • Self-organization: those closest to the work decide how to structure collaboration, which builds ownership, commitment and faster problem solving.
  • Product understanding: knowledge of vision, value streams and likely architecture lets people cluster skills where end-to-end delivery is most feasible.
  • Scrum team size and cross-functionality: small teams of around ten or fewer with all skills to deliver Done work reduc.
  • Management as enablers: leaders provide purpose, boundaries and coaching, but imposed allocation by history or matrix weakens motivation and fit.

Why A is correct

Scrum theory holds that complex work is best organized by the people doing it, provided they grasp product goals and Scrum constraints on size and cross-functionality. A group of one hundred dividing itself can balance domain knowledge, technical skills and team cohesion far better than top-down sorting by past pairings or seniority matrices.

Why the others are wrong

  • B. Rotating membership every Sprint destroys stability and shared learning, preventing the trust and throughput that stable teams build over time.
  • C. Reusing prior pairings from allocation records optimizes for familiarity rather than product needs and preserves silos instead of cross-functionality.
  • D. Manager-built skill matrices impose structure without ownership and treat people as resources, undermining self-organization and commitment.

PSM-I exam tip

For large groups, choose self-division guided by product vision and Scrum rules, reject imposed matrices, history-based grouping, or constant rotation.

9A new Developer is having continuing conflicts with existing members of the Scrum Team, which is impacting the delivery of the Increment. If necessary, who is responsible for removing the Developer from the Scrum Team?
  • The hiring manager is responsible, because they hired the Developer.
  • The Product Owner is responsible, because they control the return on investment (ROI).
  • The Scrum Master is responsible, because they remove Impediments.
  • The Scrum Team is responsible.
Answer: D

The short version

D — The Scrum Team as a whole owns membership decisions. Self-management means the team, often with Scrum Master facilitation and management support, resolves persistent interpersonal impediments including removal.

Key concepts in this question

  • Self-managing Scrum Team: Developers, Product Owner and Scrum Master collectively own effectiveness, norms and collaboration health.
  • Scrum Master facilitation: coaches on conflict, transparency and productive norms, and helps remove impediments, but does not hire, fire or unilaterally reassign people.
  • Management and HR boundaries: hiring managers handle employment mechanics.
  • Escalation path: internal coaching first, then team decision with organizational help to implement, preserving respect while protecting delivery of the Increment.

Why D is correct

Persistent conflict that blocks the Increment is a team effectiveness issue, and Scrum assigns ownership of such effectiveness to the Scrum Team itself. The team can seek Scrum Master coaching and organizational assistance to mediate or transition the person, but accountability for requesting the change rests with the team rather than an external owner of ROI or a remover of technical impediments.

Why the others are wrong

  • A. Hiring authority does not equal ongoing accountability for team dynamics, since hiring managers lack daily insight into Sprint impact.
  • B. Product Owner accountability for value does not extend to team composition, and using ROI control to remove people confuses value ordering with team health.
  • C. Removing impediments is facilitation and coaching, not unilateral power to eject members, so assigning removal to Scrum Master overstates that accountability.

PSM-I exam tip

People conflict that threatens delivery resolves at team level with coaching help, never by Product Owner ROI power or Scrum Master firing authority.

10Which three purposes does the definition of Done serve? (Choose three.)
  • Guide the Development Team on how many Product Backlog items to select for the Sprint.
  • Create a shared understanding of when work is complete.
  • Describe the purpose, objective, and time-box of each Scrum event.
  • Describe the work that must be done before the Sprint is allowed to end.
  • Increase transparency.
Answer: A, B, E

The short version

ABE — Done guides selection, creates shared completion meaning, and boosts transparency. The Definition of Done is the quality contract that makes forecasting realistic and inspection honest.

Key concepts in this question

  • Definition of Done: a formal description of the quality and completeness standard that every Increment must meet to be considered releasable.
  • Forecasting aid: knowing the testing, integration and documentation burden in Done helps Developers judge how many items can realistically be finished.
  • Shared understanding: a common checklist prevents each person meaning something different by complete and aligns Developers, Product Owner and stakeholders.
  • Transparency multiplier: explicit Done makes progress binary and visible, so undone work cannot masquerade as Done at Review.

Why ABE is correct

Selection depends on effort implied by Done, because stricter verification and integration work directly affects capacity for the Sprint. Shared meaning follows because Done codifies when work counts as complete across roles and teams. Transparency rises because a public standard exposes gaps immediately and lets inspection focus on real value rather than debated completeness, which together explain the three chosen purposes.

Why the others are wrong

  • C. Event purposes and timeboxes are defined by the Scrum framework itself, not by the product quality contract of Done.
  • D. Done describes quality for any Increment whenever it is met, not a rule that listed work must all finish before the timebox ends.

PSM-I exam tip

Attach Done to selection guidance, shared complete meaning, and transparency, never to event descriptions or must-finish-all-work rules.

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