Free and Premium Scrum PSPO-I Dumps Questions Answers

The Developers on the Scrum Team share accountability for the Sprint Backlog, which is a forecast of the work and the plan to deliver the Sprint Goal12. The Sprint Backlog is dynamic and can be updated by the Developers as more is learned during the Sprint34. The Developers are not individually accountable for the items in the Sprint Backlog, nor are they assigned by the Scrum Master or the Product Owner5.

Scrum does not require that the Product Owner must use any of the following items:

• Burndown chart: A burndown chart is a graphical representation of work left to do versus time. It can be used to track progress and forecast completion dates of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.
• Feature burn-up: A feature burn-up chart is a graphical representation of features completed versus time. It can be used to track progress and forecast scope changes of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.
• Critical Path Analysis: Critical Path Analysis is a project management technique that identifies the sequence of tasks that must be completed on time for a project or Sprint to finish on schedule. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.
• Project Gantt chart: A project Gantt chart is a graphical representation of tasks, dependencies, durations, and milestones of a project or Sprint. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.

Therefore, the correct answer is none of the above.

References:

• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 11, section “Product Backlog”
• [Professional Scrum Product Owner™ Training], page 8, section “Release Management”

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.

References:

• The Scrum Guide
• The Scrum Team
• Professional Scrum Product Owner™ I Certification

The Product Owner should not have the entire Product Backlog documented in detail before the first Sprint can start. This is because:

• The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
• The Product Owner collaborates with the Developers and the stakeholders to refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of detail and precision required for each Product Backlog item depends on its order, size, and complexity.
• The Product Owner does not need to have the entire Product Backlog documented in detail before the first Sprint can start, as this would imply a fixed and upfront plan that does not allow for feedback, learning, and adaptation. Instead, the Product Owner only needs to have enough items that are well understood and valuable for the Scrum Team to start working on them in the first Sprint.

References:

• [Scrum Guide], page 11, section “Product Backlog”
• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 10, section “Product Goal”
• [Scrum Guide], page 12, section “Product Backlog Refinement”

 An Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.1 An Increment is a concrete, tangible, and usable outcome of the work done by the Developers in a Sprint. It is not a plan, a mock-up, a design, or a roll-out plan, as these are not valuable or useful products in themselves. An Increment must meet the definition of “Done”, which means it must adhere to the quality standards agreed upon by the Scrum Team and the stakeholders.1 An Increment must also be potentially releasable, which means it must be in a state that it could be delivered to the customer or user if the Product Owner decides so.1

References:

• 1: The Scrum Guide2, page 14
• 2: The Scrum Guide

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 Goal1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment1. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal1. The Sprint Backlog can include any items that the Developers deem necessary to achieve the Sprint Goal, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum1.

References:

• The Scrum Guide, section 3.3. Sprint Backlog
• Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint
• Professional Scrum Product Owner I (PSPO I) Sample Questions, question 11

According to Scrum.org, when splitting a large group into multiple Scrum Teams, it can be beneficial to allow the people to self-organize into smaller teams12. This approach respects the principle of self-organization, which is a key aspect of Scrum12. It allows individuals to choose the team they feel they can contribute to most effectively12. However, it’s important to note that this process should be facilitated and guided to ensure a balanced distribution of skills and capabilities across the teams12.

The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:

• It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
• It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
• It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.

References:

• Scrum Guide 2020, page 10: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”
• Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ensuring that the Product Backlog is transparent, visible and understood.”
• Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.”
• Scrum Guide 2020, page 11: “Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.”
• Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”

The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:

• Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.
• Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.

Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.

References:

• Professional Scrum Product Owner™ Training, page 5, section “Product Value”
• Professional Scrum Product Owner™ Training, page 6, section “Product Vision”
• Professional Scrum Product Owner™ Training, page 7, section “Product Backlog Management”
• Professional Scrum Product Owner™ Training, page 8, section “Release Management”
• Professional Scrum Product Owner™ Training, page 9, section “Business Strategy”
• Professional Scrum Product Owner™ Training, page 10, section “Stakeholders & Customers”

Answer: False

