Scrum Master PSM I Prep Practice Exam

Question 1 Scrum Master PSM I Prep

What is the Sprint Retrospective?

The final Sprint event, dedicated to inspecting and improving the team's process, relationships, and tools. A team organized around delivering end-to-end customer value features rather than technical components. If any aspects deviate outside acceptable limits, the process must be adjusted to minimize further deviation. A 15-minute time-boxed daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan.

Question 2 Scrum Master PSM I Prep

What is the Sprint Review?

Maximizing the value of the product resulting from the work of the Scrum Team. A working meeting at the end of the Sprint to inspect the Increment and adapt the Product Backlog. A team organized around a technical layer (e.g., database, UI) — generally discouraged in Scrum. A version of the product made available for use by end users.

Question 3 Scrum Master PSM I Prep

What is the maximum duration of Sprint Planning for a one-month Sprint?

4 hours. A unit of measure expressing an estimate of the overall effort required to fully implement a Product Backlog item. Poor Definition of Done leads to accumulating technical debt; Scrum requires transparency about it. 8 hours.

Question 4 Scrum Master PSM I Prep

Who must attend the Daily Scrum?

The Developers — only they are required to attend; the Scrum Master and Product Owner participate only if they are also doing Developer work. Selecting items from the Product Backlog to include in the current Sprint. A fixed time-box of one month or less during which a done Increment is created. An ordered, emergent list of what is needed to improve the product; the single source of work undertaken by the Scrum Team.

Question 5 Scrum Master PSM I Prep

What is "Done" vs "Done-Done"?

Engaging stakeholders, gathering feedback, and ensuring the Product Owner represents their needs while balancing value. Some teams distinguish intermediate states (e.g., "code complete" vs fully released) — Scrum requires a single, clear Definition of Done. The definitive definition of Scrum, authored by Ken Schwaber and Jeff Sutherland; the rules of the framework. It remains fixed and cannot be changed or extended.

Question 6 Scrum Master PSM I Prep

When might the Product Owner cancel a Sprint?

A common story distinguishing those who are committed (pigs — actually doing the work) from those who are merely involved (chickens). When the Sprint Goal becomes obsolete, such as due to a change in direction or market conditions. Significant aspects of the process must be visible to those who perform and receive the work. A technique to coordinate multiple Scrum Teams working on the same product, with representatives from each team.

Question 7 Scrum Master PSM I Prep

In Scrum, who are the "pigs"?

Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done? A tangible output that provides transparency and opportunities for inspection and adaptation. Velocity measures the amount of work — not productivity in absolute terms and not value directly. Product Owner, Scrum Master, and Developers — they are committed and accountable.

Question 8 Scrum Master PSM I Prep

Who attends the Sprint Review?

One month or less. The cost of change is relatively flat because feedback is frequent and rework is early. The Product Backlog contains everything; the Sprint Backlog is the subset selected for the current Sprint. The Scrum Team and stakeholders — it is not a status meeting but a collaborative working session.

Question 9 Scrum Master PSM I Prep

How does the Scrum Master serve the organization?

As a <user type>, I want <goal>, so that <benefit>. The cost of change is relatively flat because feedback is frequent and rework is early. Decision-making based on observation, experimentation, and learning from experience rather than upfront defined processes. Leading, training, and coaching the organization in Scrum adoption; planning Scrum implementations; helping employees understand empiricism.

Question 10 Scrum Master PSM I Prep

What is the commitment associated with the Increment?

A chart tracking remaining work toward a release, often using story points or features. The Definition of Done. Establishing Scrum as defined in the Scrum Guide; removing impediments; coaching the team and organization. Code reviewed, tested, integrated, documented, and potentially released to production.

Question 11 Scrum Master PSM I Prep

What is the purpose of the Sprint Review?

Story point estimation — 1, 2, 3, 5, 8, 13, 21, etc., reflecting uncertainty for larger items. The set of Product Backlog items selected for the Sprint, plus the plan to deliver them and the Sprint Goal. To inspect the Increment, discuss progress toward the Product Goal, determine next backlog items, and gather feedback. Primarily the Scrum Master, although the whole team should help surface and remove them.

Question 12 Scrum Master PSM I Prep

Can the Scrum Master facilitate all Scrum events?

Usually no more than 10% of the capacity of the Developers, though it is not time-boxed in the Scrum Guide as a separate event. Story point estimation — 1, 2, 3, 5, 8, 13, 21, etc., reflecting uncertainty for larger items. Yes — the Scrum Master is responsible for ensuring events are held and facilitating them when appropriate. Estimating items by comparing them to each other rather than estimating in absolute time.

Question 13 Scrum Master PSM I Prep

