The Scrum Value most demonstrated when a team completes a task before moving on to the next one is Focus . In Scrum, the team is expected to focus on the work required to meet the Sprint Goal. Completing one task at a time shows that the team prioritizes their attention and energy on delivering work of high quality, avoiding multitasking and distractions.

According to the 2020 Scrum Guide , focus is one of the five Scrum Values, which include:

Commitment : Dedication to the goals of the team and the Sprint.

Focus : Concentrating on the work at hand to ensure maximum productivity and value.

Respect : Valuing each team member and their contributions.

Courage : Facing challenges and delivering value despite uncertainties.

Openness : Transparency in communication and progress.

Why the other options are incorrect:

A. Commitment: While commitment is important, the act of completing a task before moving to the next one primarily demonstrates focus rather than commitment to goals.

C. Respect: Respect refers to valuing team members and their contributions, not the practice of completing one task at a time.

D. Courage: Courage involves tackling difficult challenges or speaking up, but it is not directly related to task completion.

The Scrum Master is a servant leader , focused on enabling the Scrum Team to work effectively. By taking action to resolve the Developer's impediment (lack of hardware), the Scrum Master demonstrates leadership by facilitating the team’s progress and ensuring they can meet the Sprint Goal.

According to the 2020 Scrum Guide , the Scrum Master serves the Scrum Team by:

Removing Impediments : Resolving obstacles that block the team’s progress is a key responsibility of the Scrum Master.

Supporting Team Effectiveness : By addressing issues outside the team’s control, the Scrum Master ensures that the Developers can focus on their work.

Why the other options are incorrect:

A. Disciplinarian: A Scrum Master does not enforce rules or discipline team members. They lead by fostering collaboration and resolving issues, not by control.

B. Project Manager: Scrum Masters do not perform traditional project management tasks like resource allocation or task assignment. Their role is to serve and support the team rather than manage it.

C. Authoritarian: The Scrum Master is not an authoritarian leader. Their approach is grounded in servant leadership, enabling and empowering the team rather than commanding it.

Size (or an estimate) is a required attribute of a Product Backlog item (PBI). PBIs are sized to help the Scrum Team understand the effort required to complete them and to assist in planning and forecasting. The Developers assign the size or estimate during Product Backlog refinement or Sprint Planning.

According to the 2020 Scrum Guide , Product Backlog items:

Must be clearly expressed and ordered by priority to maximize value.

Should include estimates (or sizes) so the Developers can plan the work required to deliver them.

Why the other options are incorrect:

A. Assigned to: PBIs are not assigned to specific individuals. The Developers are self-organizing and collectively decide how to complete the work.

C. Due Date: Scrum does not use due dates for PBIs, as delivery is based on iterative progress and the Sprint Goal.

D. State: While PBIs may be tracked in terms of progress (e.g., "in progress" or "done"), "state" is not a required attribute.

Incremental process refers to building and delivering software in small, usable pieces (Increments). In Scrum, each Increment is a usable part of the product that adds value and meets the Definition of Done.

According to the 2020 Scrum Guide :

The Increment is a concrete step toward the Product Goal .

Increments allow for frequent inspection and adaptation while ensuring transparency of progress.

Why the other options are incorrect:

A. An iterative process: While Scrum is iterative, "iterative" describes repeated cycles of planning and improving, whereas "incremental" refers to delivering usable pieces of the product.

C. A lifecycle process: This is a generic term for any process involving software development and does not specifically describe building in pieces.

D. A release process: A release process focuses on deploying software, not the incremental building of usable Increments.

When a Scrum Master encounters resistance from outside the Scrum Team, their role is to act as a servant leader and coach , ensuring the organization's adoption of Scrum is effective. Resistance often stems from a lack of understanding or buy-in regarding the value of Scrum.

According to the 2020 Scrum Guide , the Scrum Master serves the organization in several ways, including:

Leading, training, and coaching the organization in its Scrum adoption.

Planning and advising Scrum implementations within the organization.

Helping employees and stakeholders understand and enact an empirical approach for complex work.

In this case, the Scrum Master collaborates with other Scrum Masters to amplify the effectiveness of Scrum across the organization. This collaboration is essential for addressing systemic challenges or resistance to Scrum.

Why the other options are incorrect:

A. Escalate to management to reprimand the resisters: Escalating and seeking reprimand is not aligned with the Scrum Master's role as a facilitator and coach. This approach could create conflict rather than resolve resistance.

B. Not intervene in the business of others: The Scrum Master’s role involves actively addressing impediments and resistance. Avoiding intervention undermines their responsibility to promote Scrum.