Very Short Explanation: According to Scrum.org, the Product Owner is not required to create clear and unambiguous acceptance criteria for each item in the product’s backlog before it can be selected in Sprint Planning1. Acceptance Criteria is optional and is not prescribed by Scrum12. It can be valuable, but it’s not a must12. The Developers can inspect and adapt the Sprint Backlog in any way they see fit, in order to help meet the Sprint Goal2.

• The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
• Stakeholders are people external to the Scrum Team who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. Stakeholders provide valuable input, feedback, and insights to the Scrum Team regarding the product vision, goals, value proposition, requirements, features, functions, quality, usability, or market conditions.
• Collecting stakeholder feedback is one of the main purposes of the Sprint Review. Stakeholder feedback can help the Scrum Team to:

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review
• Stakeholders: https://www.agilealliance.org/glossary/stakeholders

• The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
• The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
• The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
• The responsibility of crafting the Sprint Goal is shared by both the Product Owner and the Developers. The Product Owner should come to Sprint Planning with a business objective in mind, based on their understanding of the product vision, goals, value proposition, stakeholder feedback, market conditions, or other relevant factors. The Product Owner should propose how this objective can be achieved by selecting some Product Backlog items that can deliver value to customers or users. The Developers should collaborate with the Product Owner to craft a clear and concise Sprint Goal that expresses what they want to accomplish as a team during this Sprint. The Developers should also ensure that they have enough capacity and skills to deliver on this Sprint Goal.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal
• Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
• Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
• Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning

Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.

References:

1: Non-functional requirement, Wikipedia, accessed on December 16, 2023

2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023

[3][3]: The Scrum Guide, November 2020, p. 6

4: The Scrum Guide, November 2020, p. 7

5: The Scrum Guide, November 2020, p. 13

 Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

A Sprint is a time-boxed period when a Scrum Team works to complete a set amount of work that delivers value to the customer1. A Sprint concludes when the time-box expires, regardless of whether all the tasks, Product Backlog items, or Definition of Done are completed or not23. The Product Owner has the authority to cancel a Sprint if they determine that the Sprint Goal is obsolete or the work done is no longer valuable1. Therefore, the Product Owner decides when enough has been delivered to meet the Sprint Goal, and the Sprint ends accordingly.

The Sprint Retrospective is an event for the Scrum Team to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness for the next Sprint2. Therefore, appropriate topics for discussion during a Sprint Retrospective are:

Identifying high priority process improvements for the next Sprint. The Scrum Team should identify the most important things that went well and the potential improvements, and create a plan for implementing some of them in the next Sprint[3][3]. This way, the Scrum Team can continuously improve their performance and deliver more value.

How the team collaborates. The Scrum Team should reflect on how they work together as a self-managing unit, and how they can enhance their skills, tools, and relationships4. This way, the Scrum Team can foster a culture of trust, respect, and collaboration.

The other options are not appropriate topics for discussion during a Sprint Retrospective, as they are either related to the Product Backlog or the Sprint Backlog, which are not the focus of the Sprint Retrospective. The order of items in the Product Backlog is the responsibility of the Product Owner, who manages the Product Backlog based on the value, risk, and dependencies of the items5. The Product Owner may seek input from the Scrum Team or the stakeholders, but the final decision is up to the Product Owner. Documenting acceptance criteria for items in the next Sprint is part of the Product Backlog refinement, which is an ongoing activity throughout the Sprint, not a specific event. The Scrum Team should collaborate on refining the Product Backlog items and adding more details, such as acceptance criteria, as they become more clear and ready for selection in a Sprint Planning.

References:

1: The Scrum Guide, November 2020, p. 14

2: The Scrum Guide, November 2020, p. 15

[3][3]: The Scrum Guide, November 2020, p. 15

4: Developing People and Teams, Scrum.org, accessed on December 16, 2023

5: The Scrum Guide, November 2020, p. 7

 The Scrum Guide, November 2020, p. 10

 The Scrum Guide, November 2020, p. 10

 Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