What is the difference between a Sprint Goal and a release goal?

The Sprint Goal defines focus for a single Sprint; a release goal is longer-term across multiple Sprints. A chart tracking remaining work toward a release, often using story points or features. Poor Definition of Done leads to accumulating technical debt; Scrum requires transparency about it. A rugby scrum, used by Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 Harvard Business Review paper.

Question 14 Scrum Master PSM I Prep

Who is responsible for the Definition of Done?

The definitive definition of Scrum, authored by Ken Schwaber and Jeff Sutherland; the rules of the framework. The set of Product Backlog items selected for the Sprint, plus the plan to deliver them and the Sprint Goal. The Scrum Team as a whole — it is a shared commitment, not owned by one role. A team organized around delivering end-to-end customer value features rather than technical components.

Question 15 Scrum Master PSM I Prep

What is the purpose of the Retrospective?

A rugby scrum, used by Hirotaka Takeuchi and Ikujiro Nonaka in their 1986 Harvard Business Review paper. The single objective for the Sprint that gives the team a specific focus and encourages unity. Code reviewed, tested, integrated, documented, and potentially released to production. To plan improvements to increase quality and effectiveness; the team adapts its definition of "done" if useful.

Question 16 Scrum Master PSM I Prep

What is a potentially shippable product increment?

Inspect the previous Sprint regarding people, relationships, process, tools, and Definition of Done; identify improvements. The Scrum Team as a whole — it is a shared commitment, not owned by one role. An Increment that meets the Definition of Done and is theoretically ready for release at any time. Story point estimation — 1, 2, 3, 5, 8, 13, 21, etc., reflecting uncertainty for larger items.

Question 17 Scrum Master PSM I Prep

What is a chicken-and-pig metaphor?

A specific type of stakeholder who actually uses the product. Primarily the Scrum Master, although the whole team should help surface and remove them. The single objective for the Sprint that gives the team a specific focus and encourages unity. A common story distinguishing those who are committed (pigs — actually doing the work) from those who are merely involved (chickens).

Question 18 Scrum Master PSM I Prep

What is cumulative flow diagram (CFD)?

Transparency, Inspection, and Adaptation. The Developers — they own it and update it throughout the Sprint. Helping find techniques for effective Product Backlog management, facilitating collaboration with stakeholders, and establishing empirical planning. A chart showing cumulative work across statuses over time, used to identify bottlenecks.

Question 19 Scrum Master PSM I Prep

What are the topics of Sprint Planning?

Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done? The definitive definition of Scrum, authored by Ken Schwaber and Jeff Sutherland; the rules of the framework. A chart tracking remaining work toward a release, often using story points or features. A version of the product made available for use by end users.

Question 20 Scrum Master PSM I Prep

What is user story format?

The Scrum Team — Product Owner, Scrum Master, and all Developers. An ordered, emergent list of what is needed to improve the product; the single source of work undertaken by the Scrum Team. As a <user type>, I want <goal>, so that <benefit>. By ordering the Product Backlog based on value, transparency, and trade-offs to maximize overall value.

Question 21 Scrum Master PSM I Prep

What is empirical process control?

The Product Goal. Decision-making based on observation, experimentation, and learning from experience rather than upfront defined processes. The final Sprint event, dedicated to inspecting and improving the team's process, relationships, and tools. The implied cost of additional rework caused by choosing an easy (limited) solution today instead of using a better but slower approach.

Question 22 Scrum Master PSM I Prep

What is Inspection in Scrum?

8 hours. The Definition of Done. Scrum artifacts and progress toward the agreed Sprint Goal are inspected frequently and diligently. The cost of change is relatively flat because feedback is frequent and rework is early.

Question 23 Scrum Master PSM I Prep

What is a component team?

Estimating items by comparing them to each other rather than estimating in absolute time. To deliver value iteratively and incrementally by solving complex problems while enabling teams to deliver productively and creatively. Primarily the Scrum Master, although the whole team should help surface and remove them. A team organized around a technical layer (e.g., database, UI) — generally discouraged in Scrum.

Question 24 Scrum Master PSM I Prep

What is Adaptation in Scrum?

If any aspects deviate outside acceptable limits, the process must be adjusted to minimize further deviation. 8 hours. A fixed time-box of one month or less during which a done Increment is created. Product Owner, Scrum Master, and Developers.

Question 25 Scrum Master PSM I Prep

What is the cost of change curve in Scrum?

Estimating items by comparing them to each other rather than estimating in absolute time. Engaging stakeholders, gathering feedback, and ensuring the Product Owner represents their needs while balancing value. The cost of change is relatively flat because feedback is frequent and rework is early. If any aspects deviate outside acceptable limits, the process must be adjusted to minimize further deviation.

