Scrum PSM-I Professional Scrum Master I Exam Practice Test

The correct answer is B, because a Scrum Master is not the same thing as a traditional PM (Project Manager). The Scrum Guide states that “the Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.” Therefore, a Scrum Master is not a manager, but a servant-leader and a coach for the Scrum Team and the organization.

According to the Scrum Guide 1 , 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-box for the Sprint Review is four hours for a one-month Sprint.

According to the Scrum Guide, a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint at the Sprint Planning event. This is when the Developers select items from the Product Backlog that they can commit to complete within a Sprint. The Developers are then responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they either imply that Developers are not accountable for value (such as never or whenever), or that they become accountable at a different time (such as during the Daily Scrum).

The correct answer is B, because the Scrum Guide states that “at the end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.” Therefore, all the increments from different Scrum Teams working on the same product should be integrated every Sprint to enable inspection and adaptation by the Product Owner and stakeholders.

According to the Scrum Guide 1 , there are five values that guide decisions within Scrum teams:

Commitment

Focus

Openness

Respect

Courage

In order to achieve the benefits of Scrum, it is important to enact these values. Two actions that demonstrate the commitment of Scrum Team members are:

Help the other Scrum Team members, as they work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.

Do your best, as they strive to deliver a potentially releasable Increment that meets the definition of “Done” and provides value to the stakeholders.

The correct answer is A. When multiple Scrum Teams work on the same product, they should share a common Definition of Done. This creates transparency across the product and ensures that all Increments are held to the same quality standard. Without one shared Definition of Done, it becomes difficult to inspect the integrated product accurately and determine whether work is truly complete.

Option B is incorrect because Scrum does not recommend separate Definitions of Done later reconciled in a hardening Sprint. Hardening Sprints are not part of Scrum and usually indicate that quality has not been built into normal development. Option C is also incorrect because merely making different definitions visible does not solve the inconsistency problem. A product needs one integrated standard of completion. Option D is incorrect because Scrum Masters do not define the Definition of Done on behalf of the teams. It must be mutually understood and used by the Scrum Teams working on that product, taking organizational standards into account.

A shared Definition of Done supports integration, quality, and releasability. It helps all teams contribute to one coherent product Increment rather than producing partially compatible outputs with differing completion standards.

The correct answer is D. The Sprint Goal provides the Developers with a common, specific objective that creates focus and coherence during the Sprint. Rather than treating the Sprint as a collection of unrelated backlog items, the Sprint Goal gives the team a shared purpose for the work they are doing. This helps the Developers make trade-offs, collaborate more effectively, and adapt the Sprint Backlog while still moving toward a meaningful outcome.

Option A is incorrect because Scrum does not define Sprint 0 as part of Scrum, and the Sprint Goal applies to every Sprint. Option B is incorrect because the Sprint Goal is highly valuable. The Product Backlog provides ordered possibilities for future work, but the Sprint Goal explains the purpose of the current Sprint. Option C is incorrect because the Sprint Goal does not guarantee that every selected Product Backlog item will be completed. The team may renegotiate scope with the Product Owner as more is learned, while still aiming to achieve the Sprint Goal.

The Sprint Goal supports flexibility. It allows the Developers to adjust their plan during the Sprint without losing direction. That is why Scrum uses a goal-oriented approach rather than only a task-oriented one.

According to the Scrum Guide, the best approach for Scrum Teams in order to produce valuable Increments is to have each Developer work on the component where they feel that they can contribute. This means that the Developers can self-organize and collaborate effectively to deliver a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid approaches, as they either imply that the Developers work in silos or rely on external people (such as developing functionality from beginning to end, working on an independent set of components, or working only as an independent layer of the system).

According to the Scrum Guide 1 , the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, one good way for a Scrum Team to ensure security concerns are satisfied is to add security concerns to the definition of “Done”. Another good way is to have the Scrum Team create Product Backlog items for each concern, as they are responsible for managing and refining the Product Backlog.