• The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
• An Increment is a concrete stepping stone toward the product vision. It 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 meets the Definition of Done and is usable.
• The Scrum Team is accountable for creating a valuable increment every Sprint, not just once or occasionally. This means that the Scrum Team must deliver a product functionality that provides value to the customers and users and contributes to the product goals and missions. The value of an increment can be measured by various factors, such as customer satisfaction, feedback, revenue, market share, or social impact.
• The Scrum Team is also accountable for creating a valuable increment every Sprint, not just any increment. This means that the Scrum Team must deliver a product functionality that meets the quality standards and expectations of the customers and users and complies with the Definition of Done. The quality of an increment can be measured by various factors, such as usability, reliability, performance, security, or maintainability.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Scrum Team: https://www.scrum.org/resources/what-is-a-scrum-team
• Increment: https://www.scrum.org/resources/what-is-an-increment

The Product Owner and the Scrum Master are essential roles in the Scrum Team. They have distinct accountabilities and responsibilities that contribute to the success of the product and the team. The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Scrum Master is responsible for promoting and supporting Scrum and the Scrum Team. Both roles need to be fully engaged and available to the Scrum Team throughout the Sprint.

 If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:

• Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
• The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
• The Product Owner is accountable for ensuring that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must collaborate with the Developers and provide clarifications, feedback, and guidance on what items are most important and valuable for the product.
• If the Product Backlog is not sufficiently clear at Sprint Planning, it means that there are items that are not well defined, ordered, or estimated. This may make it hard for the Developers to understand what they are supposed to build and why. It may also make it hard for them to estimate how much work they can do or how long it will take them to do it. This may result in a poor or inaccurate Sprint forecast that may affect the quality or value of the Increment.

Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.

References:

• [Scrum Guide], page 14, section “Sprint Planning”
• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 11, section “Product Backlog”

 The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. This is because:

• The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
• The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.
• The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that both parties are confident that the Increment will meet the intended value.

Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product development.

References:

• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 10, section “Definition of Done”
• [Scrum Guide], page 10, section “Increment”
• [Scrum Guide], page 10, section “Product Goal”

• A Product Owner is not the same thing as a traditional Project Manager. A Product Owner is a role in Scrum, a framework for developing, delivering, and sustaining complex products. A Project Manager is a role in traditional project management, a discipline for planning, executing, and controlling projects.
• A Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
• A Project Manager is accountable for delivering the project within the predefined scope, time, and cost constraints. The Project Manager is responsible for defining and managing the project plan, resources, risks, issues, and dependencies. The Project Manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.
• Some of the main differences between a Product Owner and a Project Manager are:

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
• Project Manager: https://www.pmi.org/about/learn-about-pmi/what-is-project-management

The reasons why it is important that there is only one Product Owner per product are:

• It is clear who is accountable for the ultimate value of the product. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
• It helps avoid barriers to effective communication and rapid decision-making. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog items based on value and impact.
• The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work.

Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders.

References:

• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 11, section “Product Backlog”
• [Scrum Guide], page 12, section “Product Backlog Refinement”
• [Scrum Guide], page 11, section “Product Backlog”
• [Scrum Guide], page 7, section “Developers”

• The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
• The purpose of a Sprint Review is to inspect the product Increment with the stakeholders and collect feedback on next steps. The Sprint Review is a collaborative and interactive session where the Scrum Team and the stakeholders discuss what was done in the Sprint, what problems were encountered, what was learned, and what can be improved or changed. The Sprint Review also provides input for updating the Product Backlog to maximize value in future Sprints.
• The other options are not valid or relevant purposes of a Sprint Review. They are either too vague, unrelated, or incorrect. They are:

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review

 A Sprint may be cancelled when the Sprint Goal becomes obsolete. This is because:

• The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
• The Sprint is a container for all other Scrum events and activities. It is a time-box of one month or less during which a “Done” Increment is created that meets the Sprint Goal. The Sprint has a consistent duration throughout a development effort and only changes duration between Sprints.
• A Sprint may be cancelled before it is over by the Product Owner if they determine that the Sprint Goal is no longer valid or valuable. This may happen due to various reasons, such as a significant change in the market, technology, business direction, or customer needs.
• A cancelled Sprint should be rare and exceptional. It implies a waste of time and resources that could have been spent on delivering value. It also disrupts the rhythm and flow of the Scrum Team and the stakeholders.
• When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed and potentially released. Any incomplete Product Backlog items are re-estimated and put back on the Product Backlog. The Scrum Team then plans for a new Sprint.