Question 26 Scrum Master PSM I Prep

Who is responsible for removing impediments?

No — the Scrum Master is not a project manager; Scrum has no project manager role. Primarily the Scrum Master, although the whole team should help surface and remove them. The implied cost of additional rework caused by choosing an easy (limited) solution today instead of using a better but slower approach. A risk is a potential future problem; an issue is a current problem.

Question 27 Scrum Master PSM I Prep

What is a Daily Scrum?

Command-and-control conflicts with Scrum's empirical and self-managing approach. A version of the product made available for use by end users. The Sprint Goal defines focus for a single Sprint; a release goal is longer-term across multiple Sprints. A 15-minute time-boxed daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan.

Question 28 Scrum Master PSM I Prep

What is the "Why" topic in Sprint Planning?

Defining the Sprint Goal — the single objective that creates coherence and focus. A specific type of stakeholder who actually uses the product. Yes — Sprint Planning is time-boxed (up to 8 hours for a one-month Sprint), not necessarily a single day. The set of Product Backlog items selected for the Sprint, plus the plan to deliver them and the Sprint Goal.

Question 29 Scrum Master PSM I Prep

What is Transparency in Scrum?

The final Sprint event, dedicated to inspecting and improving the team's process, relationships, and tools. The cost of change is relatively flat because feedback is frequent and rework is early. Significant aspects of the process must be visible to those who perform and receive the work. If any aspects deviate outside acceptable limits, the process must be adjusted to minimize further deviation.

Question 30 Scrum Master PSM I Prep

What is a Product Backlog item?

Ken Schwaber and Jeff Sutherland, first presented at OOPSLA in 1995. Any artifact used to describe work to be done; the unit of value, risk, or need. A fixed time-box of one month or less during which a done Increment is created. A 15-minute time-boxed daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan.

Question 31 Scrum Master PSM I Prep

Can a Sprint be cancelled?

Primarily the Scrum Master, although the whole team should help surface and remove them. Yes, only the Product Owner has the authority to cancel a Sprint. A tangible output that provides transparency and opportunities for inspection and adaptation. An updated plan for the next day of work — not a status report to management.

Question 32 Scrum Master PSM I Prep

When does a new Sprint begin?

No — within a Scrum Team, the Product Owner and Scrum Master are separate accountabilities and cannot be combined. Some teams distinguish intermediate states (e.g., "code complete" vs fully released) — Scrum requires a single, clear Definition of Done. Product Backlog, Sprint Backlog, and Increment. Immediately after the previous Sprint's Retrospective concludes.

Question 33 Scrum Master PSM I Prep

What is the Sprint Goal?

A 15-minute time-boxed daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan. The single objective for the Sprint that gives the team a specific focus and encourages unity. A team that has all the skills needed to turn the backlog into a valuable Increment without depending on others outside the team. Risk, value, and dependencies (and dependencies-priority techniques like WSJF).

Question 34 Scrum Master PSM I Prep

What is a release?

The Sprint Goal defines focus for a single Sprint; a release goal is longer-term across multiple Sprints. A version of the product made available for use by end users. Yes — Sprint Planning is time-boxed (up to 8 hours for a one-month Sprint), not necessarily a single day. The Developers, to synchronize activities and identify impediments — not for the Scrum Master or managers.

Question 35 Scrum Master PSM I Prep

What is an Impediment?

Anything that prevents the team from making progress toward the Sprint Goal. The Developers, to synchronize activities and identify impediments — not for the Scrum Master or managers. Anyone with an interest in the product or project — internal or external to the organization. Often yes, but the role also includes facilitating, serving, and leading within the organization.

Question 36 Scrum Master PSM I Prep

What is a feature team?

To define the work to be performed in the Sprint and the Sprint Goal, producing the Sprint Backlog. A consensus-based estimation technique using cards with values (often Fibonacci) where team members discuss and re-vote. Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done? A team organized around delivering end-to-end customer value features rather than technical components.

Question 37 Scrum Master PSM I Prep

What are the three Scrum artifacts?

Product Backlog, Sprint Backlog, and Increment. The single objective for the Sprint that gives the team a specific focus and encourages unity. To support the Scrum Team with resources, environment, and alignment — not to direct work. A team organized around a technical layer (e.g., database, UI) — generally discouraged in Scrum.

Question 38 Scrum Master PSM I Prep

What is the "How" topic in Sprint Planning?

The cost of change is relatively flat because feedback is frequent and rework is early. Yes — the Scrum Master is responsible for ensuring events are held and facilitating them when appropriate. Decomposing the selected Product Backlog items into smaller work items (typically one day or less). Usually no more than 10% of the capacity of the Developers, though it is not time-boxed in the Scrum Guide as a separate event.

