PSM-I Professional Scrum Master I Questions and Answers

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

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

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

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

According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does.

References: Scrum Guide

The correct answer is A, because in accordance with Scrum theory, a group of 100 people should be divided into multiple Development Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing itself into teams. This approach respects the self-organization and empowerment of the people who will do the work, and allows them to form cross-functional and collaborative teams that can deliver value.

According to the Scrum Guide1, the Sprint Review is an informal meeting at the end of the Sprint, where the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; the Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; and the Development Team demonstrates the work that it has “Done” and answers questions about the Increment. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is mainly an inspect and adapt opportunity for the Scrum Team and stakeholders.

References: Scrum Guide

In the Scrum framework, there is no specific role or accountability for a Tester. Instead, the responsibility for quality lies with the entire Scrum Team, particularly the Developers. Scrum emphasizes cross-functional teams, where every team member contributes to all aspects of the development process, including testing. The Developers collectively ensure that the work meets the Definition of Done and maintains high-quality standards. This approach fosters collaboration, shared responsibility, and continuous improvement, aligning with the core principles of Scrum.

According to the Scrum Guide1, the heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. The 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.

References: Scrum Guide

The correct answers are A, B, and D, because these techniques would be most helpful in this situation. Consulting with the Development Team may help identify the root causes of the impediments and possible solutions. Prioritizing the list and working on them in order may help reduce the backlog and focus on the most important or urgent issues. Alerting management to the impediments and their impact may help escalate the problems and get support from the organization.

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

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

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

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

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

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

References: Scrum Guide

According to the Scrum Guide, 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 is created by the Developers and it is used to assess when work is complete on the product Increment1.

The Scrum Guide also states that the Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and becomes more stringent as the Scrum Team matures1. Therefore, it is important for the Scrum Team to regularly inspect and adapt the Definition of Done to reflect their current situation and needs.

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 Sprint1. The Sprint Retrospective focuses on three questions: What went well in the Sprint? What could be improved? What will we commit to improve in the next Sprint?1 These questions can help the Scrum Team identify potential changes to the Definition of Done that would increase the quality and value of the product.

Option A is incorrect because Product Backlog refinement is not a formal Scrum event, but rather an ongoing activity that can happen at any time during the Sprint1. Product Backlog refinement is mainly concerned with adding detail, estimates, and order to Product Backlog items1. Changing the Definition of Done during Product Backlog refinement could cause confusion and inconsistency among the Developers and the Product Owner.

Option C is incorrect because Sprint Planning is a time-boxed event that initiates a Sprint by defining a Sprint Goal and selecting Product Backlog items that deliver one coherent function1. Sprint Planning is based on the current state of the Product Backlog and the latest Definition of Done1. Changing the Definition of Done during Sprint Planning could disrupt the flow of the event and affect the scope and feasibility of the Sprint.

Option D is incorrect because prior to starting a new project is not a specific time in Scrum. Scrum does not prescribe any phases or stages for a project, but rather an empirical approach that relies on frequent inspection and adaptation of both the product and the process1. Changing the Definition of Done before starting a new project could be premature and irrelevant, as the Scrum Team may not have enough information or experience to define what ‘Done’ means for their product.

References: 1: The Scrum Guide

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

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.

According to the Scrum Guide, Scrum is a framework to generate value through adaptive solutions for complex problems. It is based on empiricism, self-organization, and collaboration. The other options are not accurate descriptions of Scrum, as they are either too rigid (such as a defined and predictive process or a complete methodology), too vague (such as a cookbook), or irrelevant (such as scientific management).

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

In Scrum, the Developers have the autonomy to manage their work and the Sprint Backlog. When an unexpected request comes in, even from someone as authoritative as the CEO, it should not be added directly to the Sprint Backlog without discussion. The correct approach is for the Developers to discuss the new item with the Product Owner and the rest of the Scrum Team to understand its impact on the current Sprint Goal and to collaboratively decide the best course of action12.

This is in line with the Scrum values of Courage, Focus, Commitment, Respect, and Openness. The team must have the courage to push back on changes that could disrupt their Sprint Goal, stay focused on their commitments, respect the agreed-upon process, and be open about the implications of introducing new work mid-Sprint1.

The Scrum Guide also states that once the Sprint begins, no one can force the Development Team to work on different requirements than those they forecasted for the Sprint1. If the CEO’s request is deemed important enough to warrant a change in the Sprint’s direction, it may lead to a negotiation of scope with the Product Owner or, in extreme cases, to the cancellation of the Sprint if the Sprint Goal becomes obsolete. However, these are decisions that should be made collaboratively by the entire Scrum Team, not unilaterally by any single member, regardless of their position in the company

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, in order to turn Product Backlog items into an Increment of potentially releasable product functionality, the Development Team should have all the skills needed.

References: Scrum Guide

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

