TheSprint Reviewis heldonce at the end of every Sprint. It is a time-boxed event where the Scrum Team and stakeholders collaborate to inspect the Increment, review progress toward the Product Goal, and adapt the Product Backlog as needed.

According to the2020 Scrum Guide:

The purpose of the Sprint Review is to discuss what was completed during the Sprint and what could be done next to optimize value delivery.

It occursonce at the end of every Sprint, ensuring transparency and stakeholder involvement.

Why the other options are incorrect:

B. One in the middle and one at the end of every Sprint:The Sprint Review is not conducted multiple times within a Sprint.

C. Once at the beginning of the Sprint:The Sprint Review is held at the end of the Sprint, not the beginning.

D. Daily:The Sprint Review is not a daily event. TheDaily Scrumoccurs daily.

The Scrum Master serves not only theScrum Teambut also thelarger organizationby ensuring that Scrum is understood and enacted effectively. This aligns with the Scrum Master’s role as aservant leaderand a facilitator of organizational agility.

According to the2020 Scrum Guide, the Scrum Master serves:

The Scrum Team: By coaching team members, removing impediments, and ensuring Scrum events are productive and timeboxed.

The Product Owner: By helping with effective Product Backlog management and stakeholder collaboration.

The Organization: By leading Scrum adoption, coaching employees and stakeholders, and removing systemic barriers.

Why the other options are incorrect:

A. The Scrum Team only:While serving the Scrum Team is a key part of the Scrum Master’s role, they also serve the organization and the Product Owner.

B. The management:The Scrum Master works with management but does not exclusively serve them. Their focus is on enabling Scrum practices across the organization.

C. No one:This is incorrect as the Scrum Master’s role is fundamentally about serving and supporting others.

Scrumis a lightweight framework designed to help teams and organizations addresscomplex problemsand deliver value in an adaptive manner. It is based on the principles of empiricism (transparency, inspection, and adaptation) and is widely used for developing, delivering, and sustaining products in a flexible and iterative way.

According to the2020 Scrum Guide, Scrum is:

A lightweight framework that helps people, teams, and organizationsgenerate valuethroughadaptive solutionsfor complex problems.

Defined by roles, events, artifacts, and rules that are intentionally simple yet highly effective.

Why the other options are incorrect:

A. Kanban:Kanban is a method for visualizing work and improving flow, but it is not a framework specifically designed for solving complex problems like Scrum.

C. Agile:Agile is a broader philosophy or mindset that includes various frameworks (such as Scrum, Kanban, etc.), but Scrum itself is a specific framework.

D. Waterfall:Waterfall is a traditional, sequential approach to project management that lacks the flexibility and adaptiveness of Scrum.

In theScrum framework, the three defined accountabilities are:

Product Owner– Responsible for maximizing the value of the product by managing the Product Backlog.

Scrum Master– Ensures that Scrum is understood and enacted effectively, removes impediments, and serves the Scrum Team and organization.

Developers– Responsible for delivering a "Done" Increment that meets the Sprint Goal.

There is no role forLead Developer,Project Manager, orBusiness Analystin Scrum. Scrum promotes self-management, cross-functional teams, and does not include traditional hierarchical roles.

Why the other options are incorrect:

A. Lead Developer:Scrum does not have a Lead Developer role or accountability.

B. Project Manager:Scrum does not include a Project Manager role as tasks and responsibilities are distributed among the Scrum Team.

D. Business Analyst:While the Product Owner may perform some business analysis tasks, there is no separate role for a Business Analyst in Scrum.

TheScrum Mastershouldcoach the Scrum Teamto understand the importance of theSprint Retrospective. This event is essential for inspecting and adapting processes, tools, and team dynamics, enabling continuous improvement in future Sprints.

According to the2020 Scrum Guide:

TheSprint Retrospectiveis a key event where the Scrum Team reflects on their performance and identifies actionable improvements.

It promotes collaboration, accountability, and self-management, all of which are crucial in Scrum.

Why the other options are incorrect:

B. Let the Developers decide:The Sprint Retrospective is a mandatory event for the Scrum Team, and the Developers cannot decide to skip it.

C. Escalate to the Product Owner:The Product Owner is not responsible for team dynamics or facilitating Scrum events. This is the Scrum Master’s responsibility.

D. Exclude those members of the Scrum Team from participating:Excluding team members would undermine team collaboration and the purpose of the event. Instead, the Scrum Master should address the underlying concerns and help the team recognize its value.

TheScrum Valuemost demonstrated when a team completes a task before moving on to the next one isFocus. 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 the2020 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.

TheScrum Mastershould coach the Developers byexplaining the intent of the Daily Scrum, which is toinspect progress toward the Sprint Goaland adapt the plan as needed. The Daily Scrum is not a status update meeting—it is a collaborative event for the Developers to synchronize their efforts, share progress, and discuss any impediments.

According to the2020 Scrum Guide:

The Daily Scrum is a15-minute eventwhere the Developers inspect their progress and adapt their plan to achieve the Sprint Goal.

The event belongs to the Developers, and they decide how to structure it, but its purpose must align with the framework’s guidance.