The correct answer is B. To present the Scrum Teams with insights and resources that help them improve. According to the Scrum Guide 1 , “The role of management in Scrum is to support the Product Owner with insights and information into high-value product and system capabilities.” Management also helps the Scrum Team by providing an environment that fosters agility, learning, and collaboration 2 . Management does not directly control or monitor the work of the Developers, nor does it interfere with the self-organization and autonomy of the Scrum Team 3 . Management’s function in Scrum is to enable and empower the Scrum Team to deliver value and continuously improve.

The two effective ways for the Scrum Team to make non-functional requirements visible are C and D.

C. Add them to the Definition of Done so the work is taken care of every Sprint.

The Definition of Done (DoD) is a shared understanding of what it means for a Product Backlog item to be complete and potentially releasable 1 . The DoD can include non-functional requirements that apply to the entire product or system, such as performance, security, usability, etc. By adding them to the DoD, the Scrum Team ensures that they are met every Sprint and that the quality of the product is maintained 2 .

D. Add them to the Product Backlog to ensure transparency.

The Product Backlog is an ordered list of everything that is known to be needed in the product 1 . The Product Backlog can include non-functional requirements that are specific to certain features or functionalities, such as response time, availability, scalability, etc. By adding them to the Product Backlog, the Scrum Team ensures that they are visible to all stakeholders and that they are prioritized and refined along with the functional requirements 3 .

A and B are not effective ways for the Scrum Team to make non-functional requirements visible.

A. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.

This approach does not make non-functional requirements visible, but rather postpones them until the end of the Sprint. This can lead to incomplete or low-quality Increments that do not meet the expectations of the customers or users. Moreover, this approach does not account for any changes or feedback that may occur during the Sprint 4 .

B. Put them on a separate list on the Scrum board, available for all to see.

This approach does not make non-functional requirements transparent, but rather isolates them from the functional requirements. This can lead to confusion or inconsistency in how they are handled by the Scrum Team. Moreover, this approach does not align with the principle of having a single source of truth for the product requirements, which is the Product Backlog 5 .

According to the Scrum Guide, two valid actions that the Developers can take when they realize that the workload may be greater than their capacity to complete the work are ensuring that the Scrum Team is aware, starting the Sprint, and monitoring progress, and removing or changing selected Product Backlog items. These actions are consistent with Scrum values and principles, such as transparency, adaptation, and collaboration. The other options are not valid actions, as they are either wasteful (such as recruiting additional Developers or canceling the Sprint) or unsustainable (such as working overtime).

The correct answers are B and C. According to the Scrum Guide, the Developers are accountable for creating a plan for the Sprint, which is the Sprint Backlog. That makes Option C correct. They are also accountable for organizing the work required to meet the Sprint Goal, which makes Option B correct. These are core elements of self-management in Scrum. Developers decide how to turn selected Product Backlog items into a valuable, usable Increment and how to adapt their plan throughout the Sprint.

Option A is incorrect because Scrum does not define “reporting productivity” as a Developer accountability. Scrum focuses on outcomes, transparency, and progress toward the Sprint Goal rather than traditional productivity reporting. Option D is incorrect because selecting the Product Owner is not a Developer accountability. Role assignments are determined by the organization, not by the Developers.

These accountabilities matter because Scrum relies on Developers to manage their own work rather than wait for direction from others. By creating and adapting the Sprint Backlog and organizing work toward the Sprint Goal, the Developers enable collaboration, flexibility, and accountability for producing a Done Increment each Sprint.

During the Sprint, the Scrum Master’s role is to facilitate inspection and adaptation opportunities as requested or needed, and to coach the team members in self-management, as stated in  3 : “The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the Scrum Team to improve its practices, within the Scrum framework.”

According to the Scrum Guide, the Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide 1 .  Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values 1 .  The Scrum Master is accountable for establishing Scrum 2 .  They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization while serving the Scrum Team as well as the larger organization 2 .

Option B is incorrect because keeping track of resource allocation is not a responsibility of the Scrum Master. The Scrum Master does not manage or control the resources of the Scrum Team or the organization.  The Scrum Team is self-organizing and responsible for managing its own work within a Sprint 1 .