Other options, such as when the Developers determine the product plan is infeasible, when it becomes clear that not everything will be finished by the end of the Sprint, or when the sales department has an important new opportunity, are not valid reasons for cancelling a Sprint. They may reflect a misunderstanding of what a Sprint Goal is or how Scrum works.

References:

• [Scrum Guide], page 15, section “Sprint Goal”
• [Scrum Guide], page 9, section “Sprint”
• [Scrum Guide], page 16, section “Cancelling a Sprint”

If the Developers find out during the Sprint that they are not likely to build everything they forecast, the best response from the Product Owner is to re-work the selected Product Backlog items with the Developers to meet the Sprint Goal. This is because:

• The Sprint Goal is a short-term objective that provides guidance and focus to the Scrum Team throughout the Sprint. It is a flexible and negotiable commitment that can be adjusted as more is learned throughout the Sprint.
• The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
• The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.
• If the Developers find out during the Sprint that they are not likely to build everything they forecast, it means that there is a gap between their initial plan and their actual progress. This may happen due to various reasons, such as new insights, changing requirements, technical challenges, or unforeseen circumstances.
• In this situation, the Product Owner should work with the Developers to re-work the selected Product Backlog items to meet the Sprint Goal. This may involve adding, removing, or modifying some items, as long as they still support the Sprint Goal and deliver value. The Product Owner should also communicate any changes or impacts to the stakeholders and customers as appropriate.

Other options, such as skipping Product Backlog refinement activities, informing management that more Developers are needed, changing the Sprint Goal, or canceling the Sprint, are not valid responses from the Product Owner as they do not reflect what should happen in Scrum or how to deal with uncertainty and complexity.

References:

• [Scrum Guide], page 15, section “Sprint Goal”
• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 10, section “Definition of Done”
• [Scrum Guide], page 10, section “Increment”
• [Scrum Guide], page 10, section “Product Goal”

If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.

The Sprint Retrospective is one of the five events defined by Scrum. It is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to adapt the way of working so that it becomes more effective and enjoyable. The other options are not required by Scrum, but may be useful practices depending on the context. Developers do not have to stand up at the Daily Scrum, they can choose any format that works for them. A Sprint Burndown Chart is a common way to visualize the remaining work in a Sprint, but it is not mandated by Scrum. Release Planning is a topic that falls under the broader competency of Managing Products with Agility, but it is not a prescribed event in Scrum.

References:

• The Scrum Guide
• Understanding and Applying the Scrum Framework
• Professional Scrum Product Owner™ I Certification

Explanation: The Product Owner is responsible for managing and refining the Product Backlog, which is the single source of truth for the plan of the product development. The Product Backlog is a living artifact that changes as the product and the market evolve. The Product Owner updates the Product Backlog continuously based on feedback, learning, and stakeholder needs. There is no separate project plan document in Scrum.

References:

• [Scrum Guide], section 3.1: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”
• [Professional Scrum Product Owner], chapter 5: “The Product Backlog represents everything necessary to develop and launch a successful product.”
• [What is a Product Backlog?]: “The Product Backlog is a list of all things that need to be done within the project.”

 Management that is external to the Scrum Team is not involved in the Daily Scrum because:

• The Daily Scrum is an event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. It is not a status meeting or a reporting session for managers or other stakeholders.
• The presence of external managers may hinder the self-organization, collaboration, and transparency of the Developers. It may also create pressure, interference, or distraction for the team.
• The Scrum Master is responsible for ensuring that the Daily Scrum is held and that only the Developers participate. The Product Owner and other stakeholders may attend as observers, but only if the Developers find it useful.

References:

• Scrum Guide 2020, page 12: “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.”
• Scrum Guide 2020, page 13: “The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. This creates focus and improves self-management.”
• Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.”

 It is not true that the Product Owner must write all of the Product Backlog items (e.g. user stories, requirements, etc.) on the Product Backlog before handing them over to the Scrum Team. This is because:

