Scrum Events

5 minutes 5 Questions

In Scrum, there are five events for inspection and adaptation, namely: The Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. These events are specified to reduce regularity of meetings and to enable timely decision-making. Each of these time-boxed events happen in a specific o…

A Comprehensive Guide to Scrum Events for the PSM I Exam

Importance:
Scrum Events are critical elements in the Scrum framework, the systematic understanding and correct implementation of which can enhance project efficiency and improve teamwork. They create regularity and minimize unnecessary meetings. They also provide the framework for teams to reflect, synchronize, plan and adapt.

Scrum Events:
Scrum defines five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.

How Scrum Events Work:

Sprint: It's the core of Scrum where the actual work happens, maximum one month long.
Sprint Planning: The team plans and agrees on the tasks to be done in the coming Sprint.
Daily Scrum: The team inspects progress towards the Sprint Goal and adapts the Sprint Backlog accordingly.
Sprint Review: The Scrum Team and stakeholders inspect the outcome of the Sprint and discuss what to do the next.
Sprint Retrospective: Used for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

Exam Tips: Answering Questions on Scrum Events:
Understand the purpose of each event, who participates and the outcomes. Pay attention to the time boxes. Remember, in Scrum, change is accepted but within the boundaries of the fixed-length Sprint. Be clear on what artifacts are reviewed/updated and when. Understanding the flow of Scrum events helps a lot.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

PSM I - Scrum Events Example Questions

Test your knowledge of Scrum Events

Question 1

You have noticed that the Product Owner is not attending the Sprint Planning meetings consistently. What should be the Scrum Master's course of action here?

Adjust the Sprint duration to accommodate the Product Owner’s availability, ensuring their participation in the planning. Address the issue by coaching the Product Owner on the impact of their absence and reinforcing the value they bring to Sprint Planning. Encourage the development team to proceed with selecting Product Backlog items they feel confident in without the Product Owner’s direct input, documenting assumptions for later review. Organize a separate meeting with stakeholders to discuss the Product Backlog without the Product Owner, ensuring alignment.

Correct Answer: Address the issue by coaching the Product Owner on the impact of their absence and reinforcing the value they bring to Sprint Planning.

The correct course of action involves the Scrum Master using their role to educate and coach the Product Owner on the importance of their active participation in Sprint Planning. This is crucial for effectively conveying the vision, clarifying details of the Product Backlog items, and determining the Sprint Goal. The wrong answers divert from this approach by either bypassing the Product Owner’s role, making adjustments that could compromise the Scrum framework, or putting the development team in a position to make Product Backlog decisions without the necessary context, all of which can lead to misunderstandings and misalignment with the Product Goal.

Question 2

The product owner is continuously interfering with day to day team activities and trying to push more work into the sprint. What is your role and action in this situation?

Include the extra work in the sprint Ask the team to work overtime Protect the team from external interference and remind the product owner about the rules Retain silent and let the team handle it

Correct Answer: Protect the team from external interference and remind the product owner about the rules

The primary role of a Scrum Master in a Scrum team is to protect the team from external interferences and help the team focus on the agreed-upon sprint goals. So, when a product owner tries to interfere with the team's day-to-day activities and tries to push more work into the ongoing sprint, the Scrum Master should intervene. The Scrum Master should remind the product owner about the rules of Scrum, where adding extra work in the middle of the sprint is discouraged unless it's absolutely necessary. The scope creep should be handled properly, and the product owner needs to respect the boundaries of the ongoing sprintThe other answers are not in line with the Scrum framework and are incorrect:1. Asking the team to work overtime can lead to team burnout and a decrease in the productivity and quality of work which is not in line with Agile principles2. Retaining silent and letting the team handle it is also not a good idea, as protecting the team and facilitating Scrum practices is the responsibility of the Scrum Master3. Including the extra work in the sprint without discussion with the team and reassessing the sprint goals and capacity is against the Scrum rules.

Question 3

During a Sprint Review, a stakeholder proposes a new feature that aligns with Sprint Goal, but certainly will extend the Sprint length. As a Scrum Master, what would the best way to handle this?

Propose to drop a less important item from the current Sprint to make room for the new feature, assuming it will not impact the Sprint Goal significantly. Advocate for extending the current Sprint by a few days to include the new feature, consulting with the Development Team for their agreement. Schedule an immediate Sprint Planning meeting to accommodate the new feature into the current Sprint, ensuring it doesn't impact the Sprint Goal. Politely explain to the stakeholder that the current Sprint content is decided and cannot be changed, but their feature can be considered for the Product Backlog for future Sprints.

Correct Answer: Politely explain to the stakeholder that the current Sprint content is decided and cannot be changed, but their feature can be considered for the Product Backlog for future Sprints.

Sprints are fixed in duration and their scope, once committed, is expected to remain unchanged. The correct approach is to consider the new feature for future Sprints, adding it to the Product Backlog for refinement and prioritization. Immediate changes to the Sprint, extending its duration, or reprioritizing its content are not recommended practices as they disrupt the team's focus and undermine the principles of Scrum.

🎓 Unlock Premium Access

Professional Scrum Master I + ALL Certifications

🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
2149 Superior-grade Professional Scrum Master I practice questions
Unlimited practice tests across all certifications
Detailed explanations for every question
PSM I: 5 full exams plus all other certification exams
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!

Start Your Free 7-Day Trial