Option C is incorrect because managing the performance of the Scrum Team is not a responsibility of the Scrum Master. The Scrum Master does not evaluate or appraise the performance of the Development Team or the Product Owner.  The Scrum Master serves the Development Team by coaching them on self-organization and cross-functionality, and serves the Product Owner by ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team 1 .

Option D is incorrect because the meetings and the objectives that a Scrum Team sets for itself are not a responsibility of the Scrum Master. The Scrum Master does not dictate or prescribe what meetings or objectives a Scrum Team should have.  The Scrum Master facilitates the Scrum Events as requested or needed, and ensures that they are positive, productive, and kept within the time-box 1 .

According to the Scrum Guide, the Developers are accountable for tracking the remaining work toward the Sprint Goal, as they are responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that someone else outside the Development Team (such as the Scrum Master, the Product Owner, or the Project Manager) is accountable for tracking the remaining work, which is not consistent with Scrum values and principles.

Two techniques that the Scrum Master could use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply are to involve the complete Scrum Team in making a decision, and to use coaching techniques such as open questions and active listening, as stated in [3]: “The Scrum Master should facilitate a constructive dialogue among the team members and help them reach a consensus on which agile practices to use. The Scrum Master should also use coaching techniques such as open questions and active listening to understand the underlying needs and motivations of each team member and to help them find common ground.”

The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that “development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, changing Development Team membership may affect their cross-functionality and self-organization in the short term.

The correct answer is D, because if a new Development Team decides that a Sprint Retrospective is unnecessary, the Scrum Master should begin facilitating productive and useful Sprint Retrospectives. The Scrum Guide states that “the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. … During each Sprint Retrospective, the Scrum Team plans ways to improve product quality by adapting the definition of ‘Done’ as appropriate.” Therefore, the Scrum Master should help the Development Team understand the value and importance of the Sprint Retrospective, and make it an engaging and constructive event.

 According to the Scrum Guide, a Development Team needs a Sprint Goal because it provides guidance and focus for building an Increment that delivers value. The other options are not valid reasons for having a Sprint Goal, as they are either incorrect (such as giving purpose only to Sprint 0 or ensuring implementation of all Product Backlog items) or irrelevant (such as knowing everything from the Product Backlog).

Scrum promotes self-management by empowering the Scrum Team to take ownership of their work and processes. The best three answers are:

A. By having the Scrum Master protect the Scrum Team: The Scrum Master plays a key role in shielding the team from external distractions and impediments, allowing the team to focus on self-management and delivering value.

B. By the Scrum Team deciding what work to do in a Sprint: During Sprint Planning, the Scrum Team collaboratively selects and commits to the work they can accomplish within the Sprint, fostering self-organization and decision-making.

C. By being a lightweight framework: Scrum ' s simplicity and minimal structure provide the team with the flexibility to adapt and manage their work, encouraging self-management without imposing rigid controls.

The best answer is C. When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done. This is because the Definition of Done creates transparency and ensures that the product Increment meets the quality standards required for the product 1 . If each Scrum Team has its own Definition of Done, it may lead to inconsistencies, conflicts, and technical debt in the product. Therefore, the Scrum Teams should collaborate and agree on a common Definition of Done that applies to all Product Backlog Items and Increments. This way, the Scrum Teams can deliver a potentially releasable product Increment at the end of every Sprint 2 .

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).

The best answer is C. The function or purpose of management in Scrum is to present the Scrum Teams with insights and resources that help them improve. According to the article What is the Function or Purpose of Management in Scrum? , management is still critical to providing vision, securing resources, hiring talent, training teams, removing roadblocks, and continuously improving. Management also encourages collaboration and establishes Scrum Team autonomy, which are essential for Scrum’s values and principles.

A, B and D are not good answers because they imply a command-and-control approach that contradicts Scrum’s values of respect, openness, and self-organization. Management in Scrum is not supposed to micromanage, judge, or interfere with the work of the Developers, but rather support them and enable them to deliver value.

The correct answer is D, because this statement best describes the Sprint Review. The Scrum Guide states that “a Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint.” Therefore, the Sprint Review is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