Question 39 Scrum Master PSM I Prep

What is the purpose of Sprint Planning?

A team that internally decides who does the work, how it is done, and how to turn the Product Backlog into Increments. An updated plan for the next day of work — not a status report to management. The ongoing activity of adding detail, estimates, and order to Product Backlog items. To define the work to be performed in the Sprint and the Sprint Goal, producing the Sprint Backlog.

Question 40 Scrum Master PSM I Prep

What is the Scrum Guide?

An ordered, emergent list of what is needed to improve the product; the single source of work undertaken by the Scrum Team. Story point estimation — 1, 2, 3, 5, 8, 13, 21, etc., reflecting uncertainty for larger items. The definitive definition of Scrum, authored by Ken Schwaber and Jeff Sutherland; the rules of the framework. A chart showing cumulative work across statuses over time, used to identify bottlenecks.

Question 41 Scrum Master PSM I Prep

What is the role of management in Scrum?

The set of Product Backlog items selected for the Sprint, plus the plan to deliver them and the Sprint Goal. The Product Owner — including its content, availability, and ordering. The Scrum Team as a whole — it is a shared commitment, not owned by one role. To support the Scrum Team with resources, environment, and alignment — not to direct work.

Question 42 Scrum Master PSM I Prep

What is the Product Backlog refinement?

The ongoing activity of adding detail, estimates, and order to Product Backlog items. Immediately after the previous Sprint's Retrospective concludes. Code reviewed, tested, integrated, documented, and potentially released to production. 3 hours.

Question 43 Scrum Master PSM I Prep

What is the relationship between Scrum and technical debt?

Poor Definition of Done leads to accumulating technical debt; Scrum requires transparency about it. An ordered, emergent list of what is needed to improve the product; the single source of work undertaken by the Scrum Team. Minimum Viable Product — a version of a new product that allows a team to collect the maximum amount of validated learning with the least effort. A specific type of stakeholder who actually uses the product.

Question 44 Scrum Master PSM I Prep

What is the commitment associated with the Sprint Backlog?

A team that has all the skills needed to turn the backlog into a valuable Increment without depending on others outside the team. When the Sprint Goal becomes obsolete, such as due to a change in direction or market conditions. A graphical representation of work remaining over time, often used during a Sprint for the Sprint Backlog. The Sprint Goal.

Question 45 Scrum Master PSM I Prep

What is the difference between a risk and an issue?

The Scrum Master's effectiveness; the team following Scrum; removing impediments; ensuring events are held. A risk is a potential future problem; an issue is a current problem. A chart showing cumulative work across statuses over time, used to identify bottlenecks. A specific type of stakeholder who actually uses the product.

Question 46 Scrum Master PSM I Prep

In Scrum, who are the "chickens"?

A consensus-based estimation technique using cards with values (often Fibonacci) where team members discuss and re-vote. They are reviewed and if appropriate, accepted into the baseline for future reference. An empirical measure of how much product backlog work a team turns into Increment of done product during a Sprint. Stakeholders, managers, and others who are interested but not accountable for delivery.

Question 47 Scrum Master PSM I Prep

What is burndown?

A graphical representation of work remaining over time, often used during a Sprint for the Sprint Backlog. Decomposing the selected Product Backlog items into smaller work items (typically one day or less). Usually no more than 10% of the capacity of the Developers, though it is not time-boxed in the Scrum Guide as a separate event. Someone who guides a meeting or process without authority over content — a key Scrum Master skill.

Question 48 Scrum Master PSM I Prep

What is Planning Poker?

An empirical measure of how much product backlog work a team turns into Increment of done product during a Sprint. A consensus-based estimation technique using cards with values (often Fibonacci) where team members discuss and re-vote. A technique to coordinate multiple Scrum Teams working on the same product, with representatives from each team. The Scrum Team and stakeholders — it is not a status meeting but a collaborative working session.

Question 49 Scrum Master PSM I Prep

What is a Stakeholder?

A chart tracking remaining work toward a release, often using story points or features. A leadership philosophy where the leader's primary goal is to serve others, focusing on the team's needs. Anyone with an interest in the product or project — internal or external to the organization. No — within a Scrum Team, the Product Owner and Scrum Master are separate accountabilities and cannot be combined.

Question 50 Scrum Master PSM I Prep

Is the Scrum Master an agile coach?

Often yes, but the role also includes facilitating, serving, and leading within the organization. Someone who guides a meeting or process without authority over content — a key Scrum Master skill. When the Sprint Goal becomes obsolete, such as due to a change in direction or market conditions. A team organized around delivering end-to-end customer value features rather than technical components.