Product LeadersMasterclass

Scaled Professional Scrum with Nexus (SPS) with Certification

Learn to scale Scrum with the Nexus Framework, tackle cross-team challenges, and prepare for SPS certification through hands-on workshops and collaborative exercises.

Masterclass Scrum.org Traditional (Full Day) · Traditional (Half Day) · Immersive

What changes for your team

  • Make multiple Scrum teams move as one
  • Turn cross-team blockers into flow
  • Certification readiness with real application

Immersive training pays back differently to a two-day course. Sessions spread across several weeks mean each idea is applied in your real work before the next one lands — so capability builds instead of fading under a backlog. Why immersive produces better returns →  ·  Other formats available in the panel above.

Scaled Professional Scrum with Nexus (SPS) with Certification

Course Code: SPS

Overview

A hands-on, activity-based course designed to equip professionals with practical skills for scaling Scrum using the Nexus Framework, addressing cross-team challenges, and preparing for the Scaled Professional Scrum (SPS) certification.

Target Audience

  • Product Owners
  • Product Managers
  • Scrum Masters
  • Lean Agile Practitioners
  • Scrum Teams
  • Development Leads and Managers
  • Anyone involved in managing or participating in scaled Scrum product development

Learning Outcomes

  • Understand that scaled Scrum is still Scrum
  • Gain an introduction to the Nexus Framework
  • Learn new roles, artifacts, and events in Nexus
  • Organize teams and work for large-scale development
  • Manage the Nexus and Nexus+
  • Address common challenges in scaling Scrum
  • Apply practices to efficiently build integrated software products
  • Experience organizing several teams working on the same product
  • Optimize team productivity
  • Identify, minimize, and remove dependencies

Course Topics

  • Scaling Scrum and organizing teams
  • Team selection and organizing work
  • Nexus in action
  • Managing the Nexus
  • Overcoming cross-team dependencies and collaboration challenges
  • Practices for launching, structuring, and managing large Agile projects

Certification

  • Includes one free attempt at the Scaled Professional Scrum (SPS) certification exam
  • Second attempt provided if the first is taken within 14 days and unsuccessful

Frequently Asked Questions

Scaled Professional Scrum with Nexus (SPS) is designed for experienced Scrum professionals: Scrum Masters, Product Owners, team members, Agile coaches, and department managers involved in scaling Scrum across multiple teams. It is not suitable for those with little to no prior Scrum experience.

SPS includes one free attempt at the Scaled Professional Scrum (SPS) certification exam; if you take your first attempt within 14 days and don’t pass, you’re granted a second try at no additional cost.

You’ll tackle cross-team dependencies, challenges in organising multiple Scrum teams, transparency issues, and approaches for delivering value at scale—all based on typical obstacles organisations face when scaling Scrum.

You should have strong, hands-on Scrum experience in roles like Scrum Master, Product Owner, or team member before attending SPS; it’s not suitable for those unfamiliar with Scrum.

The SPS certification from Scrum.org is globally recognised and valued by employers and the Agile community as evidence of your understanding of scaling Scrum with Nexus.

Syllabus

Here is exactly what your team will cover, and how we deliver it. Browse the syllabus below, then choose the format that fits how your people learn and how fast you need results:

Every format delivers practical skills your team can apply immediately—through incremental learning, outcome-based assignments, and facilitated reflections that connect the material to your real challenges and keep capability improving long after the session ends.

Before You Start

Complete the pre-work below before your first session so you arrive ready to participate.

Scaling Scrum Fundamentals & Case Study Kickoff

Session 1 120+
Introduces the need for scaling and the Nexus approach while reinforcing that Scaled Scrum is still Scrum. Explores why and when to scale Scrum versus keeping it simple. Provides an overview of the Nexus framework at a high level. Kicks off the Surge Pricing case study – an end-to-end scenario used throughout the course – outlining how multiple teams will collaborate on a single product with dynamic pricing features.
Reflect on your current organization or project and identify key challenges or pain points related to scaling Scrum. Consider how the principle “Scaled Scrum is still Scrum” could address each challenge.
View Examples

Nexus Framework Deep Dive

Session 2 120+
Dives into the Nexus framework’s structure and mechanics. Details the new Nexus roles, events, and artifacts that augment Scrum for scaling: the Nexus Integration Team, Nexus Sprint Planning, Nexus Daily Scrum, Nexus Sprint Review & Retrospective, and the Nexus Sprint Backlog. Discusses how each addition addresses common scaling issues (like cross-team coordination and integration). Uses the Surge Pricing case to map these Nexus elements onto a realistic multi-team project.
Summarize the key differences between a single-team Scrum and the Nexus framework. Identify each new Nexus role, event, or artifact and explain in your own words how it helps multiple teams work together.
View Examples

Organizing Teams & Nexus Integration Team

Session 3 120+
Focuses on structuring people and teams in a scaled Scrum environment. Examines strategies for organizing multiple Scrum Teams around one product (feature teams vs. component teams) while minimizing dependencies. Introduces the Nexus Integration Team in depth – its composition, responsibilities, and how it supports the Scrum Teams to produce an integrated increment. Through the Surge Pricing case, students form Scrum Teams for the project and decide who might serve on the Nexus Integration Team, learning how to coordinate roles across teams.
Develop a high-level team organization plan for a Nexus working on a single product. Decide how you would split into 3–9 Scrum Teams and outline the role of a Nexus Integration Team in your context or the case study.
View Examples

Organizing the Work & Managing Dependencies