According to the Scrum Guide, a high-performance Scrum Team does not run a Release Sprint, as this is not a Scrum event. A Release Sprint is a term used to describe a Sprint that is dedicated to finalizing the product for release, such as fixing bugs, polishing features, or integrating components. This is contrary to the Scrum principle of delivering a potentially releasable Increment at the end of each Sprint, regardless of whether it is actually released or not. Therefore, the answer is false.

The correct answer is B because cross-functional teams in Scrum are not optimized to work on only one component or one technical layer of a system. A cross-functional Scrum Team has all the skills necessary to create value each Sprint and deliver a usable Increment. This means the team should be capable of working across the different skills and disciplines needed to complete Product Backlog items according to the Definition of Done.

If a team is organized around only one component or specialty, it creates handoffs, dependencies, and silos. Those conditions reduce agility and make it harder to deliver a complete Increment each Sprint. Scrum instead favors teams that can collaborate across analysis, design, development, testing, and other needed capabilities so they can produce finished product value rather than partial technical output.

Cross-functionality supports self-management and reduces delays caused by waiting on other specialists or teams. It helps the Scrum Team focus on outcomes instead of isolated activities. In Scrum, the goal is not local optimization of a single layer or function. The goal is delivering complete, useful, high-value Increments frequently and transparently.

According to the Scrum Guide 1 , the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time.

The correct answer is A, because keeping component teams while starting Scrum may cause less initial disruption than organizing into new teams. As they start using Scrum, they will discover what works best for them and how to potentially re-organize towards feature teams. However, component teams may face some challenges in delivering a working Increment of software that provides business value every Sprint, as they may depend on other teams or layers.

The correct answer is C because the Product Owner is a full member of the Scrum Team and participates in the Sprint Retrospective along with the Developers and Scrum Master. The Sprint Retrospective is not a meeting only for Developers or only for process specialists. It is an event for the Scrum Team to inspect how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done, and then identify improvements for the future.

The Product Owner’s role in this event is not to act as an external observer or a stakeholder representative. Instead, the Product Owner contributes as a Scrum Team member by sharing observations, listening to concerns, and collaborating on ways to improve effectiveness and value delivery. This shared participation supports transparency and continuous improvement.

Option A is incorrect because the Retrospective is an internal Scrum Team event, not a stakeholder reporting session. Option B is incorrect because the Product Owner absolutely should participate. Option D is incorrect because capturing backlog requirements is not the purpose of the Retrospective. The main purpose is improvement of how the team works together.

When a Development Team determines that it will not be able to finish the complete forecast, both the Product Owner and the Development Team have to be present when reviewing and adjusting the Sprint work selected, as stated in [6]: “If there is not enough work remaining for all members of a Development Team then they can renegotiate scope with their Product Owner. If there is too much work remaining then they can also renegotiate scope with their Product Owner.”

The correct answer is D, because the Scrum Guide states that “a Sprint is a container for all other events. 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.” Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items or tasks are completed or not.

The Product Backlog is ordered by the Product Owner with the most valuable items placed at the top, as stated in [6]: “The Product Owner is responsible for ordering items on their product backlog based on their value to customers and users. Value can be measured by various factors, such as business value, customer satisfaction, risk reduction, learning opportunities, etc. The most valuable items are placed at the top of the product backlog so that they can be delivered sooner by the development team.”

According to the Scrum Guide 1 , an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, an Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, implementation of a Product Backlog item is considered complete when the item has no work remaining in order to be potentially released.

The correct answer is B, because the time-box for the Sprint Planning meeting is 8 hours for a monthly Sprint. The Scrum Guide states that “Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.”

The correct answer is B, because the Scrum Guide states that “the Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.” Therefore, the Sprint Goal provides the Development Team with a target and overarching direction for the Sprint.

According to the Scrum Guide, when many Scrum Teams are working on a single product, they must have a Definition of Done that makes their combined work potentially releasable. This ensures that there is a clear and consistent understanding of what “Done” means for the product and that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid descriptions of the Definition of Done for multiple Scrum Teams, as they either create inconsistency, confusion, or waste (such as having different definitions, discussing and reconciling differences during a hardening Sprint, or having the Scrum Masters define a common Definition of Done).

