Organizational Design and Agile Culture are two interconnected pillars critical to scaling agility beyond individual teams, a key focus area in the Professional Scrum Master II (PSM II) curriculum and the broader concept of Evolving the Agile Organization.

**Organizational Design** refers to how an organization structures its teams, hierarchies, communication pathways, and decision-making processes to support agility. Traditional organizations often rely on functional silos, top-down command structures, and rigid processes that impede collaboration and responsiveness. In contrast, an agile-oriented organizational design favors cross-functional, self-managing teams aligned around value streams rather than functional departments. It emphasizes decentralized decision-making, minimizing handoffs, reducing dependencies, and creating structures where teams can deliver end-to-end value autonomously. A Scrum Master operating at the organizational level helps leaders understand how structural impediments—such as misaligned incentive systems, excessive approvals, or siloed departments—hinder agility and guides them toward restructuring for flow and collaboration.

**Agile Culture** is the mindset, values, and behaviors that permeate the organization. It encompasses psychological safety, transparency, continuous improvement, experimentation, and a willingness to embrace failure as a learning opportunity. Culture is shaped by leadership behaviors, organizational policies, and daily interactions. Without a supportive culture, agile frameworks become hollow ceremonies devoid of real impact. An agile culture values individuals and interactions, encourages empiricism, and fosters trust at every level.

The connection between the two is vital: organizational design shapes culture, and culture reinforces or undermines design choices. A PSM II-level Scrum Master recognizes that sustainable agility requires addressing both dimensions simultaneously. They act as change agents, coaching leaders to align structures, policies, and cultural norms with agile principles. They facilitate conversations about systemic impediments and help the organization evolve iteratively, treating organizational change itself as an empirical process guided by inspection, adaptation, and transparency.

Scaling Scrum and Multiple Teams is a critical concept in the Professional Scrum Master II (PSM II) framework that addresses how organizations can effectively apply Scrum principles when multiple teams collaborate on a single product or complex initiative.

At its core, scaling Scrum maintains the foundational Scrum framework while introducing coordination mechanisms to manage dependencies, integration, and alignment across teams. The Nexus framework, developed by Scrum.org, is a commonly referenced approach that extends Scrum for 3-9 teams working on a single Product Backlog.

Key principles of scaling Scrum include:

1. **Single Product Backlog**: Regardless of the number of teams, there is one Product Backlog managed by one Product Owner. This ensures a unified vision and consistent prioritization across all teams.

2. **Cross-Team Coordination**: Teams must identify and manage dependencies through integration events such as cross-team refinement, a unified Sprint Planning, and joint Sprint Reviews to inspect the integrated increment.

3. **Integrated Increment**: All teams must produce a combined, Done, integrated increment by the end of each Sprint. This requires strong engineering practices, continuous integration, and shared Definition of Done.

4. **Minimizing Dependencies**: Effective scaling focuses on reducing inter-team dependencies through properly structured, cross-functional teams that can deliver end-to-end functionality.

5. **Transparency and Communication**: Scaling demands enhanced transparency through shared artifacts, regular Scrum of Scrums or integration meetings, and open communication channels.

The Scrum Master's role in a scaled environment evolves significantly. They must facilitate cross-team collaboration, help remove organizational impediments, coach leadership on empiricism, and foster an environment where teams can self-manage effectively. They also play a vital role in identifying systemic issues that hinder delivery across teams.

Successful scaling requires organizational support, including aligned structures, reduced bureaucracy, and a culture that embraces agility. The goal is not merely to scale processes but to scale the ability to deliver value while maintaining agility and responsiveness to change.

Portfolio Planning and Agility is a critical concept in scaling Scrum and evolving organizations toward enterprise-level agility. It involves strategically managing a collection of products, projects, and initiatives to maximize business value while maintaining agile principles.

At the portfolio level, organizations must balance long-term strategic goals with the ability to respond to changing market conditions. Traditional portfolio management relied on annual budgeting cycles and rigid project plans, but agile portfolio planning embraces iterative decision-making, frequent reassessment, and lean governance.

Key elements of Portfolio Planning and Agility include:

1. **Lean Budgeting**: Instead of funding individual projects, organizations allocate budgets to value streams or product lines, empowering teams to make decisions about how to best deliver value without bureaucratic overhead.

2. **Strategic Alignment**: Portfolio-level planning ensures that all Scrum Teams are working toward organizational objectives. This involves creating transparency around strategic themes and priorities so teams understand how their work contributes to the bigger picture.

3. **Empirical Governance**: Rather than relying on upfront predictions, agile portfolio management uses empirical data — such as throughput, customer satisfaction, and business outcomes — to make investment decisions and adjust priorities.

4. **Decentralized Decision-Making**: Agile organizations push decision authority to the teams closest to the work, reserving only strategic, infrequent, and high-impact decisions for centralized leadership.

5. **Managing Flow**: Portfolio agility focuses on limiting work in progress (WIP) at the organizational level, ensuring teams are not overburdened and can deliver with quality and speed.

6. **Continuous Reprioritization**: Portfolios are regularly reviewed through cadenced planning events, allowing the organization to pivot based on new information, market shifts, or emerging opportunities.

For a Professional Scrum Master, understanding portfolio agility means helping organizations move beyond team-level Scrum toward systemic agility, removing organizational impediments, and fostering a culture where strategic decisions are made transparently and empirically.

Evidence-Based Management (EBM) is an empirical framework developed by Scrum.org that helps organizations measure, manage, and improve the value they deliver. Rather than relying on gut feelings or vanity metrics, EBM encourages leaders and Scrum Masters to make strategic decisions based on tangible evidence and measurable outcomes.

EBM revolves around four Key Value Areas (KVAs) that provide a holistic view of an organization's ability to deliver value:

1. **Current Value (CV):** Measures the value delivered to customers and stakeholders today. Metrics may include customer satisfaction, employee satisfaction, and revenue per employee. This area answers the question: How happy are our users and stakeholders right now?

2. **Unrealized Value (UV):** Represents the potential value that could be realized if the organization met the needs of all potential customers. It highlights market gaps and opportunities. Metrics include market share and customer desire vs. satisfaction gap.

3. **Ability to Innovate (A2I):** Measures the organization's capacity to deliver new capabilities and innovative solutions. It examines technical debt, feature usage, and the percentage of time spent on maintaining legacy systems versus building new value.

4. **Time to Market (T2M):** Assesses how quickly the organization can deliver new features, services, or products. Key metrics include release frequency, cycle time, and lead time.

For a Professional Scrum Master II, understanding EBM is crucial for evolving the Agile organization. Scrum Masters use EBM to guide leadership conversations, helping stakeholders move beyond output-focused metrics (like velocity) toward outcome-based measures that reflect true business value. By establishing a Strategic Goal and Intermediate Goals, teams can run experiments, inspect results, and adapt their approach.

EBM supports the empirical pillars of Scrum—transparency, inspection, and adaptation—at an organizational level, enabling data-driven continuous improvement and fostering an environment where agility extends beyond individual teams to the entire enterprise.