This post provides guidance for conducting a Nexus Sprint Review, a key component of the Nexus Scaled Scrum Framework (or any scaled Scrum implementation) aimed at enhancing inspection and adaptation for large-scale agile development. Dissatisfied with existing guidance, I decided to share my insights on how to structure these reviews to facilitate integrated feedback on the work done by the Nexus (the team of teams). It outlines the replacement of individual Scrum Team Sprint Reviews with a Nexus-wide review focusing on the integrated increment and suggests employing a "Sprint Review Bazaar" to cater to stakeholders' diverse interests through a diverge-converge approach. This method encourages detailed inspections and feedback in breakout rooms, analogous to visiting booths at a science fair or car show, thereby increasing transparency and engagement. The post also provides a detailed sample agenda for a 2.5-hour Nexus Sprint Review, emphasizing the importance of flexibility and adaptation during execution.

It is important for Scrum practitioners to understand that there are a lot of myths and misconceptions about Scrum that they should be wary of when they are applying Scrum to their unique environment. In this article, we will debunk four common Scrum myths.

Nexus is the simplest, most lightweight framework available. Nexus can be considered an extension of Scrum because it preserves the simplicity that makes Scrum great.

Nexus es el marco ideal para escalar Scrum debido a que no modifica Scrum. Es ideal para quienes ya usan Scrum debido a que su adopción se basa en Scrum. Nexus mejora la visiblidad y transparencia de las dependencias entre los equipos, dependencias externas y de otro tipo que elevan el riesgo de no entregar incremento de producto integrado entre todos los equipos que escalan a través de Nexus. Un evento clave es el Nexus Daily Scrum donde participan al menos un integrante de cada equipo Scrum del escalamiento además del equipo de Integración, Product Owner y Scrum Master.

Backlog refinement is still a vastly misunderstood activity. There is no single approach to it and no time-boxed event. But why is that? And how to handle it? More on that in this article.

How can you scale in Scrum and what scaling patterns can you use?

Hi everyone! The new podcast episode is out, this time featuring Steve Porter as a guest. We are talking about tough but fair exams, origins of the Nexus framework, complexity behind scaling Scrum and much more. Hope you'll enjoy listening to it and find it useful. Feel free to check previous episodes as well.

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. 

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.