According to the Scrum Guide 1 , the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, when the Scrum Team gets caught in an internal disagreement about which development techniques to apply, two techniques that the Scrum Master could use are:

Involve the complete Development Team, as they are responsible for managing and refining their own work.

Use coaching techniques, such as open questions and active listening, to help the Development Team resolve their conflict and reach a consensus.

The other options are not appropriate, as they may undermine the self-organization and empowerment of the Developers.

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 1 , 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.

According to the Scrum Guide 1 , the Sprint Backlog is the property of the Developers and no one else can tell them which items they should work on. The Developers can select any item from the Product Backlog that they forecast they can complete within a Sprint. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, no one owns a Sprint Backlog item, but the entire Development Team is accountable for it.

According to the Scrum Guide 1 , one aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. Therefore, it is most appropriate for a Development Team to change the definition of “Done” during the Sprint Retrospective.

If the Development Team cannot complete its work by the end of the Sprint, then the Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length, as stated in [7]: “If a Development Team determines it has overcommitted itself for a Sprint, one option is to collaborate with the Product Owner to negotiate removing or reducing scope. Another option is to simply work hard and do its best, without cutting quality or pressuring individuals. In either case, the Development Team learns from its experience and uses this learning when planning future Sprints.”

According to the Scrum Guide, every Scrum Team must have a Product Owner and a Scrum Master, as they are essential roles for Scrum. The outcomes of the Scrum Team are affected by their participation and availability, as they provide guidance, support, and facilitation to the Development Team and the stakeholders. The other options are false, as they imply that a Product Owner or a Scrum Master can be replaced or optional, which is not consistent with Scrum.

The correct answer is E, because any of the above (or others) which are a decomposition of the selected Product Backlog items can be included in the Sprint Backlog. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.” Therefore, any work items that help the Development Team achieve the Sprint Goal can be part of the Sprint Backlog.

According to the Scrum Guide, the Product Backlog is an ordered list of everything that is known to be needed in the product. It is allowed to grow and change as more is learned about the product and its customers. The other options are not accurate descriptions of the Product Backlog, as they are either too restrictive (such as providing just enough information or baselining to follow change management processes) or too comprehensive (such as containing all foreseeable tasks and requirements or enabling a complete project plan).

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).

 According to the Scrum Guide, the Sprint Review is a time for the Scrum Team and the stakeholders to inspect the product Increment and adapt the Product Backlog if needed. The Product Owner is responsible for keeping the stakeholders aware of the progress of the project and inviting them to the Sprint Review. If the Product Owner has not been doing this, or if the stakeholders have not been using the Sprint Review to inspect and evaluate progress, then they may be disappointed and angry at the seventh Sprint Review. The other options are not likely factors that led to this situation, as they are either irrelevant (such as the PMO or the development area) or incorrect (such as delaying the release).

The best answers are B and C because the Scrum Master serves both the Product Owner and the Scrum Team by helping address quality concerns in a constructive, transparent, and Scrum-consistent way. Quality in Scrum is not handled outside the team or delegated only to testers. When a stakeholder raises a concern about low quality, the issue should be made visible and addressed through the Product Backlog, the Definition of Done, and direct collaboration within the Scrum Team.

Option B is correct because quality expectations and stakeholder concerns should be reflected in Product Backlog items when appropriate, and the Developers need to understand those concerns clearly. Option C is also correct because the Scrum Master helps the Product Owner find an effective way to work with the Developers and address the issue empirically.

Option A is incorrect because acceptable quality standards are not solely for Developers to decide in isolation. Option D is incorrect because Scrum does not create a separate tester role responsible for quality. Option E is too passive and delayed. A significant quality concern should be addressed promptly, not simply postponed to the Sprint Retrospective.

According to the Scrum Guide, an Increment does not have to be released to customers or users at the end of each Sprint. However, it must be in a usable condition and meet the Definition of Done. The decision to release an Increment is made by the Product Owner, based on the value and feedback obtained from stakeholders. The other option is not valid, as it implies that releasing an Increment is mandatory at the end of each Sprint.

