How can I scale Scrum? The Nexus Framework (Part 1) with Rich Hundhausen

Jan 26, 2024

Rich Hundhausen, co-creator of Nexus Framework, discusses scaling Scrum in a multidisciplinary organization. He emphasizes starting small, the role of product owner, and the importance of clear sprint goals. The episode explores challenges of dependency, introduces the concept of 'exoskeleton,' and emphasizes cross-team refinement in a scaled Scrum setting.

Ask episode

Chapters

Transcript

Episode notes

Introduction

00:00 • 2min

Challenges of Scaling Scrum in a Multidisciplinary Organization

02:30 • 5min

Scaling Scrum with Nexus Framework

07:19 • 7min

Importance of Clear Sprint Goals

14:18 • 8min

Exploring the Nexus Framework and Scaled Scrum Practices

21:53 • 3min

This week, your hosts, Dan Neumann, and Justin Thatil, welcome an external guest, Rich Hundhausen, software developer, Professional Scrum Trainer, and co-creator of the Nexus Framewokr for scaling Scrum. This episode is the first of two parts, in which they discuss the features of Nexus and when and how to implement it.

Listen to this episode for a description of Nexus, how it started, and why it was developed. Rich, Dan, and Justin also dive deep into the definition of scaling, what is considered done, and the Nexus goal. Stay tuned for part two!

Key Takeaways

Why do we have a Nexus Scaling Framework?

Rich started working with Ken Schwaber, co-creator of Scrum, in 2009. Together, they created Scrum.org, “The home of professionals.” They later became interested in Scaling according to the Scale Agile framework.

Are you really in a situation where you need to scale?

Rule number one when scaling is “Don’t.” Let your Team tackle the problems first. Always start small and add as needed.

What is Scaling?

Scaling is simply one product owner and backlog and multiple Scrum Teams. Everything you learned about Scrum for a single Team still applies at Scale with the Nexus. Additional features, such as the exoskeleton, are required for scaling.
The number one reason to build Nexus was for dependencies on different areas (not only technical). Refinement has been a proof practice at single-team Scrum, and at Nexus, it has become a required event called Cross Team Refinement.

What is the definition of Done?

Everyone at Nexus is a creative person, and these people are motivated when they have space to implement their creativity. All Teams should have autonomy, purpose, and the ability to master their actions. Each Scrum Team can have its definition of done, but it has to stay on top of the unified set of items that the other teams share.
The Nexus Goal: Do everything you committed to in the product backlogs.

Mentioned in this Episode:

“Shu, Ha, Ri” Episode of The Agile Coaches Corner.

Dan Pink’s books and TedTalks

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!