PSM I

Free PSM I practice questions

10 questions from our PSM I practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the PSM I practice exams

Question 1 of 10, Scrum Theory, Empiricism and Scrum Values

A project manager argues that detailed up-front planning works for building identical warehouses, so it must work for a new mobile banking app as well. How should the Scrum Master explain the difference?

  1. AThe app is simple work, so no planning is needed and the Developers can start coding without any Sprint Planning
  2. BThe warehouse needs Scrum more, since physical construction is riskier than software work and changes are costlier
  3. CThe app is complex work with many unknowns, where inspecting real results beats prediction Correct answer
  4. DThe app can be planned up front too, but Scrum demands a new plan every month

Answer and explanation: Scrum is designed for complex problems where more is unknown than known, so an empirical approach of inspecting actual results and adapting works better than a detailed predictive plan. A new banking app is not simple, Scrum's rhythm exists because of uncertainty rather than as an arbitrary rule, and the comparison about warehouses misses the point that predictable, repeatable work suits defined processes.

Question 2 of 10, Scrum Theory, Empiricism and Scrum Values

A Scrum Master sees that the Product Backlog shows only high-level themes while the real requirements live in private spreadsheets held by individual stakeholders. What is the Scrum Master's MOST important concern?

  1. ALow artifact transparency can lead to decisions that diminish value and increase risk Correct answer
  2. BThe themes are too large for the Daily Scrum, which must inspect every backlog item
  3. CThe spreadsheets break the rule that only the Scrum Master may edit the items on the Product Backlog
  4. DStakeholders are not allowed to keep requirements anywhere other than a Scrum tool

Answer and explanation: Scrum's artifacts are designed to maximize transparency; decisions to optimize value and control risk are based on their perceived state, so low transparency can lead to decisions that diminish value and increase risk. The Scrum Master does not own backlog edits, the Daily Scrum inspects progress toward the Sprint Goal rather than the whole Product Backlog, and no specific tool is mandated.

Question 3 of 10, Scrum Team and Accountabilities

A Product Owner frequently tells stakeholders that the Scrum Master is 'responsible for managing their expectations' about delivery. The Scrum Master wants to clarify accountabilities. Which statement is MOST accurate?

  1. AThe Product Owner engages stakeholders about the product and value; the Scrum Master facilitates collaboration when needed Correct answer
  2. BThe Developers are accountable for stakeholder expectations, because they produce the Increment that stakeholders will receive
  3. CThe Scrum Master is accountable for stakeholder expectations, because the Scrum Master owns all communication outside the team
  4. DStakeholder expectations are not part of Scrum, so nobody in the Scrum Team needs to engage with stakeholders before release

Answer and explanation: The Product Owner is accountable for maximizing value and effective Product Backlog management, which includes working with stakeholders, while the Scrum Master serves the Product Owner by facilitating stakeholder collaboration as requested or needed. Making the Scrum Master or Developers solely accountable is inaccurate, and stakeholders are central to Scrum, especially at the Sprint Review.

Question 4 of 10, Scrum Team and Accountabilities

The Developers produce lots of small features nobody uses, while high-value items wait. How does the Scrum Guide describe the Scrum Master's service to the team here?

  1. AHelping the Scrum Team focus on creating high-value Increments that meet the Definition of Done Correct answer
  2. BChoosing which Product Backlog items the Developers should work on next, based on value
  3. CReporting the low-value features to stakeholders so they can stop the work at the Review
  4. DAsking the Developers to slow down so the Product Owner has time to review each feature

Answer and explanation: The Scrum Guide says the Scrum Master serves the team by helping it focus on creating high-value Increments that meet the Definition of Done, for example by making the problem transparent and coaching on the Sprint Goal and ordering. Choosing items is not the Scrum Master's role, reporting to stakeholders bypasses the Product Owner, and slowing down does not address value.

Question 5 of 10, Scrum Events

A fully remote team suggests replacing its Daily Scrum with each Developer posting a written update in chat whenever they like. What is the MOST important concern for the Scrum Master to raise?

  1. AAsync updates may not provide a shared inspection of progress and an adapted plan toward the Sprint Goal Correct answer
  2. BWritten updates are forbidden by the Scrum Guide, which requires every Daily Scrum to happen in person
  3. CWritten updates take more than fifteen minutes in total, which always exceeds the Daily Scrum timebox
  4. DWritten updates prevent the Scrum Master from recording attendance, which management needs each day

Answer and explanation: The Daily Scrum's purpose is for the Developers to inspect progress together and adapt the Sprint Backlog, producing an actionable plan; scattered individual posts often lose this collaborative inspection. The guide does not require in-person meetings, total time spent writing is not the timebox concern, and attendance tracking for management is not a purpose of Scrum.