According to the Scrum Guide 1 , the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, if a Product Backlog item worked on during the Sprint does not meet the definition of “Done”, two things that should happen with the undone Product Backlog item are:

Put it on the Product Backlog for the Product Owner to decide what to do with it, as they are accountable for effective Product Backlog management and ordering.

Do not include the item in the Increment this Sprint, as it does not meet the quality standards and may compromise value.

The other options are not appropriate, as they may compromise transparency, inspection, or adaptation.

According to the Scrum Guide, the Product Owner has the final decision about the order of items in the Product Backlog, 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.

According to the Scrum Guide 1 , a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review, as stated in [5]: “The Scrum Master should educate the IT manager about how Scrum works and how progress is measured. The Scrum Master should invite the IT manager to attend the Sprint Review where the Development Team demonstrates what was accomplished during the Sprint. The Scrum Master should also explain that status reports are not necessary in Scrum, as transparency is ensured by using artifacts such as Product Backlog, Sprint Backlog, and Increment.”

he correct answer is A, because doing all work needed to meet the definition of “Done” enhances the transparency of an increment. The Scrum Guide states that “when a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” Therefore, by meeting the definition of “Done”, an increment becomes transparent to all stakeholders and ready for release.

According to the Scrum Guide 1 , the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

According to the Scrum Guide, a Scrum Team must release each Increment when it makes sense to do so, based on the value and feedback obtained from stakeholders. The decision to release an Increment is made by the Product Owner, who is responsible for maximizing the value of the product and the work of the Development Team. The other options are not valid, as they imply that releasing an Increment is either mandatory (such as after every Sprint), conditional (such as when the product is free of defects), or irrelevant (such as when the Scrum Team finishes their work).

A Product Owner releases each Increment when it makes sense, as stated in [2]: “The Product Owner decides when to release an Increment. This can be done at any time during or after a Sprint. The Product Owner may choose to release an Increment when it delivers enough value to customers or users, when it meets a market opportunity, when it reduces risk or uncertainty, or when it aligns with other business goals.”

The correct answer is E, because all of these topics can be discussed during a Sprint Retrospective. The Scrum Guide states that “the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. … During each Sprint Retrospective, the Scrum Team plans ways to improve product quality by adapting the definition of ‘Done’ as appropriate.” Therefore, the Scrum Team can discuss any aspect of their process, communication, skills, or definition of ‘Done’ that may help them improve.

According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).

The correct answer is B, because the Development Team determines how work is performed during the Sprint. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, the Development Team has the autonomy and responsibility to organize and manage its own work.

According to the Scrum Guide 1 , self-organization is one of the essential characteristics of Scrum Teams. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Self-organization enables teams to deliver faster and better results by harnessing their creativity and skills. Some benefits of self-organization are:

Increased creativity, as team members have more freedom and autonomy to explore new ideas and solutions.

Increased self-accountability, as team members take ownership and responsibility for their work and outcomes.

Increased commitment, as team members are more engaged and motivated by having a say in how they work.

The other options are not benefits of self-organization, as they may imply external control or pressure.

The answer is A. True. The Sprint Backlog is a result of Sprint Planning, and it includes the Sprint Goal. According to the Scrum Guide, the Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how) 1 . The Sprint Goal is the single objective for the Sprint, and it provides coherence and focus for the Scrum Team 2 . The Sprint Backlog is a plan by and for the Developers, and it is updated throughout the Sprint as more is learned 2 .

The correct answer is E because all of the listed topics are appropriate subjects for a Sprint Retrospective. The Scrum Guide states that during the Sprint Retrospective, the Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done. The team then identifies improvements to increase quality and effectiveness.

Methods of communication are relevant because communication strongly affects collaboration and transparency. The way Sprint Planning is conducted is also valid to inspect if the team believes planning could be more effective. Skills needed to improve delivery are appropriate because a Scrum Team continuously seeks to become more capable and cross-functional. The Definition of Done is explicitly a valid retrospective topic because it may need refinement as the team matures and raises quality standards.