• The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is never complete and constantly changes to reflect the needs and desires of the customers, users, and stakeholders.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
• The Product Owner is also accountable for managing the Product Backlog items effectively. They must ensure that they are transparent, visible, and understood by everyone who needs to work on them. They must also collaborate with the Developers and stakeholders to refine, order, and prioritize them based on value and impact.
• The Product Owner does not need to write all of the Product Backlog items by themselves or before handing them over to the Scrum Team. They can involve others in creating or contributing to them, such as customers, users, stakeholders, or Developers. They can also add or modify them at any time during the product development process, as long as they are clear and ready for selection in Sprint Planning.

References:

• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 11, section “Product Backlog”
• [Scrum Guide], page 10, section “Product Goal”
• [Scrum Guide], page 12, section “Product Backlog Refinement”
• [Scrum Guide], page 14, section “Sprint Planning”

• Customer satisfaction is a measure of how well a product or service meets or exceeds the expectations and needs of the customers. It is an important indicator of the value and quality of a product or service, and it can affect the loyalty, retention, and profitability of the customers.
• Customer satisfaction should be measured frequently, as it can change over time depending on various factors, such as the market conditions, the customer feedback, the product updates, the competitor actions, and the customer behavior. Measuring customer satisfaction frequently can help the Product Owner and the Scrum Team to inspect and adapt their product vision, strategy, roadmap, backlog, and increments based on the customer needs and preferences. It can also help them to identify and resolve any issues or gaps that may affect the customer satisfaction and value delivery.
• Measuring customer satisfaction quarterly, daily, or annually is not optimal, as it may not reflect the current state of the customer satisfaction and may miss some opportunities or risks that may arise in between the measurement intervals. Quarterly measurement may be too slow to respond to the fast-changing market and customer demands. Daily measurement may be too noisy and costly to collect and analyze. Annual measurement may be too outdated and irrelevant to inform the product decisions.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Customer Satisfaction: https://www.agilealliance.org/glossary/customer-satisfaction/

The work to make sure Product Backlog items conform to the Definition of Done is done by the Developers. This is because:

• The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
• The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what “Done” means for any Product Backlog item that is selected for a Sprint.
• The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.

Other options, such as the Product Owner, the Quality Assurance Team, the Scrum Team, or the Scrum Master, are not responsible for making sure Product Backlog items conform to the Definition of Done. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a “Done” Increment.

References:

• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 10, section “Definition of Done”
• [Scrum Guide], page 7, section “The Scrum Team”

The Scrum Team is accountable for creating a valuable increment every Sprint. The Increment is the sum of all Product Backlog items Done during a Sprint and the value of all the previous Increments. The entire Scrum Team is accountable for creating a valuable and useful Increment every Sprint1. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team1. The Developers are responsible for creating a Done Increment that meets the Sprint Goal1. The Scrum Master is responsible for establishing Scrum as defined in the Scrum Guide and helping everyone understand Scrum theory, practices, rules, and values1. References:

• Scrum Guide
• What is an Increment and how Does it Connect with the other Elements of Scrum?
• The Professional Product Owner

• The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
• The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
• The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning

The Daily Scrum is held at the same time and same place because:

• The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
• The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
• The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.

References:

• Scrum Guide 2020, page 12: “The Daily Scrum is held at the same time and place each day to reduce complexity.”
• Scrum Guide 2020, page 12: “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.”
• Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.”

Correct Answer: D. Never. The entire Scrum Team is accountable for creating value every Sprint.

Explanation: According to the Scrum Guide, the Scrum Team consists of one Product Owner, one Scrum Master, and Developers. The Scrum Team is responsible for all product-related activities, including delivering a valuable, usable product increment every Sprint. The Product Owner is accountable for maximizing the value of the product and the work of the Developers. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog; instilling quality by adhering to a Definition of Done; and adapting their plan each day toward the Sprint Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team’s progress.

Therefore, the Developers are not individually accountable for the value of a Product Backlog item selected for the Sprint, but collectively accountable as part of the Scrum Team. The value of a Product Backlog item is determined by the Product Owner, who orders the Product Backlog items based on stakeholder needs and feedback. The Developers collaborate with the Product Owner to understand the value and requirements of each Product Backlog item and deliver a potentially releasable product increment that meets the Definition of Done and the Sprint Goal.

References:

