Community Blog

10+ years of helping organizations scale Scrum from one team to 500+ teams has taught me one thing - most practitioners abandon the scientific principles and core values of Scrum in their pursuit of scaling Scrum. To many of these practitioners, Scaling Scrum is a whole another ball-game to which Scrum principles and values do not apply.

Scrum of Scrums describes one of the first approaches to scale Scrum and is often confused with Nexus Daily Scrum.  

How effectively a Nexus works depends on its ability to eliminate dependencies. Eliminating dependencies simplifies integration. Scrum Masters who efficiently perform cross-team refinements save time. Saving time saves money. 

When scaling Scrum, we balance cost and effort with benefits and advantages. Costs and effort come from adding teams. Benefits and advantages come from delivering more value in the same amount of time. 

I've been asked several times now about Nexus and SAFe - what are the similarities, differences, etc. If you’re not familiar with either Nexus or SAFe I recommend taking a look at the Nexus Guide and the SAFe whitepaper first.

Der Nexus Guide -- der Leitfaden zur Skalierung von Scrum -- wurde aktualisiert! Der Nexus Guide 2021 enthält weniger Vorschriften, Erklärung von spezifischer Terminologie und einen Ergänzender Theorieabschnitt.

How this popular and empowering liberating structure can be used for retrospectives and increasing organizational agility. But can you Open Space be used in a virtual set-up?

Many thanks to attendees at my PAL-E workshop in London on 26-27 October who reviewed & debugged my change story for "what is organizational agility?"

For executives and for change agents who deal with executives in large contexts ...

This article discusses the growth of agility for customer-facing products with 3+ teams, probably tens of teams with Nexus and/or LeSS.

A friend sent me an e-mail, asking me to summarize Nexus and the Scaled Professional Scrum class. Here's the gist of what I sent in return.

THE (MIXED) BLESSING OF NEXTGEN REWRITES  About 10 years ago, I experienced the mixed blessing of being part of yet another nextgen rewrite project.

Scaling Scrum. Agile at Scale. Enterprise Everything. Everyone is using the Scaled Agile Framework SAFe.  Scaling, Scaling, Scaling. If you’re working in product development, you’ve probably had a few conversations on this topic.

This blog is the feedback on Scaled Professional Scrum using Nexus Framework and over 50 practices from the participants who attended my SPS workshop in India.

Nexus and SPS have been online for a while. There are organisations around the world giving it a try and, of course, there are questions about how to set up and begin using Nexus in an organisation.

Nexus and SPS have been online for a while. There are organisations around the world giving it a try and, of course, there are questions about how to set up and begin using Nexus in an organisation.

After downloading and studying the Nexus guide, you have questions about how the Nexus Integration Team actually works, so here are some keys to understand the role and its fit within the Nexus.

After downloading and studying the Nexus guide, you have questions about how the Nexus Integration Team actually works, so here are some keys to understand the role and its fit within the Nexus.

A lot of people talk about scaling Agile. It’s all the rage nowadays. Everyone wants to scale Agile. But what does that actually mean? What does it imply? What are the underlying assumptions?

Before I begin, I have to make sure you’re not fixed on a misconception. The Daily Scrum is not a status meeting, nor a report back to the team. It’s a planning event.

Scaled Professional Scrum is based on unit of development called a Nexus. The Nexus consists of up to 10 Scrum teams, the number depending on how well the code and design are structured, the domains understood, and the people organized.

History

EMBARRASSING DISCOVERY