The Sprint Retrospective is the Scrum Team’s formal opportunity to inspect and adapt its ways of working. It is not limited to one narrow process area. Anything that affects the team’s effectiveness, quality, collaboration, or ability to deliver valuable Increments can be discussed, making “All of the above” the best answer.

The correct answer is A, because the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner is to monitor communications between them and facilitate direct collaboration. The Scrum Guide states that “the Scrum Master serves the Product Owner in several ways, including … facilitating Scrum events as requested or needed.” Therefore, the Scrum Master should help the Development Team and the Product Owner interact regularly and productively during the Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective events.

According to the Scrum Guide 1 , Product Backlog refinement is an ongoing activity in which Product Backlog items are reviewed and revised. The Developers who will be doing the work are responsible for sizing or estimating it. The Product Owner may influence them by helping them understand and select trade-offs.

The correct answer is B, because there is no role called “Project Manager” in Scrum. The Scrum Guide states that “Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule.” Therefore, Scrum has only three roles: Product Owner, Scrum Master, and Developer.

The correct answer is A, because a good first question for you to suggest the group thinks about when forming into teams is how will we make sure all teams have the right amount of expertise. This question helps the group consider the cross-functionality and self-organization of the Development Teams, which are essential for delivering a potentially releasable Increment every Sprint.

The correct answers are D and E, because these are two activities that a Product Owner can engage in during a Sprint. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, the Product Owner can answer questions from the Development Team about items in the current Sprint, and work with the stakeholders to understand their needs and expectations.

The correct answer is A because the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Product Backlog ordering should therefore be driven primarily by value, not by keeping every Developer busy at all times. Scrum does not optimize for utilization. It optimizes for value delivery, learning, and progress toward the Product Goal.

The Scrum Master should coach the Product Owner to keep the Product Backlog ordered based on what delivers the most value and best supports product outcomes. External dependencies may influence sequencing, but they should not cause the Product Owner to abandon value-based ordering just to fill capacity. In Scrum, some inefficiency may temporarily occur due to uncertainty or dependency constraints, but that is not a reason to shift toward activity-based planning.

Option B is too prescriptive and assumes a specific backlog ordering response. Option C is incorrect because maximizing utilization is not the Product Owner’s responsibility and is not a Scrum objective. Scrum encourages focus on valuable Increments, not on ensuring that everyone is always fully occupied regardless of whether the work is the most important.

According to the Scrum Guide 1 , 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-box for the Daily Scrum is 15 minutes or less for a one-month Sprint. Its location and time remain constant.

According to the Scrum Guide, two intended outcomes of the Daily Scrum are a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal, and new impediments for the Scrum Master to take care of. The other options are not intended outcomes of the Daily Scrum, as they are either irrelevant (such as updating a Scrum board) or inappropriate (such as providing an update or a status report).

According to the Scrum Guide 1 , the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.

According to the Scrum Guide, a self-organizing Development Team chooses how to best accomplish its work, rather than being directed by others outside the team. The other options are not choices that a self-organizing Development Team makes, as they are either determined by the Scrum framework (such as Sprint length and Product Backlog ordering) or by collaboration with other roles (such as stakeholders for the Sprint Review and when to release).

According to the Scrum Guide, the amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning is as much as is required to meet the Scrum Team’s Definition of Done. This means that the Developers must ensure that every item they work on is in a usable condition and meets all quality standards agreed upon by the team. The other options are not valid descriptions of the amount of work required, as they are either too vague (such as all development work and some testing or a proportional amount of time) or incorrect (such as fitting as much as possible or deferring work to the next Sprint).

According to the Scrum Guide 1 , an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.

The correct answer is C. The Scrum Team creates the Definition of Done. According to the Scrum Guide 1 , “The Developers are required to conform to the Definition of Done, which is defined and evolves with the Scrum Team.” The Definition of Done is a commitment by the Developers for the Increment, but it is also a shared understanding within the whole Scrum Team, including the Product Owner and the Scrum Master 2 . The Scrum Team collaborates to create and update the Definition of Done as needed, based on the product and organizational standards 3 . The Definition of Done is not imposed by any external authority or individual.

