Back to Professional Scrum Master I (PSM I)

Scrum in Different Contexts

Applying Scrum outside software development.

5 minutes 5 Questions

Scrum is a framework that can be applied across diverse contexts while maintaining its core principles. Though initially popular in software development, Scrum's versatility extends to multiple domains. While Scrum's rules remain consistent regardless of application area, how teams implement those…

Concepts covered: Scrum with Kanban, Scrum in Large Organizations, Scrum in Hardware Development, Scaling Scrum, Scrum in HR, Scrum Rookies vs Scrum Veterans, Distributed Teams, Scrum in non-Software Development, Scrum in Marketing, Scrum in Fixed-Price Projects

Test mode:
Start practice test
PSM I - Scrum in Different Contexts Example Questions

Test your knowledge of Scrum in Different Contexts

Question 1

A Scrum rookie Master suggests that scrum team makes major decisions, which affects the product backlog. A veteran Scrum Master disagrees. Who is correct?

Correct Answer: The veteran is correct. The Product Owner is responsible for the content, availability, and order of the Product Backlog.

According to Scrum Guide, the Product Owner is explicitly responsible for the Product Backlog, including its content, availability, and ordering. While the Scrum Team as a whole might discuss and suggest changes, the Product Owner has the ultimate authority to make decisions about the Product Backlog.

Question 2

Your Scrum team is working on a hardware development project to build a new server system. The team is trying to decide when they should be releasing the server during the sprint. What is the best Scrum approach to this scenario?

Correct Answer: The team aims to have a potentially releasable increment by the end of each Sprint, aligning with the Sprint Goal.

In Scrum, the objective is to have a potentially releasable increment by the end of each Sprint, ensuring that the product could be released to customers if deemed appropriate without being tied to external approvals or extensive documentation processes. While Stakeholder feedback during the Sprint Review is crucial for future planning, it does not directly dictate release timings. Comprehensive documentation, although important, especially in hardware development, should not delay the potential for release each Sprint. Finally, release decisions are not the primary focus of the Sprint Retrospective, which is intended for the team to inspect their processes and make improvements going forward.

Question 3

Your Scrum team is working on a hardware product and suspects that the selected materials will not suffice for the quality expectations. The team has already committed to deliver the product at the end of the sprint. What should be your course of action?

Correct Answer: Raise this as an issue in the Daily Scrum to facilitate proactive problem-solving, involving the team and the Product Owner in the discussion.

The essence of Scrum is collaboration and transparency. Raising the issue in the Daily Scrum allows for collective problem-solving and ensures that the team and the Product Owner are aligned and can work together on a solution. Directing the problem to stakeholders or management without team consultation can bypass the collaborative nature of Scrum and potentially disrupt the Sprint Goal. Similarly, adjusting the sprint backlog without team and Product Owner discussion disregards the importance of maintaining agreed-upon goals and scope for the sprint.

More Scrum in Different Contexts questions
79 questions (total)
Start 79 question test