Evolving the Agile Organization

Leading agile transformations, scaling Scrum, and shaping organizational design and culture.

5 minutes 5 Questions

Evolving the Agile Organization is a critical concept in the Professional Scrum Master II (PSM II) framework that focuses on how Scrum Masters can drive organizational change beyond the team level. It recognizes that true agility requires systemic transformation, not just team-level Scrum adoption.…

Concepts covered
Organizational Design and Agile CulturePortfolio Planning and AgilityScaling Scrum and Multiple TeamsEvidence-Based Management (EBM)
Test mode:
Start practice test

PSM II - Evolving the Agile Organization Example Questions

Test your knowledge of Evolving the Agile Organization

Question 1

A Scrum Master supports four Scrum Teams building one product. A manager proposes that each team should specialize in a specific architectural layer (e.g., UI, API, database, infrastructure) to reduce complexity and improve efficiency. The Product Owner is concerned this might create problems. What should the Scrum Master recommend?

Correct Answer: Recommend forming cross-functional, feature-based teams that can deliver end-to-end increments of value each Sprint

Cross-functional, feature-based teams can deliver end-to-end Done Increments each Sprint, minimizing dependencies, reducing coordination overhead, and maximizing each team's ability to independently deliver value.

Component or layer-based teams create heavy inter-team dependencies, requiring constant coordination and often preventing any single team from delivering a usable Increment independently. Adding an integration team introduces a handoff and bottleneck that delays feedback and violates the principle that each team should produce a Done Increment. Experimenting with a known anti-pattern wastes time when the problems of component teams are well understood in scaled Scrum.

Key concept tested: feature teams versus component teams in scaled Scrum and minimizing cross-team dependencies.

Question 2

A Scrum Master notices that an organization's existing communities of practice (CoPs) are siloed by department—testing CoP, development CoP, and architecture CoP. Teams struggle to share learning across disciplines, and innovation remains confined within functional boundaries. The Scrum Master wants to leverage these CoPs to foster a more agile culture. What approach should the Scrum Master take?

Correct Answer: Encourage the formation of cross-discipline CoPs organized around product domains or value streams, enabling shared learning across functional expertise areas

Cross-discipline CoPs organized around product domains or value streams break down functional silos by bringing together people with diverse expertise to share learning and innovate around common business outcomes, which directly addresses the stated problem.

Strengthening existing functional CoPs reinforces the very silos causing the problem. Merging all CoPs into one massive community would be unwieldy and dilute focus, reducing effectiveness. Creating a Scrum Master-led coordination CoP adds an intermediary layer that filters and controls knowledge flow rather than enabling direct cross-functional collaboration, and it positions Scrum Masters as gatekeepers rather than facilitators.

The key concept tested is using communities of practice to enable cross-functional collaboration and break organizational silos in support of agile culture.

Question 3

A Scrum Master joins an organization where teams are called 'Scrum Teams' and use Sprints, but each team only contains people from one department (e.g., a testing team, a design team, a development team). Work flows sequentially between these teams. What best explains why this structure limits agility?

Correct Answer: Teams cannot deliver a Done Increment independently because each team owns only one skill area, creating handoffs and dependencies

The core problem with component or department-based teams is that no single team possesses all the skills needed to deliver a Done, potentially releasable Increment, which means work must flow sequentially through multiple teams, creating handoffs, dependencies, wait times, and integration risks that fundamentally undermine agility.

Stakeholder composition at Sprint Reviews is unrelated to team structure limitations. Velocity estimation challenges are a symptom, not the root cause of reduced agility. Sprint cadence inconsistency is also a downstream effect rather than the fundamental structural problem.

The key concept tested is cross-functional, feature-based Scrum Teams versus component teams and the importance of teams that can independently deliver Done Increments.

More Evolving the Agile Organization questions
305 questions (total)
Practice 100 questions
One session at a time, always new questions