The Scaled Professional Scrum (SPS) workshop, presented by guest instructor Richard Hundhausen, shows you how to launch, structure, staff, and manage a large agile or Scrum project. In this two day workshop you will organize and simulate a scaled software development project to learn the infrastructure, tools, and practices needed for success. You will leave knowing how to scale Scrum in order to maximize the value of your software development initiative.

You will experience the Scaled Professional Scrum (SPS) framework as you work as teams, forming and managing a Nexus – the core development unit of SPS. This will help you understand the techniques, philosophies, and challenges that Ken Schwaber, Jeff Sutherland, and Scrum.org have learned through years of formulating and coaching scaled Scrum projects.

You will also be introduced to approximately 50 new and reformulated practices, which help the Nexus to operate more predictably. Several of these practices will be applied to the case study during the workshop. For example, practices include techniques for organizing your teams to maximize the initiative, Product Backlog refinement at scale, and scaling the Scrum events. You will take home some new experiments to apply when addressing situations when technical debt, domain knowledge, and test results impede forward progress. Students who complete the workshop will receive a password to take the intermediate level Scaled Professional Scrum assessment.

2-day workshop 

Highlights 

  • Scaled Scrum is still Scrum
  • How to deliver working software without scaling
  • Knowing when and why to scale (and descale)
  • The Nexus framework (roles, events, artifacts)
  • Organizing teams to form a Nexus while minimizing dependencies
  • Effectively staffing and leveraging the Nexus Integration Team
  • The Product Owner and Product Backlog at scale
  • Refining the Product Backlog to identify and minimize dependencies
  • Development practices for ensuring a “Done” Integrated Increment
  • Managing the Nexus from a reporting and financial impact perspective
  • Using decentralized coordination practices
  • Practices for distributed and offshore teams
  • Going beyond nine teams with Nexus+

Benefits

Attendees will learn:
  • The new roles, artifacts and events of the Nexus Framework
  • How to organize multiple teams working on the same software product to optimize productivity
  • How to detect and minimize cross-team and other dependencies
  • Practices that will help teams efficiently build an integrated software product
  • Techniques to detect irregularities and how to address them appropriately
  • Challenges in large-scale development initiatives and how to get back on track

Who Should Attend

This workshop is intended for development leads and managers and anyone else involved in formulating, participating or managing scaled Scrum product development. Organizations are encouraged to send a team of people that will be (or already are) running large Scrum initiatives. It is especially oriented to those who:
  • Already are effectively running small Scrum projects
  • Want to apply multiple Scrum teams to develop a large system or product
  • Managing scaled projects
  • Struggling with scaled projects

Overview

  • What do we mean by scaling?
  • Scaling Scrum vs. organizational transformation
  • What must be done prior to scaling
  • What must be done to continue scaling
  • Working software without needing to scale
  • Scaled Scrum is still Scrum

The Nexus

  • Roles, Events, and Artifacts
  • Nexus framework and Scrum framework differences
  • Forming a Nexus
  • Feature, feature set, and persona teams
  • Effectively adding teams to the Nexus
  • Organizing teams to minimize dependencies

The Nexus Integration Team

  • Purpose and role of the Nexus Integration Team
  • Roles on the Nexus Integration Team
  • Modes of working well
  • Common dysfunctions to avoid

Organizing Work

  • Impact mapping
  • Story mapping
  • The Product Backlog at scale
  • Product Backlog Refinement
  • Sizing and planning upcoming work
  • Cross-team refinement

Nexus in Action

  • Nexus Sprint Planning
  • Nexus Sprint Backlog
  • Nexus Daily Scrum
  • Nexus Sprint Review
  • Nexus Sprint Retrospective

The Product Owner at Scale

  • Product Owner role and responsibilities
  • Getting help from the product
  • Getting help from others
  • Product Backlog decomposition

Development Practices at Scale

  • The Integrated Increment
  • Continuous Integration
  • Continuous Delivery
  • Develop for Operations
  • The Definition of "Done" at scale

Managing the Nexus

  • Trust-driven planning practices
  • Value-driven reporting practices
  • Determining the financial impact of adding a team
  • Calculating the cost of delivery
  • Spending money in smarter ways
  • Descaling

Coordination at Scale

  • Relying on self-organizing teams
  • Decentralized vs. centralized facilitation
  • Offshore challenges at scale
  • Practices for distributed teams
  • Communities of practice
  • Shared architecture
  • Internal open source

Nexus+

  • The challenges of scaling beyond nine teams
  • When to add an additional Nexus
  • The Product Owner role in Nexus+
  • Horizontal vs. vertical scaling options
  • Platform engineering
  • Organizing Nexus+
  • Managing flow across Nexus+
This seminar is offered publicly but is not scheduled at this time.

Richard Hundhausen

Richard Hundhausen, a guest instructor for Construx, helps software teams develop better products by leveraging Scrum, ALM tools, and DevOps. He is a Professional ...