Back to Professional Scrum Master I (PSM I)

Scale Scrum

Implementing Scrum in large-scale projects.

5 minutes 5 Questions

In Professional Scrum Master I, scaling Scrum refers to the application of Scrum principles in larger settings involving multiple teams working together on complex products. The Scrum Guide itself is "purposefully incomplete," providing a minimal framework that can be extended when needed. When or…

Concepts covered
MetascrumServant LeadershipLarge Scale Scrum (LeSS)Scaled Daily ScrumNexus FrameworkScaled Agile Framework (SAFe)Scrum at Scale (Sc@le)Scrum of ScrumsCross-team CoordinationScaling Mastery
Test mode:
Start practice test
PSM I - Scale Scrum Example Questions

Test your knowledge of Scale Scrum

Question 1

Your company has adopted Scrum and is trying to scale it across multiple teams. As the Scrum Master, what is the most appropriate way to handle inter-team dependencies?

Correct Answer: Implement Scrum of Scrums to address and manage dependencies across teams.

The correct approach in a scaled Scrum environment is to use Scrum of Scrums, a method that allows multiple Scrum teams to communicate with each other, ensuring that dependencies are addressed in a timely and effective manner. Scrum of Scrums is an essential practice for aligning teams, fostering collaboration, and facilitating the resolution of dependencies. Assigning a dependency manager or adopting a centralized planning approach may create bottlenecks and reduce the autonomy of the teams, which is against Scrum principles. Organizing teams to work in silos ignores the reality of dependencies in complex projects and can lead to integration challenges later on.

Question 2

You've recently been assigned as Scrum Master to a new enterprise project. The project is large, complex, and involves many different teams. What's the best approach to planning and managing a large Scrum project?

Correct Answer: Adopt a scaled agile framework like Scrum of Scrums or Large-Scale Scrum (LeSS) for coordinating and integrating the work of multiple Scrum teams.

While implementing Scrum on a large-scale project, it is essential to enable efficient coordination and collaboration across multiple teams. Scaling frameworks such as Scrum of Scrums or Large-Scale Scrum (LeSS) are designed to handle the complexity of large projects by establishing roles, artifacts, and events that facilitate integration across teams. Using a single Scrum board for all teams may lead to information overload and reduce clarity. Introducing a Chief Product Owner can help in aligning priorities across teams, but it does not address the complexities related to large-scale coordination and integration. Decomposing the project into smaller, independent projects may reduce dependency but can also lead to fragmentation and dilute the overall goal of the project.

Question 3

In an organization using the Nexus Framework, multiple Scrum Teams are delivering separate increments at the end of the Sprint causing a lack of integration. What should be the Scrum Master’s approach?

Correct Answer: Enforce a Sprint Goal that requires all teams to work on features that contribute towards a single, integrated increment.

In the Nexus Framework, it is imperative to aim for an integrated increment at the end of the Sprint to ensure that the product increments produced by different Scrum Teams are potentially releasable. The correct answer emphasizes working on features that align with a common Sprint Goal across teams, facilitating integration throughout the Sprint. Implementing a separate Integration Sprint does not adhere to the principles of Scrum where each Sprint should result in a potentially releasable Increment. Encouraging separate backlog prioritization and assigning specific integration tasks to teams are less effective strategies as they do not guarantee a cohesive and integrated increment, which is the essence of nexus integration.

More Scale Scrum questions
78 questions (total)
Start 78 question test