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

Description:

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 Framework 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!

Share this content

Speakers

Dan Neumann

Principal Enterprise Coach

Dan Neuman is the Director of the US Transformation and Coaching practice in the Agility guild. He coaches organizations to transform the way they work to achieve their desired business outcomes.

With more than 25 years of experience, Dan Neumann is an experienced Agile Coach with a deep knowledge of Agility at the team and organizational levels. He focuses on achieving business outcomes by shifting both mindset and practices, resulting in a disciplined, yet practical approach to solving problems.

10 Things a Java Developer Should Learn These Days

We are halfway into the year and, looking back at what the last 2 years of the COVID-19 pandemic left us, we can say that the advancements on technology and all the different languages, frameworks and development tools have not disappointed us and even in many cases have overtaken us. It doesn’t seem that long since Java 8 was released more than 8 years ago and, although it is true that today the latest version is Java 18, we must remember that there are still many companies stuck with Java 8 and even a few with Java 1.4 a 1.6 and a few other legacy frameworks.Because of this great advance in programming languages and frameworks in recent years, many programmers could feel overwhelmed due to the large number of updates that we are exposed to in our industry. However, we have begun to see very marked patterns in different industries, and we believe it is important to mention what are the 10 things that every Java programmer should learn.

6 min read

August 25, 2022

Succeeding at Cost Takeout – Improving Cost Management Strategy

The cost takeout is a strategic initiative that can help your company become more efficient. The goal of the initiative is to determine ways to reduce expenses without sacrificing quality, speed or customer satisfaction. A successful cost takeout requires an accurate understanding of where costs arise in your business process and how those costs can be reduced through new technologies. In this guide, we’ll look at some of the most common drivers of costs in IT departments and explain how you can identify them within your own organization’s processes.Cost drivers are the factors that cause your costs to increase. They’re different for every business, but you can identify them by asking yourself: “What makes my costs go up?”

10 min read

February 7, 2023

Agile Podcast: Agile Coaches' Corner