nerdexam
EXIN

ASF · Question #62

A 200 member project team is working on a large and complex system with multiple sub-systems. They would like to start using the Agile Scrum methodology. As a Scrum Master, what would your best…

The correct answer is C. Agree a logical sub-division of the system so that smaller Scrum teams can work on sub- systems. C is correct because Scrum explicitly supports large projects through the "Scrum of Scrums" pattern - splitting a large team into multiple smaller Scrum teams (typically 5–9 members each), each owning a sub-system, then coordinating across teams. This preserves Scrum's core…

Scaling Scrum

Question

A 200 member project team is working on a large and complex system with multiple sub-systems. They would like to start using the Agile Scrum methodology. As a Scrum Master, what would your best advice be?

Options

  • AScrum is not suited for such a large project.
  • BAsk all potential members of the project team to have a meeting first and decide if they agree to
  • CAgree a logical sub-division of the system so that smaller Scrum teams can work on sub- systems

How the community answered

(22 responses)
  • A
    9% (2)
  • B
    18% (4)
  • C
    73% (16)

Explanation

C is correct because Scrum explicitly supports large projects through the "Scrum of Scrums" pattern - splitting a large team into multiple smaller Scrum teams (typically 5–9 members each), each owning a sub-system, then coordinating across teams. This preserves Scrum's core values while scaling to enterprise size.

A is wrong because Scrum is not inherently limited to small projects. Scaled frameworks like SAFe, LeSS, and Nexus are built precisely for this scenario - large teams using Scrum across complex systems.

B is wrong because consensus from all 200 members is neither practical nor a Scrum principle. The Scrum Master's role is to guide and coach, not to seek unanimous approval before adopting a methodology.

Memory tip: Think "Divide and Scrum" - when a team is too large for one Scrum, divide the system into sub-systems and let smaller Scrum teams own each piece. Large team = multiple Scrums, not no Scrum.

Topics

#scaling Scrum#large teams#sub-systems#team size

Community Discussion

No community discussion yet for this question.

Full ASF Practice