About the Class

Through the Registered Scrum@Scale Practitioner (RS@SP) course, you’ll learn how to scale Scrum, the lightweight agile framework that helps people, teams and organizations to deliver valuable solutions for some of the world’s most complex, challenging problems. We’ll apply Scrum to teams-of-teams and organizations, describing how the Product Owner, individual Scrum teams, and enterprise leadership interact in a variety of different scaling situations while applying Scrum@Scale.

At the heart of Scrum@Scale are the Product Owner Cycle and the ScrumMaster Cycle, to sets of Scrum practices that define the “what” and the “how” of product development. You’ll learn these two cycles and how to connect them together to effectively deliver high-value, high-quality products at scale.

Once you complete the Registered Scrum@Scale Practitioner (RS@SP) course, you’ll qualify to take the Registered Scrum@Scale Practitioner exam and earn the RS@SP credential from the Agile Education Program.

What We’ll Cover

The Registered Scrum@Scale Practitioner course covers six main topics — an overview of Scrum@Scale, Scaling Teams via Scrum@Scale, Scrum Patterns, the Scrum Master Cycle, the Product Owner Cycle and Connecting the Cycles.

Scrum@Scale Overview

• The Scrum@Scale Framework, including its purpose, its definition and when its best used.
• Describe the importance of a values-driven culture in Scrum@Scale, as well as how to create a values-driven culture and why creating a values-driven culture is often so challenging.

Scaling Teams via Scrum@Scale

• The Scrum Team as the foundational building-block of Scrum@Scale
• The Scrum of Scrums (SoS), the team-of-teams who self-manage value delivery by multiple Scrum Teams.
• The Scaled Daily Scrum, the opportunity for multiple Scrum teams to work toward the SoS Sprint goal, to manage, mitigate and eliminate dependencies, and to share insights learned.

Scrum Patterns

• The patterns of high performing teams, describing how these patterns can be used to scale Scrum. 
• We’ll cover patterns that include the Interrupt Buffer, Swarming, the Happiness Metric, Yesterday’s Weather, Teams that Finish Earlier Accelerate Faster, Good Housekeeping, and the power of Stable Teams.

The Scrum Master Cycle

• The Scrum Master cycle - the activities that coordinate the “How” in a Scrum@Scale environment.
• The Scrum of Scrums Master (SoSM) role and accountabilities, including how the role scales as the organization scales.
• The Executive Action Team (EAT) in Scrum@Scale, including how this team guides execution, ideal members of the team, and the difference between an EAT and a traditional PMO.
• The Agile Practice, a pattern using in Scrum@Scale that ensures quality Scrum is practiced in the organization.
• The role of continuous improvement when scaling Scrum.
• Impediment removal and escalation in a scaled environment.
• Help to assess the organization’s effectiveness at impediment removal.
• Coordination across teams, including sharing learning and communication across teams, coordinating the “what” and the “how” via Scrum of Scrums and MetaScrum in Scrum@Scale.
• Delivery, including different approaches to delivery, the value of automation when delivering, leveraging the SoS for release management, and understanding how delivery cadence varies across organizations.

The Product Owner Cycle

• The Product Owner Team, a scaled version of the Scrum Product Owner.
• The Executive MetaScrum, a forum for the Product Owner to meet with stakeholders and translate the strategic vision into an actionable backlog.
• How strategic vision relates to product goals.
• Measuring progress toward achieving strategic vision and product goals.
• How prioritization of the backlog affects a company’s bottom line or ability to fulfill the strategic vision.
• Identify methods of determining business value, including ways to release earlier in the cycle.
• Release planning as a means of forecasting versus coordinating delivery.

Connecting the Cycles

• The importance of obtaining feedback from multiple sources, including stakeholders, customers and Scrum team members.
• The purpose of MVP and the pivot as they relate to obtaining feedback.
• Applying feedback to both product and delivery processes.
• Identifying the different lenses for measuring progress and give sample success metrics.