Question 6 of 10, Scrum Events

A department adds a weekly 'alignment meeting' for each Scrum Team on top of the Scrum events, and Developers complain about meeting overload. What should the Scrum Master explore FIRST?

  1. AWhether the Scrum events are used well enough to meet that need, as they are designed to minimize extra meetings Correct answer
  2. BWhether the alignment meeting can replace the Sprint Review, since it happens more often during each Sprint
  3. CWhether the Daily Scrum can be dropped on alignment days, so the total time spent in meetings stays the same
  4. DWhether the Developers can skip the alignment meeting, while the Scrum Master attends and reports back to them

Answer and explanation: The Scrum Guide says events are used to create regularity and to minimize the need for meetings not defined in Scrum; if extra meetings appear, the Scrum Master should first check whether the events are fulfilling their purpose. Replacing or dropping Scrum events is not allowed, and having the Scrum Master act as a relay adds a reporting layer without fixing the cause.

Question 7 of 10, Scrum Artifacts, Commitments and Done

A stakeholder argues that a Definition of Done that includes automated tests and security scanning is 'too strict' and slows delivery. How should the Scrum Master respond?

  1. AExplain that a strong Definition of Done keeps Increments usable and transparent, and invite discussion of the trade-offs Correct answer
  2. BAgree to move the security scanning to a hardening Sprint at the end of each quarter so that delivery speeds up
  3. CTell the stakeholder that the Definition of Done is confidential to the Developers and not open to discussion
  4. DAgree to drop the tests from the Definition of Done for urgent items and record the risk in the Sprint Backlog

Answer and explanation: The Definition of Done defines the quality required for work to be part of a usable Increment; weakening it creates hidden debt and lowers transparency, though the Scrum Master can facilitate a discussion about the trade-offs. Dropping checks for urgent items or deferring them to hardening Sprints means Increments are not really Done, and the Definition of Done is meant to create shared understanding, not be confidential.

Question 8 of 10, Developing People and Teams (Self-Management, Facilitation, Coaching)

A Developer asks the Scrum Master to just tell her the 'right way' to split a large item. The Scrum Master wants to build her capability. Which question is the BEST coaching response?

  1. A'Have you thought about simply splitting it by technical layer, as most teams do it?'
  2. B'Why didn't you split this before Sprint Planning, as we agreed in our last meeting?'
  3. C'What options for splitting it have you already considered, and what would each give users?' Correct answer
  4. D'Can you ask the Product Owner to split it for you, since that is the Product Owner's job?'

Answer and explanation: An open, forward-looking question helps the Developer explore options and think about value, building her own capability. A leading question pushes one approach, a 'why didn't you' question sounds like blame, and handing the task to the Product Owner is not coaching and misrepresents accountabilities, as Developers are responsible for sizing and often splitting work.

Question 9 of 10, Developing People and Teams (Self-Management, Facilitation, Coaching)

A Scrum Master wants every person in a large group to contribute ideas during a Sprint Retrospective, not only the loudest voices. Which facilitation approach is MOST suitable?

  1. AHave people reflect alone first, then share in pairs and fours before the whole group Correct answer
  2. BLet the most experienced Developer summarize the problems for the whole group
  3. CRun an open discussion and let the Scrum Master decide which ideas are best
  4. DSend a survey after the Retrospective and let the Product Owner pick actions

Answer and explanation: Structures such as 1-2-4-All start with silent individual reflection and gradually widen the conversation, so quieter people contribute and ideas build up. Letting one person summarize or the Scrum Master choose concentrates influence, and an after-the-fact survey with the Product Owner choosing actions removes the team's ownership of its improvements.

Question 10 of 10, Managing Products with Agility

The Developers tell the Scrum Master that shortcuts taken in earlier Sprints now slow down every new feature. The Product Owner is unaware of this. What should the Scrum Master do FIRST?

  1. ATell the Developers to fix the debt secretly during each Sprint without involving the Product Owner at all
  2. BHelp the Developers make the technical debt transparent to the Product Owner, for example as Product Backlog items Correct answer
  3. CAdd a separate debt-reduction Sprint after every three Sprints in which no Product Backlog items are worked on
  4. DAsk the Product Owner to stop accepting new features until every piece of debt is fully removed by the team

Answer and explanation: Technical debt reduces transparency and the product's ability to change, so making it visible lets the Product Owner weigh it against new value when ordering the Product Backlog. Hiding the work removes transparency, freezing all features is an extreme decision for the Product Owner to make with full information, and special debt Sprints are not part of Scrum.