According to the Scrum Guide1, the Sprint Planning meeting has a time-box of eight hours or less for a one-month Sprint. The Scrum Master ensures that the meeting is time-boxed and keeps the Scrum Team focused on the objective. If the Development Team cannot forecast how many Product Backlog items it can complete, it should still start the Sprint and work on the most likely items to meet the Sprint Goal. The Sprint Backlog can be updated throughout the Sprint as more is learned. The Scrum Master should also support the team to discuss the reasons for the lack of clarity in the Product Backlog items and how to prevent it from happening again in the next Sprint Retrospective.

References: Scrum Guide

The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. 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, a product Increment must be potentially releasable, but the decision to release it is up to the Product Owner.

The correct answer is B, because the Scrum Guide states that “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.” Therefore, new work or further decomposition of work can be added to the Sprint Backlog as soon as possible after they are identified by the Development Team.

According to the Scrum Guide, the purpose of a Sprint is to produce a valuable useful Increment that meets the Definition of Done and the Sprint Goal. This means that the Developers work on items from the Product Backlog that deliver value to the stakeholders and align with the product vision. The other option is not valid, as it implies that producing an Increment is not the purpose of a Sprint.

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

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

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 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, there is no such thing as a Release Sprint in Scrum. A Release Sprint implies that there are other Sprints that don’t produce a potentially releasable Increment, which violates the core principle of Scrum. Every Sprint should result in a “Done”, useable, and potentially releasable product Increment.

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, 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 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 of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition guides the Development Team in creating a “Done” Increment.

References: Scrum Guide

According to the Scrum Guide, management external to the Scrum Team is not involved in the Daily Scrum at all. The Daily Scrum is an internal event for the Development Team to inspect their progress toward the Sprint Goal and plan their work for the next 24 hours. The other options are not valid ways for management to be involved in the Daily Scrum, as they are either intrusive (such as giving an update or speaking on behalf of others) or unnecessary (such as being represented by the Product Owner or the Scrum Master).

According to the Scrum Guide1, each Sprint is a project with no more than a one-month horizon. The Sprint Goal gives guidance to why the Scrum Team is building an Increment. 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. Therefore, in the first Sprint, as in any other Sprint, the Development Team should develop at least one piece of functionality and create an increment of potentially releasable software. The other options are not consistent with Scrum values and principles.

References: Scrum Guide

A Sprint burndown chart shows an estimate of the total work remaining for the Sprint, as stated in 3: “A sprint burndown chart tracks work remaining in a sprint. It shows how much work remains at any given point during a sprint. It helps teams monitor whether they will finish all planned tasks by the end of a sprint.”

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

The correct answer is A, because the role of management in Scrum is to facilitate the Scrum Teams with insights and resources that help them improve. The Scrum Guide states that “the organization respects their self-organization by not telling them how they should do their work.” Therefore, management should support the Scrum Teams by providing them with an environment that fosters collaboration, learning, and innovation.

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 B. The Scrum Team includes skilled individuals who together have all the skills necessary to create value each Sprint. According to the Scrum Guide1, “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint.” This does not mean that every individual has all the skills, but rather that the team as a whole does. Cross-functionality enables the Scrum Team to deliver a potentially releasable Increment of “Done” product at the end of each Sprint, without depending on others outside the team.

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

The correct answer is A, because the Product Owner does not determine how many Product Backlog items the Development Team selects for a Sprint. 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.

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

References: Scrum Guide

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

References: Scrum Guide

The correct answers are A and B, because these are true about the Product Owner role. The Product Owner is one person, not a committee or a team, who is accountable for ordering the Product Backlog and maximizing the value of the product. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. … For the Product Owner to succeed, the entire organization must respect his or her decisions.”

According to the Scrum Guide, two actions that the Scrum Master should support in this scenario are forecasting the Product Backlog items that are most likely to meet the Sprint Goal and creating the Sprint Backlog, and discussing why this happened and what changes will make it less likely to recur during the next Sprint Retrospective. These actions are consistent with Scrum values and principles, such as empiricism, adaptation, and continuous improvement. The other options are not valid actions, as they are either wasteful (such as canceling the Sprint or continuing the Sprint Planning past its timebox) or ineffective (such as asking everyone to take more time to analyze the Product Backlog).

The best two answers are A and B. As a Scrum Team, prioritizing the list and working on them in order is a good technique to tackle the impediments. This way, the team can focus on the most urgent and important issues first and avoid being overwhelmed by the number of impediments. The Scrum Master discusses the impediments with the Scrum Team is also a helpful technique, as it allows the team to share their perspectives, identify the root causes, and come up with possible solutions. The Scrum Master can also coach the team on how to remove or prevent impediments in the future.

