The correct answer is B, because the Product Owner does not make sure the team selects enough from the Product Backlog for a Sprint to satisfy the stakeholders. 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 is responsible for choosing the scope of work for a Sprint.

The Developers determine how many Product Backlog items they select for a Sprint, as stated in the Scrum Guide: “The Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.”

The correct answer is D. 10 or fewer. According to the Scrum Guide 20201, “The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.” The other options are outdated or incorrect. Option A was based on the previous version of the Scrum Guide, which suggested a range of 3 to 9 developers2. Option B is too vague and does not account for the upper limit of team size. Option C is too specific and does not allow for flexibility.

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, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other options are not valid, as they are either too long (such as monthly), too vague (such as whenever it’s done), or too short (such as 4 hours for a one-month Sprint).

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

The correct answer is C, because the second Sprint starts immediately after the first Sprint. The Scrum Guide states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.”

According to the Scrum Guide, the Scrum Master is responsible for coaching the Scrum Team to improve its skills, tools and environment over time and adjust the Definition of Done accordingly1. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product1. The Definition of Done should be possible to achieve given current circumstances2. Therefore, option B and E are appropriate for a Scrum Master to do, if the Scrum Team does not have the tools and environment to completely finish each selected Product Backlog item.

Option A is not appropriate because declaring the Scrum Team not ready for Scrum implies that there is a fixed set of prerequisites for using Scrum, which is not true. Scrum is a framework that can be applied to any complex product development effort1.

Option C is not appropriate because encouraging the Product Owner to accept partially done Increments until the situation improves violates the principle of transparency. Transparency requires that the Increment is a usable product that meets the current Definition of Done1. Accepting partially done Increments also increases technical debt and reduces value delivery3.

Option D is not appropriate because refocusing the current Sprint on establishing the Scrum Team’s environment instead of delivering an Increment goes against the purpose of a Sprint. A Sprint is a time-boxed event that serves as a container for the other Scrum events and activities. The goal of each Sprint is to deliver a potentially releasable Increment that adheres to the current Definition of Done1.

References: 1: The Scrum Guide 2: Suggested Reading for Professional Scrum Master™ I 3: Mastering Professional Scrum

The correct answer is C, because if necessary, the Development Team is responsible for removing a team member who is creating a hostile environment. 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 should manage its own composition and dynamics, and may need help from the Scrum Master to facilitate this process.

 According to the Scrum Guide, the Daily Scrum is held at the same time and same place to reduce complexity and promote consistency. The other options are not valid reasons for holding the Daily Scrum at the same time and same place, as they are either irrelevant (such as naming the place) or incorrect (such as being demanded by the Product Owner or booking rooms in advance).

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

Two techniques that would be most helpful in this situation are to discuss the impediments with the Development Team, and to prioritize the list and work on them in order, as stated in [3]: “The Scrum Master should facilitate a discussion with the Development Team to identify and prioritize the impediments that are blocking their progress. The Scrum Master should then work with the Development Team and other stakeholders to remove or mitigate these impediments as soon as possible.”

The best answer is C. Ensure every Increment meets them. Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs1. NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release1. The Scrum Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.

The correct answer is B, because when multiple teams work together on the same product, they should not maintain separate Product Backlogs. The Scrum Guide states that “multiple Scrum Teams often work together on the same product. One product goal unites them. Therefore, they must mutually define and comply with a definition of ‘Done’ that applies to their combined work product. … Multiple Scrum Teams working on the same product use the same Product Backlog.”

The correct answer is C, because 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.” Therefore, the main reason for the Scrum Master to be at the Daily Scrum is to ensure that it happens, but he or she does not have to be there.

The correct answers are B and D, because these are the most appropriate responses for the Scrum Master. The Scrum Master should coach the team on why the Daily Scrum is important as an opportunity to update the plan, inspect the progress, and synchronize the activities of the Development Team. The Scrum Master should also learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum, rather than imposing a decision or accepting their request without question.

According to the Scrum Guide1, 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.

References: Scrum Guide

According to the Scrum Guide1, the Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is accountable for maximizing value resulting from work by Developers. The Product Owner is also accountable for effective Product Backlog management, which includes:

Developing and explicitly communicating the Product Goal;

Creating and clearly communicating Product Backlog items;

Ordering Product Backlog items; and

Ensuring that the Product Backlog is transparent, visible and understood.

Therefore, the Product Owner is responsible for clearly expressing Product Backlog items.

