SE2 (LEC) Week 7 - 8 Introduction to Scrum

During the daily stand-up meeting, a team member mentions difficulty focusing due to constant interruptions from external stakeholders. What should the Scrum Master do?

• Ignore the issue as it's not directly related to the sprint backlog.

• Explain to the stakeholders that the team is unavailable for interruptions during the stand-up.

• Instruct the team member to deal with the interruptions themselves.

• Investigate the source of the interruptions and address them directly with the stakeholders involved.

Your team is considering adopting a new approach to manage their software development project. They are debating between Agile and Scrum. Which statement is most accurate?

• Agile is a specific project management framework, while Scrum is a broader methodology encompassing various approaches.

• Agile and Scrum have no connection; they are entirely different project management methodologies.

• Both Agile and Scrum are synonymous terms used to describe the same project management approach.

• Agile is a set of principles and values, while Scrum is a specific framework that implements those principles.

Every morning, the team gathers for a brief meeting to discuss progress, identify roadblocks, and adjust their work if needed. What event is this?

• Sprint Backlog Refinement

• Daily Scrum

• Sprint Retrospective

• Sprint Review

The Product Owner keeps adding new user stories to the sprint backlog midway through the sprint, causing the team to feel overwhelmed. What should the Scrum Master do?

• Accept the changes and inform the team to adjust their work accordingly.

• Inform the Product Owner that changes are not allowed during a sprint and redirect them to wait for the next sprint.

• Ask the team to work overtime to meet the revised sprint goals.

• Schedule a meeting with the Product Owner, team, and stakeholders to discuss the situation and find a collaborative solution.

The daily stand-up meeting is exceeding its allotted time of 15 minutes. What can you do to improve the efficiency of future stand-up meetings?

• Encourage team members to be more detailed in their explanations.

• Discuss personal updates and non-work-related topics to build team rapport.

• Focus on individual accomplishments and achievements during the meeting.

• Limit individual speaking time and ensure everyone stays focused on the core questions

The team is planning their upcoming sprint. They gather to discuss user stories, estimate effort, and assign tasks. Which Scrum event are they participating in?

• Sprint Retrospective

• Daily Scrum

• Sprint Review

• Sprint Planning

You completed a user story yesterday that involved adding a product search bar to the platform.

During the stand-up, you should:

• Ask the team for feedback on the design of the search bar.

• Briefly mention you finished the user story.

• Explain the technical details of how you implemented the search bar.

• Demonstrate the functionality of the search bar to the team.

The development team is struggling to meet their sprint goals due to a lack of understanding of a new technology required for a user story. What should the Scrum Master do?

• Delegate the task to a team member with relevant experience and inform the Product Owner.

• Criticize the team for not being prepared and assign them additional training resources.

• Facilitate a session to help the team learn the new technology collaboratively.

• Remove the user story from the sprint backlog and add it to the next sprint.

Imagine you are a member of a Scrum team developing a new e-commerce platform. Today is your daily stand-up meeting. Which of the following questions is NOT typically asked during a daily stand-up meeting?

• What are your long-term goals for the project?

• What did you accomplish yesterday?

• Are there any roadblocks preventing your progress?

• What are your priorities for today?

Multiple stakeholders approach the Product Owner with urgent requests outside the current sprint. How should they respond?

• Explain priorities for the current sprint and guide stakeholders on how to add their requests to the product backlog for future consideration.

• Tell the stakeholders that Scrum doesn't allow changes after the sprint begins.

• Add the requests to the current sprint backlog, regardless of potential disruptions.

• Pick the most important-sounding request and instruct the team to work on it.