• [Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
• Accountabilities in Scrum | Scrum.org: “Scrum has three accountabilities, each with a different focus : Product Owner (green figure) The "What". With a focus on Value, time to market, return on investment and Total Cost of Ownership (TCO). Developers (red figures) The "How". Focus on building something that is Done – that the increment is useable and potentially releasable.”
• What is a Developer in Scrum? | Scrum.org: “The specific skills needed by the Developers are often broad and will vary based on the type of work they are doing. 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”

• The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
• The Product Owner is accountable for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
• The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
• All planned work for the Product done by the Scrum Team must originate from the Product Backlog. The Scrum Team does not work on anything that is not in the Product Backlog. The Scrum Team does not add or remove anything from the Product Backlog without consulting with the Product Owner. The Scrum Team does not accept or implement any requests or changes that are not in the Product Backlog. The Scrum Team does not create any other artifacts or documents that are not derived from or related to the Product Backlog.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog
• Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
• Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum

A sprint review is a collaborative event where the Scrum Team and stakeholders inspect the outcome of a Sprint and determine future adaptations12. It is not a mechanism to control, reward, or punish the Developers, nor is it just a demo of the work done.

The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3]. The Product Owner does not have the authority to tell the Developers how much work they should do, as this would violate the principle of self-management4.

References:

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10

[3][3]: The Scrum Guide, November 2020, p. 6

4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

• In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.
• Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities. Therefore, a Product Owner with multiple teams working on one product should not maintain separate Product Backlogs for each team.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
• In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Nexus: [1]
• LeSS: [2]
• SAFe: [3]
• Scrum of Scrums: [4]

The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. This is because:

• Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
• The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
• The Developers are also accountable for creating a plan for how they will deliver the selected Product Backlog items as a “Done” Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their work.
• The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their forecast of what work they can do and have a clear direction for the first few days of the Sprint.

Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the Developers’ understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast.

References:

• [Scrum Guide], page 14, section “Sprint Planning”
• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 15, section “Sprint Backlog”
• [Scrum Guide], page 14, section “Sprint Planning”

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "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 Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.

References:

• 1: The Scrum Guide2, page 15
• 2: The Scrum Guide

The ideal time for refinement to take place and who should participate are the Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work, and the Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection. This is because:

• Product Backlog refinement is the act of adding detail, estimates, and order to Product Backlog items. It is an ongoing and collaborative process that involves the whole Scrum Team.
• The Scrum Team should refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of time spent on refinement usually varies from one Scrum Team to another, but it is recommended not to exceed 10% of the capacity of the Developers.
• The Scrum Team may also use a Sprint to refine the Product Backlog if they have not been able to do so in previous Sprints. This may happen when the product is new or complex, or when there is a significant change in the product vision or direction. However, this should be an exception rather than a rule, as it may delay the delivery of value and feedback.

Other options, such as business analysts doing the refinement work for the Scrum Team, the Product Owner doing the refinement alone in Sprint 0 or between Sprints, or handing off the ownership of the Product Backlog to someone else, are not consistent with the principles and values of Scrum. They may lead to misunderstandings, misalignment, or loss of ownership and accountability.

References:

• [Scrum Guide], page 11, section “Product Backlog”
• [Scrum Guide], page 12, section “Product Backlog Refinement”
• [Professional Scrum Product Owner™ Training], page 7, section “Product Backlog Management”
• [Professional Scrum Product Owner™ Training], page 8, section “Release Management”
• [Professional Scrum Product Owner™ Training], page 9, section “Business Strategy”

During the Sprint Review, the stakeholder’s role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:

• The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration. The stakeholders are invited to attend the Sprint Review as observers, participants, or customers, and they can share their opinions, ideas, or requests regarding the product and its features, functionality, quality, value, etc.
• The ordering of the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions. The Product Owner may consider the feedback and suggestions from the stakeholders, as well as other factors such as dependencies, risks, costs, etc., when ordering the Product Backlog. However, they are not obliged to follow or implement them.
• The Product Backlog is not a fixed or final list of requirements, but rather an emergent and dynamic artifact that represents all the possible changes to the product. The Product Owner is accountable for effective Product Backlog management, which includes refining, communicating, and optimizing the Product Backlog items. The Product Owner may update the Product Backlog at any time, not only during the Sprint Review.

