Scaled Professional Scrum

The Scaled Professional Scrum for Practitioners (SPSP) Workshop will show you how to launch, structure, staff, and manage a large agile or Scrum project. In this 2-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.

In SPSP, you will be introduced to the Scaled Professional Scrum (SPS) framework and walk through forming and managing a Nexus, the core development unit of SPS. This experience 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.

Scaled Professional Scrum helps teams scale with minimum waste and as much productivity as possible. SPS drives to the heart of the scaling issue – complexity caused by the dependencies between the increased parts. Scaled Professional Scrum is a product for those who want to scale with minimum waste and as much productivity as possible. It will fill a gap for those who are having trouble setting up and running their projects, programs, and releases.

It consists of the Nexus™ framework and approximately 40 practices which cause the Nexus to operate predictably. The Nexus is the exoskeleton of scaled Scrum that integrates and brings coherence to the work of up to 9 Scrum teams. It creates a communication pathway that identifies and resolves dependencies. It builds on the existing Scrum framework and values. The result is an effective development group of up to 100 people using best industry practices to create solid increments. For larger initiatives, creating product families or interoperating functional units, we create Nexus +, a unification of more than one Nexus.

Learning Objectives:

• The new roles, artifacts and events you need to scale successfully
• How to organize several teams working on the same product so efforts and productivity are optimized
• Practices that will help your teams build an integrated software product efficiently
• Techniques to detect irregularities and how to address them appropriately
• Challenges you may encounter in large-scale development initiatives and how to get back on track

Section 1: Nexus, an introduction

• What is the Nexus
• Nexus roles, events, and artifacts
• Nexus integration team
• Nexus sprint retrospectives
• Related practices

Section 2: Nexus in Action

• The Effect of dependencies
• Feature teams
• Nexus sprint planning
• Product backlog refinement in the Nexus
• Story mapping
• Related practices

Section 3: Mapping the Nexus

• Reporting progress
• Improving performance
• Adding more teams
• Nexus health checks
• Related practices

Section 4: Agile Planing

• Determining the next product generation a product
• Determining a business model
• Driving a product backlog from a vision
• Value driven backlog creation
• Creating good stories
• Estimating using story point

Section 5: Nexus+, scaling the Nexus

• Large scale development
• Nexus+
• Scaling options
• Related practices

Section 6: Closing and Questions

• Specific questions on agile in context of your organization

Attendees make the most of the class if they:

• Have a solid understanding of Scrum either through working with a Scrum Team or through taking a professional scrum master or similar course.
• Have an understanding of development techniques, tools, and practices needed to sustain large scale development.
• Attempted the scrum practitioner open assessment located at scrum.org.

Applied learning targeted at development leads and managers and anyone else involved in formulating, participating or managing a large scale Scrum product development – multiple teams developing one integrated product. Organizations are encouraged to send a team of people that will be (or already are) running large Scrum initiatives. It is especially targeted toward those who already are effectively running small Scrum projects and want to apply multiple Scrum teams to develop a large system or product, or those who are currently managing scaled projects.