Session 4 120+
Covers techniques for organizing and refining the work in a multi-team environment. Emphasizes maintaining a single Product Backlog and making dependencies visible. Students learn how to use Product Backlog refinement at scale to identify and address cross-team dependencies before Sprint Planning. Practices such as User Story Mapping are introduced to help slice work and allocate Product Backlog Items across teams. The importance of a shared Definition of Done is reinforced to guarantee that all teams deliver “Done” increments that integrate. In the Surge Pricing case study, the class refines backlog items (e.g. pricing engine, UI integration stories) and collaboratively drafts a Nexus-wide Definition of Done covering integration criteria.
Create or refine a Definition of Done (DoD) that would apply to all teams in a Nexus. Ensure it includes quality criteria and integration steps required for a potentially releasable, integrated increment each Sprint.
View Examples

Nexus in Action: Sprint Planning & Daily Coordination

Session 5 120+
Brings the Nexus framework to life by simulating Sprint execution events. Students experience Nexus Sprint Planning, where representatives from each team align on a single Nexus Sprint Goal and coordinate what each team will deliver. They learn to create a Nexus Sprint Backlog that highlights all teams’ selected items and inter-team dependencies. The session also covers how individual Scrum Teams then do their own Sprint Planning in the Nexus context. Additionally, the Nexus Daily Scrum is introduced as a daily forum for teams to share progress on the integrated increment and address new dependencies or integration issues. Using the Surge Pricing case, learners practice a scaled Sprint Planning: for example, teams plan Sprint 1 together to build and integrate a surge pricing engine and UI updates, negotiating who works on which backlog items and identifying touchpoints between teams.
Define a Nexus Sprint Goal and outline a brief Sprint plan that coordinates multiple teams. Imagine you are preparing for a Nexus Sprint Planning – determine a common Sprint Goal and how a few teams could each contribute to it.
View Examples

Nexus in Action: Integrated Increment & Sprint Review

Session 6 120+
Continues the Nexus simulation through the end of the Sprint. This session emphasizes producing an integrated Increment and inspecting it at scale. Students learn how multiple teams collaborate throughout the Sprint to build a single, integrated product increment and ensure it meets the Nexus-wide Definition of Done. The Nexus Sprint Review is covered as a joint event where all teams and stakeholders review the integrated increment together to gather feedback. Techniques for running effective large-scale Sprint Reviews (e.g., coordinated demos across teams) are discussed. The session also details the Nexus Sprint Retrospective, which has three parts (overall Nexus Retrospective, individual team retrospectives, and a final Nexus Retrospective) to identify improvements both across the Nexus and within each team. Through the case study, students plan a combined Sprint Review for Surge Pricing (showcasing a unified product increment) and practice conducting a Nexus Retrospective to uncover cross-team improvements (such as better integration testing processes).
Outline how you would conduct a Sprint Review for a Nexus delivering a single integrated increment. Define what would be demonstrated and who should be involved to get meaningful feedback on the overall product.
View Examples

Managing the Nexus: Transparency, Metrics & Scaling Practices

Session 7 120+
Addresses how to effectively manage and sustain a Nexus over time. Students explore ways to maintain transparency and oversight when many teams are working together. The session introduces metrics and tools (often drawing on Evidence-Based Management principles) to track progress and value in a scaled environment – for example, measuring integrated velocity, release frequency, defect trends, and other Key Value Areas (Current Value, Time-to-Market, Ability to Innovate, Unrealized Value). Participants discuss how to visualize Nexus work (using information radiators like integrated burndown charts or dependency boards) and how to detect when a Nexus is not improving. Common scaling challenges are revisited (e.g., communication bottlenecks, technical debt across teams, managing changing priorities across a large group) along with proven Nexus practices to address them (like frequent cross-team refinement, continuous integration tooling, and coaching techniques). By relating these concepts to the Surge Pricing case, learners consider what metrics might indicate the Nexus’ success (e.g., faster pricing updates deployment) and share techniques to proactively manage a Nexus for the long run.
Propose a simple dashboard or set of metrics to monitor the health and progress of a Nexus over time. Think about what information would help the Nexus (and stakeholders) see how well value is being delivered and where improvements are needed.
View Examples

Nexus+ and Course Wrap-up

Session 8 120+
Explores scaling beyond a single Nexus and concludes the course. The concept of Nexus+ is introduced for situations with more than 9 teams (i.e., multiple Nexuses working together). Students learn the guiding principles for coordinating large-scale development with many teams, and discuss when it might be necessary to de-scale (simplify) instead of adding more layers. The course synthesizes all topics, tying back to how scaled Scrum remains Scrum even at very large scale. The Surge Pricing case study is wrapped up with a discussion on outcomes and what a full Nexus implementation would look like post-class. Finally, students prepare for the SPS certification assessment and identify next steps in their learning journey. The session includes a retrospective on the course itself and ensures that each participant has an action plan to apply their new knowledge in their organization.
Formulate a concrete action plan for applying what you’ve learned to your real-life context. Identify two or more changes or experiments you will try in your team or organization to improve scaling with Nexus practices.
View Examples

Catchup & After

Two weeks after completion, participants are invited to join a follow-up catch-up session designed to address any remaining questions, ideas, or challenges that have emerged since the training. This session provides an opportunity to reflect on your experiences applying the concepts learned in the course, share insights, and receive additional support.

* Assignments are part of our Immersive Training Programs, encouraging participants to apply their learning practically between sessions for a more hands-on experience.

Ready to bring this to your team?

Private delivery, fixed price, money-back guarantee. Tell us what you need and we'll put together a proposal.

Bring this in-house

If this isn't quite right for where you are

Not sure what would actually move the needle?

Most organisations don't need a course catalogue. They need a diagnosis. Tell me what's not working, who is involved, and what you've already tried. I'll tell you honestly whether training will help, and if so, what.

Start a conversation Browse programmes