Why the other options are incorrect:

B. Cancel the Daily Scrum and have status update meetings instead:Status update meetings go against Scrum principles, which emphasize team ownership and collaboration.

C. Reduce the occurrence for this meeting to once a week:The Daily Scrum is adailyevent for inspection and adaptation; reducing its frequency would hinder the team’s ability to remain aligned.

D. Make Daily Scrum an optional meeting for the Developers to attend:The Daily Scrum is mandatory for the Developers to inspect and adapt their plan, and making it optional undermines its importance.

One of the key services aScrum Master provides to the Product Owneris helping them findeffective Product Backlog management techniques. This ensures that the Product Owner can maximize the value of the product and effectively manage the Product Backlog.

According to the2020 Scrum Guide, the Scrum Master serves the Product Owner by:

Helping the Product Owner find techniques for effective Product Goal definition and Product Backlog management.

Facilitating stakeholder collaboration when needed.

Supporting empirical product planning for complex environments.

Why the other options are incorrect:

A. Assign tasks to the Developers:Tasks are not assigned in Scrum. Developers are self-organizing and responsible for determining how they will complete the work.

B. Write user stories:Writing user stories is a Product Owner responsibility, not the Scrum Master's.

C. Prioritize the backlog:The Product Owner prioritizes the Product Backlog, not the Scrum Master.

When the Scrum Team does not understand the goal, scope, or product domain, theScrum Master should facilitate a discussion between the Stakeholders, Product Owner, and Developers. This ensures clarity and shared understanding, enabling the team to move forward effectively.

According to the2020 Scrum Guide, the Scrum Master serves the team by:

Facilitating stakeholder collaborationas needed.

Ensuring that the Product Backlog is understoodby the Scrum Team.

Removing any barriers that hinder the team's ability to achieve the Sprint Goal.

Why the other options are incorrect:

A. Direct the Developers to stop working until the Product Owner improves the acceptance criteria:Stopping work is not productive, and collaboration with the Product Owner and stakeholders is the proper approach to resolving misunderstandings.

B. Cancel the Sprint and schedule a new Planning meeting:Cancelling the Sprint should be an absolute last resort and is typically done only when the Sprint Goal becomes unachievable.

C. Do nothing because this is the responsibility of the Product Owner:While the Product Owner owns the Product Backlog, the Scrum Master is responsible for facilitating collaboration and resolving impediments.

The Scrum Master ensures that the Scrum Team is working effectively bycoaching the team in self-management and cross-functionality. This enables the team to take ownership of their work, collaborate effectively, and achieve their goals.

According to the2020 Scrum Guide, the Scrum Master serves the Scrum Team in the following ways:

Coaching team members to improve their practices andself-management skills.

Helping the team become cross-functional so they can deliver complete, Done Increments without relying on external dependencies.

Removing impediments to their progress and facilitating productive Scrum events.

Why the other options are incorrect:

A. Plan Scrum implementations within the organization:While the Scrum Master supports Scrum adoption across the organization, this is not directly related to the Scrum Team's effectiveness.

B. Facilitate Scrum events:Facilitating events is part of the Scrum Master’s responsibilities, but the larger goal is to enable the team's effectiveness through coaching and guidance.

C. Report all user stories in management meetings:Scrum does not involve reporting to management in this way, as the focus is on delivering value rather than detailed reporting.

TheProduct Ownerhas the final authority toorder the Product Backlogto maximize value. They are responsible for ensuring that the most valuable and important work is prioritized so that the Scrum Team delivers maximum value in each Sprint.

According to the2020 Scrum Guide:

The Product Owner is accountable formanaging the Product Backlog, which includes ordering items to best achieve the Product Goal.

While the Developers may provide input, the final decision on ordering lies with the Product Owner.

Why the other options are incorrect:

A. Lead Developer:Scrum does not have a "Lead Developer" role or accountability.

B. Scrum Master:The Scrum Master facilitates and coaches but does not manage or order the Product Backlog.

D. Developers:While Developers provide input during refinement and Sprint Planning, they do not have the authority to order the Product Backlog.

TheDaily Scrumis a short, time-boxed event (15 minutes) where Developers inspect progress toward the Sprint Goal and adapt their plan for the day. It is not intended to solve problems or deep-dive into discussions. If a major technical issue is identified during the Daily Scrum, the team should note it and arrange to discuss and solve itoutside of the Daily Scrum.

According to the2020 Scrum Guide:

The Daily Scrum is focused on progress toward the Sprint Goal, and issues that require detailed discussion or resolution should be handled separately.

The Scrum Master may help facilitate these follow-up discussions if needed.

Why the other options are incorrect:

B. Interrupt the Daily Scrum and solve the problem immediately:The Daily Scrum is not a problem-solving session. Interrupting it for detailed discussions disrupts its purpose and timebox.

C. Escalate it to the Product Owner:Technical issues are typically handled by the Developers, not the Product Owner, who is responsible for managing the Product Backlog and ensuring value delivery.

D. Discuss it during the Sprint Review:Waiting until the Sprint Review to discuss atechnical issue would delay resolution and risk jeopardizing the Sprint Goal.