References: Scrum Guide

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, two things that the Scrum Team should do during the first Sprint are building at least one piece of valuable functionality and creating at least one valuable, useful Increment. These are the goals of every Sprint, regardless of its order. The other options are not things that the Scrum Team should do during the first Sprint, as they are either out of scope (such as defining major product features and a release plan architecture or making a plan for the rest of the project) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).

An example of an Increment is a valuable, useful set of product features, as stated in [4]: “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, each Increment must be usable.”

Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

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.

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

The correct answer is C, because as soon as possible in the Sprint, the Development Team should work with the Product Owner to remove some work or Product Backlog items if they realize they have selected too much work to finish in the Sprint. The Scrum Guide states that “the Development Team may renegotiate the selected Product Backlog items with the Product Owner. If the Development Team realizes it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner. The Development Team may also invite other people to attend to provide technical or domain advice.”

According to the Scrum Guide, the Product Owner does not make sure that the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are responsible for selecting how much work they can do in a Sprint, based on their capacity and past performance. The Product Owner may influence them by ordering and clarifying the Product Backlog items, but does not control their selection.

The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal description of the state of the Increment when it meets the quality measures required for the product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and ensure every Increment meets them.

The correct answers are A, C, and E, because these are feedback loops in Scrum. The Sprint Review is a feedback loop that allows the Scrum Team and the stakeholders to inspect the Increment and adapt the Product Backlog. The Sprint Retrospective is a feedback loop that allows the Scrum Team to inspect itself and create a plan for improvements. The Daily Scrum is a feedback loop that allows the Development Team to inspect its progress and plan its work for the next 24 hours.

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 answers are B and D, because 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 can remove or change selected Product Backlog items in agreement with the Product Owner if they see that the workload is greater than they can handle. The Development Team should also ensure that the Product Owner is aware of the situation, start the Sprint, and monitor progress.

Three topics for the Developers to discuss at the Daily Scrum as they inspect their progress toward the Sprint Goal are:

What have we learned since yesterday, and how should we modify our plan to increase our ability to meet the Sprint Goal?

Are there any impediments blocking progress toward the Sprint Goal?

Are there any decisions that need to be made to maintain progress toward the Sprint Goal?

These topics are suggested by [6]: “The structure of the meeting is set by the Developers and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based.”

According to the Scrum Guide1, 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.

References: Scrum Guide

The correct answer is B, because the Sprint Backlog is created during the Sprint Planning meeting. 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.”

The Product Owner is responsible for engaging the stakeholders, as stated in the Scrum Guide1: “The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.”

The correct answers are B and C, because these are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity. The Scrum Guide states that “the Scrum Master serves the Development Team in several ways, including … removing impediments to the Development Team’s progress; facilitating Scrum events as requested or needed; and coaching the Development Team in self-organization and cross-functionality.” Therefore, by removing impediments and facilitating decisions, the Scrum Master helps the Development Team focus on their work and deliver value.

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.

The correct answer is B, because the time-box for a Daily Scrum is 15 minutes. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.”

The correct answers are B and C, because these are two responsibilities of a self-organizing Development Team. The Scrum Guide states that “the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of ‘Done’ product at the end of each Sprint. Development Teams are structured and empowered by the organization to organize and manage their own work.” Therefore, the Development Team should pull Product Backlog items for the Sprint and do the work planned in the Sprint Backlog.

According to the Scrum Guide1, when multiple Scrum Teams are working together on one product, they must coordinate their work with each other. One way to do this is through Nexus, a framework for scaling Scrum. Nexus helps to reduce cross-team dependencies and integration issues by making them more transparent. The key concern when multiple Development Teams are working from the same Product Backlog is minimizing dependencies between teams so that they can deliver an integrated Increment that meets the definition of “Done”.

References: Scrum Guide, Nexus Guide

According to the Scrum Guide, the Scrum Team consists of three roles: the Scrum Master, who coaches and facilitates the team; the Product Owner, who manages and prioritizes the Product Backlog; and the Development Team, who delivers a potentially releasable Increment at the end of each Sprint. Users and customers are not roles on the Scrum Team, but they are stakeholders who may provide feedback and input to the product.

According to the Scrum Guide, when multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint, in order to accurately inspect what is done and ensure that there is no technical debt or unfinished work at the end of each Sprint. The other options are not valid, as they imply that integration can be skipped, delayed, or done only for some teams, which is not consistent with Scrum values and principles.

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.