References:

• Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner.”
• Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ordering Product Backlog items; and ensuring that the Product Backlog is transparent, visible and understood.”
• Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”

 New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:

• It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.
• It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.
• It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.

References:

• Scrum Guide 2020, page 6: “Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.”
• Scrum Guide 2020, page 6: “The Developers are accountable for … organizing and managing their work.”
• Scrum Guide 2020, page 10: “The Sprint Goal is a single objective for the Sprint.”
• Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
• Scrum Guide 2020, page 14: “The Sprint Backlog is composed of … all of the work needed to deliver a product Increment that meets the Definition of Done.”
• Scrum Guide 2020, page 14: “The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned.”

The Developers are the ones who are accountable for tracking the remaining work toward the Sprint Goal. The Developers are self-managing and decide how much work they can do in a Sprint1. They also create and update the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers use the Daily Scrum to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. The Product Owner, the Scrum Master, and the Project Manager (if any) do not have the accountability for tracking the remaining work toward the Sprint Goal, as this is the responsibility of the Developers.

References:

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10

[3][3]: The Scrum Guide, November 2020, p. 11

The Scrum values are commitment, focus, openness, respect, and courage1. These values are embodied by the Scrum Team, which is a self-managing unit that organizes its own work and delivers a valuable product2. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers[3][3]. The best way to create Scrum Teams is to respect the self-management and empowerment of the people who will do the work, and let them decide how to organize themselves into Scrum Teams. This can be done by bringing all the people together and letting them form Scrum Teams based on their skills, interests, and alignment with the product vision4. Alternatively, existing teams can propose how they would like to reorganize themselves into Scrum Teams, based on their feedback and experience5. These ways of creating Scrum Teams are consistent with the Scrum values, as they foster commitment, focus, openness, respect, and courage among the team members and stakeholders. The other options are not consistent with the Scrum values, as they involve managers or the Chief Product Owner imposing their decisions on the team members, which undermines their self-management and empowerment, and creates a lack of trust and collaboration.

References:

1: The Scrum Guide, November 2020, p. 4

2: The Scrum Guide, November 2020, p. 5

[3][3]: The Scrum Guide, November 2020, p. 6

4: Managing Products with Agility, Scrum.org, accessed on December 16, 2023

5: Developing People and Teams, Scrum.org, accessed on December 16, 2023

The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that "The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done."1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

References:

• 1: The Scrum Guide2, page 14
• 2: The Scrum Guide

 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

• The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
• The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
• The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.
• The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

References:

• [Scrum Guide], page 17, section “Sprint Review”
• [Scrum Guide], page 9, section “Sprint”
• [Scrum Guide], page 9, section “Timeboxing Scrum Events”

In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing themselves into teams because:

• It respects the self-organization and empowerment of the people. The people are the ones who have the knowledge, skills, and experience to create and deliver the product. They are also the ones who will work together as Scrum Teams, collaborating and coordinating their efforts. Therefore, they should have the autonomy and authority to decide how to form their teams, based on their preferences, interests, and capabilities.
• It supports the alignment and coherence of the Scrum Teams. The people should have a clear and shared understanding of the product, the product vision, and the rules of the Scrum framework before forming their teams. This can help them to align their goals and missions, to ensure that they are working on the same product and towards the same vision. It can also help them to follow the same principles and practices of Scrum, to ensure that they are working effectively and consistently.
• It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a way that maximizes their collaboration and synergy. This can mean choosing team members that complement each other’s skills and strengths, that have good rapport and trust, that can communicate and coordinate well, and that can deliver a valuable Increment each Sprint.

References:

• Scrum Guide 2020, page 5: “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint.”
• Scrum Guide 2020, page 5: “Scrum Teams are self-managing, meaning they internally decide who does what, when, and how.”
• Scrum Guide 2020, page 9: “Multiple Scrum Teams working together on a product use one Product Backlog.”
• Scrum Guide 2020, page 9: “The Product Owner is one person, not a committee.”

• Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as “tester”, “analyst”, “designer”, or “architect”.
• The Developers are the people in the Scrum Team who are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
• The Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.
• The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.
• The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
• Quality: https://www.scrum.org/resources/blog/quality-scrum-value