Scrum Practice Questions, Discussions & Exam Topics by our Authors
When must the Product Owner participate in the Daily Scrum?
In Scrum, the Daily Scrum is primarily a meeting for the Developers to synchronize their work and plan for the next 24 hours. The Product Owner is not required to attend this meeting, as their primary role is not to manage the day-to-day development activities. However, there are some scenarios where their participation might be relevant.
Let’s break down each option:
A) When the Product Owner needs to represent the stakeholders' point of view to the Developers: This option is incorrect. The Daily Scrum is not the place for the Product Owner to present stakeholder perspectives. It is a meeting for the Developers to plan and discuss their tasks. If the Product Owner needs to share feedback or a stakeholder perspective, it should be in other meetings like Sprint Reviews or Product Backlog Refinements, not the Daily Scrum.
B) When there are impediments to discuss: This option is partially true, but not quite the best fit. While the Product Owner might be involved in resolving impediments related to the Product Backlog or external factors, the Daily Scrum is not the ideal time for deep discussions about impediments. Impediments are typically addressed outside of the Daily Scrum, with the Scrum Master ofte...
Author: Ava · Last updated May 20, 2026
What are three ways Scrum promotes self-management? (Choose three.)
Scrum promotes self-management by empowering the Scrum Team to take ownership of their work, make decisions, and collaborate effectively. Let’s break down the options and analyze which ones align with this concept:
A) By the Scrum Team deciding what work to do in a Sprint: This is one of the ways Scrum promotes self-management. The Scrum Team, during Sprint Planning, decides which Product Backlog items to commit to for the Sprint, and how to break them down and complete them. This autonomy encourages ownership and accountability, which are key aspects of self-management.
B) By being a lightweight framework: While it’s true that Scrum is a lightweight framework, this option doesn’t directly explain how it promotes self-management. Being lightweight allows teams to adapt and make their own decisions, but it’s not specific enough to be considered a direct promotion of self-management. It’s more about Scrum being flexible, not about encouraging self-management per se.
C) By having the Scrum Master protect the Scrum Team from interruptions: The Scrum Master protects the Scrum Team from external interruptions and distractions, which helps the team stay focused on their work. While this is important for maintaining productivity and flow, it doesn’t directl...
Author: Leah Davis · Last updated May 20, 2026
What is the typical size for a Scrum Team?
In Scrum, the size of a Scrum Team is important for ensuring the team can work effectively and efficiently. A Scrum Team is composed of three key roles: the Product Owner, the Scrum Master, and the Development Team. The Development Team should be large enough to handle the work but not so large that it becomes unwieldy.
Let’s evaluate each option:
A) 10 or fewer: While Scrum does recommend a team size that is manageable, this option doesn’t align perfectly with Scrum’s guidance. The recommendation isn’t to limit the team to exactly 10 or fewer; it’s more about finding an optimal size for effective collaboration. So, this option is not the best fit.
B) At least 7: This is incorrect. Scrum does not specify that a team must have at least 7 members. A Scrum Team can function with fewer members, especially if the scope of the work is smaller. This option is to...
Author: Nathan · Last updated May 20, 2026
Which are characteristics of the Daily Scrum? (Choose two.)
The Daily Scrum is a crucial Scrum event designed for the Development Team to inspect their progress towards the Sprint Goal and synchronize their work. Let's analyze the options to determine which characteristics align with the Daily Scrum:
A) Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog: This is true. The Daily Scrum’s primary purpose is to help the team inspect their progress towards the Sprint Goal. They review the work completed and make adjustments to the Sprint Backlog if necessary. This option is correct.
B) It is facilitated by the team lead: This is incorrect. The Daily Scrum is not facilitated by a "team lead" (a role that doesn't exist in Scrum). It is a self-organizing event where the Development Team members manage the meeting themselves. The Scrum Master may ensure the meeting happens but does not facilitate in the traditional sense. This option is rejected.
C) It is free form and designed to promote conversation: This is incorrect. While the Daily Scrum does promote communication, it is not free form. It is a structured meeting with a clear focus: each team member answers three key questions (what they did yesterday, what they plan to do today, and if there are any impediments). It is not designed for open-ended conversation.
D) It consists of ...
Author: Kai · Last updated May 20, 2026
When is it most appropriate for a Scrum Team to change the Definition of Done?
The Definition of Done (DoD) is a shared understanding within a Scrum Team of the conditions that must be met for a product increment to be considered complete. It is essential that the DoD evolves to ensure the Scrum Team maintains high-quality standards, continuous improvement, and alignment with the overall project goals.
Let's evaluate each option:
A) Prior to starting a new project
- Changing the DoD at this point could be valid, but it’s not a typical or natural moment for adjusting the DoD. The Scrum Team should already have a solid DoD established based on past projects, and starting a new project doesn’t inherently require a change to the DoD. This option is not the best because the team should already be equipped with a DoD that works for them.
B) During Product Backlog refinement
- Product Backlog refinement is where the team works to understand and clarify items in the backlog. While it is important to refine backlog items and ensure they are well-defined, this isn’t the most suitable moment to change the DoD. Changing the DoD during this process could lead to confusion, as refinement sessions focus on clarifying what needs to be done rather than defining when something is done.
C) During Sprint Planning
- Sprint Plannin...
Author: Ahmed97 · Last updated May 20, 2026
An Increment must be released to customers or users at the end of each Sprint.
In Scrum, the Increment must be released to customers or users at the end of each Sprint. This is one of the key principles of Scrum: delivering value regularly in the form of an Increment. The Increment refers to a potentially shippable product that is tested and integrated. However, it is not required that it must be immediately deployed to users or customers at the end of each Sprint — it just needs to be ready for release.
Now, let's break down each option:
A) True: This is partially true in the sense that the Increment must be ready for release. However, Scrum doesn’t enforce immediate deployment to users or customers. It’s about the product being in...
Author: Oscar · Last updated May 20, 2026
When does a Sprint conclude? (Choose the best answer.)
To determine when a Sprint concludes, we need to understand key Scrum principles that govern the end of a Sprint.
- A) When all Product Backlog items meet their Definition of Done: While it's important that Product Backlog items meet the Definition of Done, this is not the criterion for the end of a Sprint. A Sprint ends when the timebox is reached, not necessarily when all items meet the Definition of Done. Some items might be incomplete, but the Sprint still ends when the timebox is over.
- B) When the Sprint Retrospective is complete: The Sprint Retrospective is an important ceremony, but it is not the determining factor for the end of the Sprint. A Sprint ends when the timebox is over (usually 2-4 weeks), regardless of whether the retrospective has taken place. The Retrospective happens toward the end of the Sprint but doesn't define it...
Author: Noah · Last updated May 20, 2026
What factor should be considered when establishing the Sprint length?
When establishing the Sprint length, several factors should be considered to ensure that the team can effectively plan, execute, and deliver high-quality increments while being flexible enough to adapt to change.
Let's evaluate each option:
A) The frequency at which team formation can be changed
- While team formation may evolve over time, it is not directly related to determining Sprint length. The flexibility of team composition is important, but it doesn't inherently affect how long a Sprint should be. This factor is not the primary consideration for Sprint length.
B) The organization has mandated similar length sprints
- Organizational mandates regarding Sprint length may be a factor in ensuring consistency across multiple teams, but this is not a best practice in Scrum. The Scrum Guide encourages teams to select a Sprint length that works best for them based on their needs and goals, rather than being solely dictated by organizational mandates. This option is less ideal because it doesn’t prioritize team flexibility or effectiveness.
C) The organization's release schedule
- The organization's release schedule could influence the timing of when work needs to be completed, but it is not the primary factor in deciding Sprint length. Scrum emphasizes ...
Author: FlamePhoenix2025 · Last updated May 20, 2026
What tactic should a Scrum Team use to divide a group of 100 people into multiple Scrum Teams? (Choo...
To determine the best approach for dividing a group of 100 people into multiple Scrum Teams, we need to consider key Scrum principles, such as cross-functionality, self-organization, and collaboration.
- A) Ask the people to divide themselves into teams: While this may seem democratic, it is not ideal in this scenario because the people may not have the necessary context or experience to form teams that align with the overall goals of the project. It also doesn’t ensure that the teams will be cross-functional or balanced in terms of skills and capacity. Scrum teams should be formed deliberately to ensure effectiveness and alignment with the project's objectives.
- B) Ask the Product Owner to assign the people to teams: The Product Owner is responsible for the product vision and backlog, but they are not the person best suited to assign people to teams. The team formation should be a collaborative effort that takes into account the necessary skill sets and the ability to form self-organizi...
Author: NebulaEagle11 · Last updated May 20, 2026
Developers do not meet with stakeholders; only the Product Owner meets with stakeholders.
The statement in the question is "Developers do not meet with stakeholders; only the Product Owner meets with stakeholders." In Scrum, it’s important to understand the roles of the team and their interactions with stakeholders.
Let’s break this down:
A) True
- This would mean that only the Product Owner communicates with stakeholders and developers have no direct interaction with them. While it’s true that the Product Owner is primarily responsible for managing the Product Backlog and ensuring stakeholder needs are represented, Scrum does not strictly prohibit developers from interacting with stakeholders. Developers can and sometimes should interact with stakeholders to gather information, clarify requirements, and ensure their understanding of the product vision. Restricting communication between developers and stakeholders might hinder the team's ability to deliver the most valuable product. Therefore, this option is incorrect.
B) False
- The stat...
Author: Aarav · Last updated May 20, 2026
Who creates the Definition of Done? (Choose the best answer.)
The Definition of Done (DoD) is a crucial part of the Scrum framework that ensures that work is completed to a high standard and meets the agreed-upon criteria for completeness. Let’s evaluate the options provided:
A) The Scrum Team
- The Scrum Team as a whole is responsible for creating and updating the DoD. This includes collaboration between the Product Owner, Developers, and Scrum Master to ensure that the DoD reflects the team's quality standards, project needs, and any evolving requirements. The DoD is something that the whole team must agree upon to maintain consistency and quality across the increments. Therefore, this option is the best answer, as the entire team’s involvement ensures alignment and shared responsibility.
B) The Scrum Master
- The Scrum Master is responsible for ensuring the Scrum framework is understood and followed, but they are not directly responsible for creating the DoD. They might facilitate discussions around it and ensure it is clearly defined, but the actual creation of the DoD is a team effort. This option is not the best, as the Scrum Master facilitates but does not create the DoD alone.
C) The Product Owner
- The Product Owner...
Author: Ethan Smith · Last updated May 20, 2026
Which two things should the Scrum Team do during the first Sprint? (Choose two.)
In the first Sprint, the Scrum Team is focused on getting started with the project in a practical, hands-on manner. The main goals are to establish a working increment, learn about the product and its needs, and set up a solid foundation for future Sprints. Let’s evaluate the options:
A) Make up a plan for the rest of the project
- In Scrum, long-term planning is not a key focus. Instead, Scrum relies on adaptive planning through short iterations (Sprints). The first Sprint should not be about making a detailed plan for the entire project. Instead, it should focus on producing a working increment. This option is incorrect because it contradicts the Scrum approach of incremental, iterative planning.
B) Define the major product features and a release plan architecture
- While it’s important to understand the product vision and backlog, defining major product features and creating a release plan architecture are more long-term tasks that go beyond what’s expected in the first Sprint. In the first Sprint, the focus is on creating something tangible rather than over-architecting. This option is not ideal as it doesn’t align with the core idea of creating working software early.
C) Build at least one piece of valuable functionality
- This is a key focus for the first Sprint. One of the key Scrum principles is to deliver working increments early, so the team can start learning from real user feedback. Building a piece of valuable functionality allows the team to establish a starting point for the project and start delivering value to stakeholders right away. This option is correct, as ...
Author: Lucas · Last updated May 20, 2026
During the Sprint, the Scrum Master=E2=80=99s role is to do which two of the following: (Choose two....
The Scrum Master’s role during the Sprint focuses on helping the team to follow Scrum practices, facilitating the Scrum events, and coaching the team to be self-managing and continuously improving. Let’s evaluate the options based on these responsibilities:
- A) Ensure the Product Owner attends all Scrum events: While the Scrum Master can help the Product Owner understand the importance of attending Scrum events, it is not the Scrum Master’s responsibility to ensure the Product Owner’s attendance. The Scrum Master is more focused on supporting the Scrum Team and ensuring Scrum practices are followed. The Product Owner’s attendance is important, but not the primary responsibility of the Scrum Master.
- B) Facilitate inspection and adaptation opportunities as requested or needed: This is a key role of the Scrum Master. The Scrum Master ensures that the Scrum Team regularly inspects and adapts through events like the Daily Scrum, Sprint Review, and Sprint Retrospective. Facilitating these opportunities for reflection and improvement is part of the Scrum Master’s responsibility to foster a culture of continuous improvement.
- C) Assign tasks with the Scrum Team: In Scrum, the team is self-managing, meaning that team members collaboratively decide who will do what work. The Scrum Master does not assign tasks; instead, the Scrum Master helps the team understand their responsibilities, remove impedime...
Author: Aditya · Last updated May 20, 2026
Which three behaviors demonstrate that a Scrum Team is self-managing? (Choose three.)
To determine which three behaviors demonstrate that a Scrum Team is self-managing, we need to focus on Scrum’s core principle of self-management, which emphasizes that the team can organize itself to get work done without relying on external control.
- A) The Scrum Team has all the skills needed to create an increment: This is a characteristic of a well-formed Scrum Team, but it doesn’t directly demonstrate self-management. Having all necessary skills enables the team to deliver the product, but self-management is more about how the team organizes and handles work, not just its capabilities.
- B) Developers collaboratively selecting their own work during the Sprint: This behavior clearly demonstrates self-management. Self-managing teams take ownership of their work, make decisions together, and prioritize what they will work on, based on the needs of the Sprint and their skills. This allows the team to adapt as necessary, without external direction.
- C) The Developers create their own Sprint Backlog, reflecting all work that is part of the Definition of Done: This is also a key behavior of self-managing teams. Scrum Teams create and manage their own Sprint Backlog, ensuring they understand what needs to be done to meet the Sprint Goal. They make decisions about how to achieve the goal and the tasks required, ensur...
Author: Noah · Last updated May 20, 2026
Who determines how many Product Backlog items the Developers select for a Sprint? (=D0=A1hoose the b...
In Scrum, the decision about how many Product Backlog items the Developers select for a Sprint is determined by the Developers themselves. Here's the reasoning behind the selection:
Explanation:
1. The Scrum Master (A): The Scrum Master's role is to facilitate Scrum events and ensure that Scrum is being followed, but they do not directly determine the number of Product Backlog items that are selected for the Sprint. The Scrum Master supports the team, but not in making decisions about the scope of the Sprint.
2. The Product Owner (B): The Product Owner is responsible for maintaining and prioritizing the Product Backlog, but the Product Owner does not decide how many items the Developers will commit to. The Product Owner provides the necessary items for the Sprint, but it is the Developers who assess how much work they can take on.
3. The Developers (C): The Developers are the ones who determine how many items they can commit to completing in the upcoming Sprint, based on their capacity and the work required. This is because they have the expertise to assess how much work they can...
Author: Olivia Johnson · Last updated May 20, 2026
The Definition of Done serves which three purposes? (Choose three.)
The Definition of Done (DoD) is a crucial part of Scrum because it ensures a shared understanding of what it means for work to be complete. It plays an important role in maintaining consistency and transparency across the Scrum Team. Let’s evaluate each option:
Explanation:
1. Describe the purpose, objective, and timebox of each Scrum event (A):
- This is not related to the Definition of Done. The purpose, objective, and timebox of each Scrum event (such as Sprint Planning, Daily Scrum, Sprint Review, etc.) are defined separately in the Scrum Guide. The DoD focuses on the criteria for when work is considered complete, not the details of Scrum events.
2. Guide the Developers on how many Product Backlog items to select for the Sprint (B):
- The DoD does not guide how many Product Backlog items the Developers should select for the Sprint. The number of items selected is determined based on the team’s capacity, and this is not directly influenced by the DoD. The DoD is concerned with completeness, not the selection of items.
3. Describe the work that must be mostly done before the Sprint is allowed to end (C):
- This option is partially misleading. The DoD is concerned with ensuring that work is completely done before it is considered finished (according to the agreed-upon...
Author: Carlos Garcia · Last updated May 20, 2026
Who is responsible for collaboration with stakeholders? (Choose the best answer.)
In Scrum, collaboration with stakeholders is a key responsibility to ensure that the product is being developed in alignment with the needs and expectations of the business and customers. Let’s analyze the options:
- A) The Scrum Team: The Scrum Team is responsible for collaborating with stakeholders as a whole. While different members may have varying degrees of direct interaction with stakeholders, it’s the collective responsibility of the entire Scrum Team, including the Scrum Master and Product Owner, to ensure that communication with stakeholders is managed and that feedback is integrated into the work. This option recognizes the collaborative nature of Scrum, where team members are expected to engage with stakeholders regularly.
- B) The Project Manager: In Scrum, there is no role of a "Project Manager." Scrum replaces this role with the Scrum Master, who helps remove obstacles and facilitates the Scrum process but does not manage or control the project. The Scrum Team manages the work, and the Product Owner collaborates with stakeholders, rather than a Project Manager.
- C) The Team Manager: Scrum does not have a role called "Team Manager." The Scrum Team is self-managing and does not require a team manager to dictate how work is done or facilitate stakeholder collaboration. Th...
Author: Chloe · Last updated May 20, 2026
What enhances the transparency of an Increment? (Choose the best answer.)
To enhance the transparency of an Increment, the focus is on ensuring that the work done is clear and visible to all stakeholders, and it meets the quality criteria as defined by the team. Let’s analyze each option:
Explanation:
1. Doing all work needed to meet the Definition of Done (A): This is the most accurate answer. The Definition of Done (DoD) is a shared understanding of the quality and completion criteria that all work must meet before it is considered complete. When the Increment meets the Definition of Done, it ensures that the work is fully completed and of high quality, making it transparent to stakeholders and team members. This enhances transparency because everyone can clearly see what is done and what is not, without ambiguity. The DoD is key to the Increment's transparency.
2. Updating Sprint tasks properly in the electronic tracking tool (B): While updating tracking tools can provide information, it doesn't directly enhance the transparency of the Increment itself. Tracking tools might help manage work and provide a view of progress, but they don't necessarily guarantee that the Increment is fully completed or transparent. The tool might not reflect whether the work actually meets the Definition of Done or if it’s truly done to the necessary standard.
3. Keeping track of and estimating all undone work ...
Author: StarlightBear · Last updated May 20, 2026
When does a Developer become accountable for the value of a Product Backlog item selected for the Sp...
To answer when a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint, we need to focus on the responsibility of Developers in Scrum and how accountability for value is distributed in the Scrum framework.
Explanation:
1. During the Daily Scrum (A): The Daily Scrum is a daily meeting where the team inspects progress toward the Sprint Goal and plans for the next 24 hours. While it is important for the team to review progress, accountability for the value of the Product Backlog items is not specifically assigned during the Daily Scrum. This meeting is for tracking progress, not assigning responsibility for value.
2. Never. The entire Scrum Team is accountable for creating value every Sprint (B): This option emphasizes that the entire Scrum Team, including the Product Owner, Scrum Master, and Developers, shares responsibility for delivering value. While it’s true that the entire Scrum Team is accountable for delivering value, the specific accountability of individual Developers for the value of a selected Product Backlog item is established earlier in the process, especially during Sprint Planning. Therefore, while collective accountability exists, the Developer’s responsibility for value begins when they select ...
Author: RadiantJaguar56 · Last updated May 20, 2026
Who is responsible for the sizing of Product Backlog items?
To answer the question of who is responsible for the sizing of Product Backlog items, we need to understand the specific responsibilities outlined in Scrum.
Explanation:
1. The Developers after clarifying requirements with the Product Owner (A):
- This is the correct answer. In Scrum, the Developers are responsible for sizing the Product Backlog items. This happens during the backlog refinement (or grooming) process, where the team clarifies requirements with the Product Owner and then estimates or sizes the effort required to complete each item. The sizing is typically done using techniques like story points, ideal days, or other estimation methods, and it is the Developers' responsibility to provide this estimate based on their understanding and expertise.
2. The Product Owner with input from the Developer (B):
- While the Product Owner plays a key role in providing the requirements and priorities, they are not responsible for sizing the Product Backlog items. The Product Owner ensures the backlog is well-organized and clear, but the sizing of items is the responsibility of the Developers. The Product Owner provides input to the Developers by clarifying the item, but the final sizing decision is made by the Developers themselves.
3. The Developers, alone (C):
- This is partially correct but incomplete. The Dev...
Author: BlazingPhoenix22 · Last updated May 20, 2026