The correct answer is A, because the Product Owner does not need to be present at the Daily Scrum. The Scrum Guide states that “the Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. … The structure of the meeting is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal.” Therefore, the Daily Scrum is an internal event for the Development Team, and the Product Owner can attend only if invited by the Development Team.

According to the Scrum Guide, the Developers on the Scrum Team should write the user documentation, as they are responsible for creating a “Done” Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they imply that the user documentation can be deferred, ignored, or outsourced, which is not consistent with Scrum values and principles.

According to the Scrum Guide, multiple Scrum Teams working on the same product do not have to have the same Sprint start date. They may start their Sprints at different times, as long as they synchronize their work and integrate their Increments at least by the end of each Sprint. The other option is not valid, as it implies that having the same Sprint start date is mandatory for multiple Scrum Teams.

Sprint Backlog is owned by the Development Team. 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. … The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.”

According to the Scrum Guide, the Product Owner must participate in the Daily Scrum when he or she is actively working on items on the Sprint Backlog; however, they participate as a Developer, not as an authority figure. This means that the Product Owner can share progress, plans, and impediments with the other Developers and collaborate with them on delivering value. The other options are not valid reasons for the Product Owner to participate in the Daily Scrum, as they are either irrelevant (such as representing stakeholders or discussing impediments) or inappropriate (such as being asked by the Scrum Master).

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

The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum’s values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.

A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.

C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.

According to the Scrum Guide1, 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.

References: Scrum Guide

According to the Scrum Guide1, 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, two things that are appropriate for a Scrum Master to do if the Development Team doesn’t have the engineering tools and infrastructure to completely finish each selected Product Backlog item are:

Coach the Development Team to improve its skills, tools, and infrastructure over time and adjust the Definition of “Done” accordingly.

Have the Development Team establish a Definition of “Done” that is actually possible to achieve given current circumstances.

The correct answer is B, because the Development Team is responsible for managing the progress of work during a Sprint. The Scrum Guide states that “the Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress.”

The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that “a new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, there is no time required after a Sprint to prepare for the next Sprint.

During the Sprint Retrospective, the Scrum Team may add items to the Sprint Backlog for the next Sprint, as stated in [5]: “The purpose of each Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team plans ways to implement improvements identified during this meeting into its way of working. By doing this it reinforces empiricism throughout its work. Improvements may be implemented at any time during a Sprint or they may be planned for subsequent Sprints.”

The correct answer is D, because the recommended size for a Development Team is 3 to 9 members. The Scrum Guide states that “fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.”

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.

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

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 Team2. The Sprint Backlog is a plan by and for the Developers, and it is updated throughout the Sprint as more is learned2.

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

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

According to the Scrum Guide1, 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 product has one Product Backlog, as it is a single source of requirements for any changes to be made to the product. There should be only one Product Owner, who is accountable for maximizing the value of the product and the work of the Development Team. Having multiple Product Owners or Product Backlogs would create confusion, inconsistency, and waste.

According to the Scrum Guide, two activities that a Product Owner may engage in during a Sprint are updating management on what is being worked on and answering questions from the Development Team about items in the current Sprint. These activities are part of the Product Owner’s responsibilities to manage and prioritize the Product Backlog, communicate with stakeholders, and collaborate with the Development Team. The other options are not activities that a Product Owner should engage in during a Sprint, as they are either done by the Scrum Master (such as running the Daily Scrum) or by the Development Team (such as prioritizing their work on the Sprint Backlog).

Explanation of Correct Answer: According to the Scrum Guide1, 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.

References: Scrum Guide

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 answers are C and E, because these statements explain what “Done” means. No work left from the definition of “Done” means that all Product Backlog items selected for a Sprint meet the quality criteria agreed upon by the Scrum Team. All work to create software that is ready to be released to end users means that the Increment is potentially releasable at any time during the Sprint.

The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of ‘Done’ ensures that they are met every Sprint and do not accumulate technical debt.

References: Suggested Reading for Professional Scrum Master™ I

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

According to the Scrum Guide1, 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.

References: Scrum Guide

A Developer is accountable for creating a plan for the Sprint, the Sprint Backlog, and organizing the work required to meet the Sprint Goal, as stated in the Scrum Guide: "Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

Creating a plan for the Sprint, the Sprint Backlog;

Instilling quality by adhering to a Definition of Done;

Adapting their plan each day toward the Sprint Goal; and,

Holding each other accountable as professionals."

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.