PSM-I Professional Scrum Master I Questions and Answers

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

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.

A Product Backlog item is considered complete when it meets the Definition of Done, as stated in [5]: “When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.”

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.

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

References: Scrum Guide

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.

Architecture and infrastructure are handled in Scrum by implementing them along with functional development of the product, and by adding them to the Product Backlog and addressing them in early Sprints, while always requiring at least some business functionality, no matter how small, as stated in [2]: “Scrum does not distinguish between developing functionality or architecture. They are developed together, as they are both important and support each other. Architecture is not a separate phase; it is part of the product development. Architecture is added to the Product Backlog as any other feature or functionality.”

The correct answer is B. To present the Scrum Teams with insights and resources that help them improve. According to the Scrum Guide1, “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 collaboration2. 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 Team3. Management’s function in Scrum is to enable and empower the Scrum Team to deliver value and continuously improve.

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

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.

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.

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

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

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

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

References: Scrum Guide

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

The correct answer is C, because a Development Team should deliver an increment of working software that is “done” by the end of a Sprint. The Scrum Guide states that “the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. 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’.”

According to the Scrum Guide1, Scrum promotes self-organization by giving autonomy and empowerment to the Developers who decide how to do their work within a Sprint. The Developers have no titles other than Developer, regardless of their specialization or skills. Scrum is a lightweight framework that minimizes prescription and maximizes flexibility and adaptability.

References: Scrum Guide

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. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The length of a Sprint should be short enough to keep the business risk acceptable to the Product Owner, short enough to be able to synchronize the development work with other business events, and no more than one calendar month.

References: Scrum Guide

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 Guide, two intended outcomes of the Daily Scrum are identification of impediments that may prevent the Developers from achieving the Sprint Goal and a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal. These outcomes help the Developers to inspect their progress, plan their work, and collaborate effectively. 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 a status report or an update of completed tasks).

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

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 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 Product Owner should know the most about the progress toward a business objective or a release, as stated in the Scrum Guide: “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.”

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 timebox for the Sprint Review is four hours for a one-month Sprint, as stated in [4]: “The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; additionally, they discuss any changes to scope or budget or potential value. The entire group then collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is a working session and attendees should inspect based on facts. A Sprint Review is held at the end of every Sprint for a maximum duration of four hours for a one-month Sprint.”

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.

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

According to the Scrum Guide, three behaviors that demonstrate that a team is self-organizing are creating their own sprint backlog, having all the skills needed to create a releasable Increment, and collaboratively selecting their own work during the Sprint. The other options are not behaviors that demonstrate self-organization, as they are either contrary to Scrum values and principles (such as stakeholders walking in at the Daily Scrum or working within functional boundaries) or unnecessary for self-organization (such as the Product Owner not being at Sprint Retrospectives or the Development Team inviting external people to the Sprint Planning).

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

• What did I do yesterday that helped meet our Sprint Goal?
• What will I do today to help meet our Sprint Goal?
• Do I see any impediment that prevents me or our Development Team from meeting our Sprint Goal?

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

References: Scrum Guide

According to the Scrum 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, during each Daily Scrum, each Developer answers three questions:

• What did I do yesterday that helped meet our Sprint Goal?
• What will I do today to help meet our Sprint Goal?
• Do I see any impediment that prevents me or our Development Team from meeting our Sprint Goal?

The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward achieving their Sprint Goal and producing a usable Increment. The other options are not relevant or appropriate for the Daily Scrum.

References: Scrum Guide

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

References: Scrum Guide

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.

According to the Scrum Guide, a Sprint concludes when the Sprint Retrospective is complete. This is the last event of the Sprint cycle, where the Scrum Team inspects itself and creates a plan for improvements. The other options are not valid indicators of the conclusion of a Sprint, as they are either irrelevant (such as the Product Owner deciding enough has been delivered) or incomplete (such as all tasks or Product Backlog items being done).

The correct answer is C, because if burndown charts are used to visualize progress, they track work remaining across time. A burndown chart is a graphical representation of the amount of work left to do versus the time available. It helps the Scrum Team monitor and forecast the progress toward the Sprint Goal.

According to the Scrum Guide, 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 team relations, Definition of Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product Backlog in the Sprint Review).

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

References: Scrum Guide

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

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

The correct answer is A, because a Sprint Retrospective should be held at the end of each Sprint. The Scrum Guide states that “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 Scrum Master should be concerned about the ability of the Development Teams to produce integrated Increments, as this is one of the goals of Scrum. The Scrum Master should also encourage the Development Teams to figure out a solution for themselves, as this fosters self-management and collaboration. The other options are not relevant or important for the Scrum Master in this situation.

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

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. For the purpose of transparency, when does Scrum say a new increment of working software must be available? At the end of every Sprint.

References: Scrum Guide

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

According to the Scrum Guide, the Sprint Backlog is the Developers’ plan for the Sprint, as it contains all the Product Backlog items selected for the Sprint and a plan for delivering them. The other options are not valid descriptions of the Sprint Backlog, as they are either incorrect (such as having a designated owner, being ordered by the Product Owner, or being a complete list of all work) or unnecessary (such as estimating each task in hours).

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

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

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.

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

The correct answer is D, because 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.

The correct answer is C. The Scrum Team creates the Definition of Done. According to the Scrum Guide1, “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 Master2. The Scrum Team collaborates to create and update the Definition of Done as needed, based on the product and organizational standards3. The Definition of Done is not imposed by any external authority or individual.

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

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

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 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, 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 correct answer is C, because the Scrum Guide states that “the Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.” Therefore, enough work should be defined during the Sprint Planning event so that the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.