The best two answers are A and C. These two ways of creating Scrum Teams are consistent with Scrum’s values because they respect the self-organization and empowerment of the people who will be working in the teams. They also foster openness and courage by allowing the people to express their preferences and opinions about the new structure.

B, D and E are not consistent with Scrum’s values because they impose a top-down approach that does not involve the people who will be affected by the change. They also undermine the commitment and focus of the teams by assigning them to work on something they may not be interested in or passionate about.

The two intended outcomes of the Daily Scrum are A and D.

A. Identification of impediments that may prevent the Developers from achieving the Sprint Goal.

The Daily Scrum is an opportunity for the Developers to inspect their progress toward the Sprint Goal and to identify any impediments or challenges that may hinder them from completing the work in the Sprint Backlog 1 . The Scrum Master can help the Developers remove these impediments or find ways to overcome them 2 .

D. A shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal.

The Daily Scrum is also an opportunity for the Developers to adapt their plan for the next 24 hours based on their current situation and the Sprint Goal 1 . The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work 1 . This creates focus and improves self-management.

B, C, and E are not intended outcomes of the Daily Scrum.

B. An update of completed tasks and of the remaining work so the Scrum Master can plan the next day.

The Daily Scrum is not a status meeting or a report for the Scrum Master or anyone else 2 . The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master 1 . The Scrum Master’s role is to ensure that the event happens, that it is positive and productive, and that it stays within the 15-minute timebox 2 .

C. An updated Scrum board to make Sprint progress transparent for the stakeholders.

The Daily Scrum is an internal meeting for the Scrum Team, not for external stakeholders 1 . The Scrum board is a tool that can help the Developers visualize their work, but it is not an outcome of the Daily Scrum. The outcome of the Daily Scrum should be an updated Sprint Backlog and an updated Sprint plan to achieve the Sprint Goal 3 .

E. A status report for the upper management indicating what each individual has done, will be doing, and what is impeding him/her.

The Daily Scrum is not a status report for anyone, especially not for upper management 2 . The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance 1 . The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team 2 .

The best answer is B. The Developers on the Scrum Team should write the user documentation. According to the Scrum Guide, the Definition of Done creates transparency and ensures that the product Increment meets the quality standards required for the product 1 . If user documentation is part of the Definition of Done, then it should be completed within the Sprint by the Scrum Team 1 . The Scrum Team should have all the skills needed to deliver the product, and if user documentation is part of the product, then that skill should be on the team as well 2 . The Developers on the Scrum Team are responsible for creating a plan for delivering the Increment, which includes user documentation 1 . They can also ask for help from other more experienced writers outside the team, or learn the skill through training or workshops 2 . The other options are not consistent with the Scrum values and principles, as they would create dependencies, delays, and waste in the product development process.

The correct answers are B and E, because these statements are true about the length of the Sprint. It is best to have Sprints of consistent length throughout a development effort, as this helps establish a reliable rhythm and cadence for the Scrum Team and the stakeholders. All Sprints must be one month or less, as this ensures that the Scrum Team can inspect and adapt frequently and deliver value incrementally.

According to the Scrum Guide 1 , 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 Scrum Master and Product Owner may attend as observers, but only if it is useful for the Developers.

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).

 According to the Scrum Guide, the time-boxed events in Scrum are Sprint Retrospective, Sprint Planning, and Daily Scrum. These events have a maximum duration that cannot be exceeded. The other options are not time-boxed events in Scrum, as they are either not part of Scrum (such as Release Planning, Release Retrospective, Sprint Testing, and Sprint 0) or not events at all (such as Definition of Done).

Explanation of Correct Answer: According to the Scrum Guide 1 , the only required events in Scrum are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These events enable transparency, inspection, and adaptation. The other options are not mandatory in Scrum, although they may be useful in some contexts.

According to the Scrum Guide, a Scrum Master fulfills a different role from a traditional project manager. A Scrum Master is a servant-leader and a coach for the Scrum Team and the organization, not a manager or a supervisor. A Scrum Master does not assign tasks, set deadlines, or monitor progress, but rather facilitates self-organization, collaboration, and empiricism within the Scrum Team and the organization.