According to the Scrum Guide, the action that the Scrum Master should take when the Team decides that a Sprint Retrospective is unnecessary is to begin facilitating productive and useful Sprint Retrospectives. The Sprint Retrospective is an essential event for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Scrum Master is responsible for ensuring that this event takes place and that positive outcomes are achieved. The other options are not valid actions, as they either imply that the Scrum Master complies with or ignores the decision of the Team (such as complying with it, calling a meeting with senior management, or consulting with the Product Owner), which is not consistent with Scrum values and principles.

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. The topics that are appropriate for discussion are those that relate to how the team does its work, such as processes, tools, communication, collaboration, quality, etc. The value of work currently represented in the Product Backlog and arranging the Sprint Backlog for the next Sprint are not appropriate topics for discussion in a Sprint Retrospective, as they belong to the Sprint Review and Sprint Planning events respectively.

According to the Scrum Guide, Developers do meet with stakeholders, especially during the Sprint Review and Sprint Planning events. The Product Owner is the primary person who interacts with stakeholders, but Developers also need to communicate with them to understand their needs, expectations, and feedback. The Product Owner may also invite stakeholders to provide clarifications or inputs during the Sprint.

The correct answers are B and D, because the length of the Sprint should be chosen based on the level of uncertainty over the technology to be used and the risk of being disconnected from the stakeholders. 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. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid, complexity may rise, and risk may increase.”

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

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.

A cross-functional Development Team is one that includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software, as stated in the Scrum Guide1: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.”

According to the Scrum Guide1, 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. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Product Owner is part of the Scrum Team and should participate as a Scrum Team member in the Sprint Retrospective.

References: Scrum Guide

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. Therefore, two appropriate topics for discussion during a Sprint Retrospective are:

Identifying high priority process improvements for the next Sprint.

How the team collaborates.

The other options are not relevant or appropriate for the Sprint Retrospective.

References: Scrum Guide

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, every Scrum Team should have the competencies and skills needed to deliver an Increment in a 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 what every Scrum Team should have, as they either imply that the Developers work in silos or rely on external people (such as a lead developer or representatives from different departments).

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

The correct answer is B, because multiple Scrum Teams working on the same project do not have to have the same Sprint start date. 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.” Therefore, the synchronization of multiple Scrum Teams is based on their shared product goal and definition of ‘Done’, not on their Sprint start date.

According to the Scrum Guide, the Development Team is responsible for creating a “Done” Increment that meets the Definition of “Done”. User documentation is part of the Definition of “Done” in this scenario, so the Development Team must create it. The other options are not consistent with Scrum values and principles, such as self-organization, cross-functionality, and empiricism.

The correct answers are B, C, and D, because moving away from component teams toward feature teams may involve some challenges and trade-offs. Productivity may suffer when making this kind of move, as teams need to learn new skills, coordinate with other teams, and deal with legacy code. Getting support from the business side first helps, as they can provide the vision, value, and feedback for the features. Feature teams have less communication overhead, as they can deliver end-to-end functionality without depending on other teams.

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

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 Backlog1. The Scrum Master can help the Developers remove these impediments or find ways to overcome them2.

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 Goal1. 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 work1. 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 else2. The Developers are responsible for conducting and facilitating the Daily Scrum, not the Scrum Master1. 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 timebox2.

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

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 management2. The purpose of the Daily Scrum is to inspect and adapt the work of the Developers, not to report on individual activities or performance1. The focus of the Daily Scrum should be on the collective work and progress of the Developers as a self-organizing team2.

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]

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. Multiple Scrum Teams working on one product use one Product Backlog.

References: Scrum Guide, Nexus Guide

When many Development Teams are working on a single product, the definition of “Done” must be shared by all Development Teams and make their combined work potentially releasable, as stated in [4]: “When multiple teams work together on one product they must mutually define and comply with the same Definition of Done. This makes sure all Increments adhere to a consistent quality level.”

 According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner’s discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does. 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, an appropriate action for the Scrum Master to take if the Product Owner is struggling with ordering the Product Backlog is to offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.

References: Scrum Guide

According to the Scrum Guide1, the Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum optimizes the probability that the Developers will meet the Sprint Goal. Every day, the Developers should understand how they intend to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. If the frequency of the Daily Scrum were to be lowered to every two or three days, some key concerns would be:

Opportunities to inspect and adapt the Sprint Backlog are lost, which may result in wasted work or missed dependencies.

Impediments are raised and resolved more slowly, which may hinder the progress and quality of the work.

The Sprint plan may become inaccurate, as changes in requirements, risks, or priorities are not reflected in a timely manner.

The other options are not valid concerns, as they are not aligned with Scrum values and principles.

References: Scrum Guide

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 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 correct answers are B and E, because Scrum has no “tester” role and everyone in the Development Team is responsible for quality. 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. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness.”

According to the Scrum Guide1, the Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Scrum Master and Product Owner may attend as observers, but only if it is useful for the Developers.

References: Scrum Guide

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, the best description of an increment of working software is additional features in a usable state that complement those delivered in previous iterations.

References: Scrum Guide

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

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.