PSM-I Scrum Professional Scrum Master I Free Practice Exam Questions (2025 Updated)

The best answer is B. The need for the team to learn based on doing work and measuring results.

The Sprint length should be chosen based on the complexity and volatility of the product and the environment, as well as the team’s capability and Definition of Done. The Sprint length should enable the team to deliver a usable Increment of value that meets the feedback needs of the stakeholders and the business. The Sprint length should also allow the team to inspect and adapt their work processes and practices based on the outcomes of the Sprint.

The other options are not valid reasons for choosing the Sprint length. The organization’s mandate, team formation, and release schedule should not dictate the Sprint length, but rather be aligned with it. The Scrum Team should have the autonomy to choose the Sprint length that best suits their product and context.

You can learn more about how to choose the right Sprint length from these sources: How Long A Sprint Should Be?, How to Choose the Right Sprint Length in Scrum, What is a Sprint?, Determining the Sprint Length, and Sprint Length: What’s the Right Length?.

The best answer is B. The Sprint length is unchanged and the Scrum Team continuously learns and adapts.

According to the Scrum Guide1, “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, the Sprint is not extended or shortened based on the completion of the work.

The Scrum Guide also states that “Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of ‘Done’ product ensure a potentially useful version of working product is always available.” Therefore, the Scrum Team should focus on delivering a potentially releasable Increment of value by the end of the Sprint, even if some work items are not completed.

The Scrum Team should also use the Sprint Retrospective to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Scrum Team should identify and order the major items that went well and potential improvements, and create a plan for implementing improvements to the way they do their work. This way, the Scrum Team continuously learns and adapts to changing circumstances and challenges.

According to the Scrum Guide, the Developers do the work to make sure Product Backlog items conform to the Definition of Done, as they are responsible for creating a “Done” Increment that meets the Definition of Done. The other options are not valid, as they imply that the work is done by someone else outside the Development Team (such as Quality Assurance Team) or by another role on the Scrum Team (such as Product Owner or Scrum Master).

The correct answer is D, because one of the services that a Scrum Master can provide in regard to the Daily Scrum is to teach the Development Team to keep the Daily Scrum within the 15 minute time-box. The Scrum Guide states that “the Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.”

According to the Scrum Guide, the Development Team should do two things during the first Sprint: develop at least one piece of functionality and create an increment of potentially releasable software. These are the goals of every Sprint, regardless of its order. The other options are not things that the Development Team should do during the first Sprint, as they are either out of scope (such as making a plan for the rest of the project or defining major product features and release plan architecture) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).

According to the Scrum Guide1, the Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum optimizes the probability that the Developers will meet the Sprint Goal. Every day, the Developers should understand how they intend to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. Management external to the Scrum Team is not involved in the Daily Scrum, as they may interfere with the self-management and empowerment of the Developers.

References: Scrum Guide

 Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required12. The Scrum Team’s goal is to deliver a “Done” Increment that meets the Definition of Done and the Sprint Goal3.

References: 1: The Scrum Team | Scrum.org 2: The Professional Scrum™ Competencies | Scrum.org 3: The 2020 Scrum Guide | Scrum.org

The Sprint Backlog is the Development Team’s plan for the Sprint, as stated in the Scrum Guide1: “The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.”

According to the Scrum Guide1, during each Daily Scrum, each Developer answers three questions:

What did I do yesterday that helped meet our Sprint Goal?

What will I do today to help meet our Sprint Goal?

Do I see any impediment that prevents me or our Development Team from meeting our Sprint Goal?

The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward achieving their Sprint Goal and producing a usable Increment. The Developers can start with any one person and proceed in any order.

References: Scrum Guide

According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-boxed events in Scrum are:

Sprint Planning (eight hours or less for a one-month Sprint)

Daily Scrum (15 minutes or less for a one-month Sprint)

Sprint Review (four hours or less for a one-month Sprint)

Sprint Retrospective (three hours or less for a one-month Sprint)

The other options are not time-boxed events in Scrum.

References: Scrum Guide

The correct answer is A, because if two Scrum Teams are added to the development of a product that previously had only one Scrum Team, the immediate impact on the productivity of the original Scrum Team is likely to decrease. This is because adding more teams may introduce some challenges and trade-offs, such as increased communication and coordination overhead, reduced alignment and cohesion, and potential conflicts or dependencies.

References: [Suggested Reading for Professional Scrum Master™ I]

The correct answer is B, because the guideline that a Scrum Master should give is that estimates are made by the Development Team. The Scrum Guide states that “the number of items selected from the Product Backlog for the Sprint is solely up to the Development Team. Only the Development Team can assess what it can accomplish over the upcoming Sprint.” Therefore, the Development Team should estimate the work in Scrum, using any method or unit they prefer.

According to the Scrum Guide, Developers are self-managing, which means that they manage their own Sprint Backlog. They decide how to organize their work and collaborate effectively to deliver a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that Developers manage things that are either determined by the Scrum framework (such as Sprint length), by collaboration with other roles (such as when to release or stakeholders for the Sprint Review), or by the Product Owner (such as Product Backlog ordering).

The correct answers are C, E, and F, because these phrases best describe the purpose of a definition of “Done”. It creates transparency over the work inspected at the Sprint Review, as it defines what it means for an Increment to be potentially releasable. It guides the Development Team in creating a forecast at the Sprint Planning, as it helps them estimate how much work they can accomplish in a Sprint. It defines what it takes for an Increment to be ready for release, as it ensures that the product meets the quality expectations of the stakeholders.

The next Sprint begins immediately after the conclusion of the previous Sprint, as stated in the Scrum Guide: “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.”

The recommended size for a Scrum Team is 10 or fewer people, as stated in the Scrum Guide: “The recommended size of a Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”

According to the Scrum Guide, the Product Owner can cancel a Sprint, as he or she is responsible for maximizing the value of the product and the work of the Development Team. The other roles do not have this authority, although they may provide input and suggestions to the Product Owner.