C. Create a status update meeting for all Scrum Masters to coordinate team dependencies: While collaboration among Scrum Masters is essential, "status update meetings" are not a Scrum practice, and coordination of dependencies is typically handled within Sprint Planning or during collaborative refinement sessions.

The Daily Scrum is the event where impediments to achieving the Sprint Goal are shared. It is a time-boxed event (15 minutes) held every day during the Sprint. During this event, the Developers inspect their progress toward the Sprint Goal and identify any blockers or impediments that need to be addressed.

According to the 2020 Scrum Guide :

The Developers use the Daily Scrum to inspect progress and adapt their plan to achieve the Sprint Goal.

Impediments are raised and addressed by the Scrum Master if they cannot be resolved by the team.

Why the other options are incorrect:

B. Sprint Planning: Sprint Planning is focused on creating the Sprint Goal and selecting Product Backlog items for the Sprint, not sharing impediments.

C. Sprint Retrospective: The Retrospective focuses on process improvements and team dynamics, not day-to-day impediments during the Sprint.

D. Sprint Review: The Sprint Review is about presenting the Increment and gathering feedback, not resolving impediments.

Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller, clearer, and more actionable items. This process ensures that the Product Backlog is well-organized, understood, and ready for the upcoming Sprint Planning. Refinement helps the Developers and Product Owner collaborate to add detail, order, and estimates to Product Backlog items.

According to the 2020 Scrum Guide :

Product Backlog refinement is an ongoing activity that occurs throughout the Sprint.

It is not a formal event, and its timing and structure are determined by the Scrum Team.

Refinement improves clarity and helps the team better understand upcoming work.

Why the other options are incorrect:

A. a recurring event in the middle of each Sprint: Product Backlog refinement is not a time-boxed event. It occurs continuously, as needed.

C. an opportunity for the Developers to estimate Product Backlog items: While estimation may occur during refinement, the primary purpose is breaking down and clarifying items, not solely estimation.

D. a pre-planning meeting to shorten the length of Sprint Planning: Product Backlog refinement is not a pre-planning meeting but an ongoing activity to prepare for future Sprints.

One of the key accountabilities of a Scrum Master is to improve the Scrum Team's effectiveness . This aligns with the Scrum Master's role as a servant leader who helps the team deliver value through better practices, collaboration, and adherence to Scrum principles.

According to the 2020 Scrum Guide , the Scrum Master is accountable for:

Establishing Scrum as defined in the Scrum Guide , helping everyone understand its theory and practices.

Improving the Scrum Team's effectiveness by enabling the team to self-manage, improve cross-functionality, and focus on delivering high-value Increments.

Removing impediments that hinder progress and supporting the team in achieving its Sprint Goals.

Why the other options are incorrect:

A. Set the budget: The Scrum Master does not manage budgets. Budgeting decisions are outside the scope of the Scrum framework.

B. Provide estimates: Developers are responsible for providing estimates during Product Backlog refinement and Sprint Planning.

D. Decide when to release the product: Decisions about releases are made collaboratively by the Product Owner , often based on business needs and stakeholder input.

The described scenario aligns with "Individuals and Interactions over Processes and Tools" , one of the four core Agile Values from the Agile Manifesto. This value emphasizes the importance of collaboration, communication, and teamwork over reliance on rigid processes or tools. Scrum encourages team members to work together closely to solve problems and deliver high-quality software.

Why the other options are incorrect:

A. Individuals and Interactions over Working Software: While this value mentions "Working Software," the scenario focuses on collaboration among team members, which relates more to prioritizing individuals and interactions.

C. Individuals and Interactions over Contract Negotiation: This value applies to collaboration with stakeholders and customers rather than collaboration within the team.

D. Individuals and Interactions over Customer Collaboration: While customer collaboration is essential, the scenario specifically highlights collaboration among team members.

If a Scrum Team becomes too large, the team should reorganize into multiple cohesive Scrum Teams that share the same Product Goal and Product Backlog . This approach ensures that all teams remain focused on delivering value while maintaining transparency and alignment.

According to the 2020 Scrum Guide :

The ideal size for a Scrum Team is small enough to remain nimble (typically 10 or fewer people).

When a Scrum Team becomes too large, it should form multiple smaller teams, all working from the same Product Backlog and pursuing the same Product Goal.

Why the other options are incorrect:

A. Split into sub-teams based on function: Scrum encourages cross-functional teams, so dividing based on function contradicts Scrum principles.

C. Divide into separate teams each with their own Product Owner: A single Product Owner should manage the Product Backlog to ensure alignment and avoid conflicting priorities.

D. Do nothing and focus on delivering a usable product Increment: Not addressing the issue of an oversized team can lead to inefficiencies and reduced team effectiveness.