
In the Cross-Team Refinement, the Product Backlog is broken down. Cross-Team Refinement makes the Product Backlog transparent. In Scaled Scrum, however, Cross-Team Refinement is mandatory.ġ. To make this work transparent, Refinement is a helpful practice in Scrum. It is the only source of work carried out by Scrum teams.

Working on a product requires a Product Backlog. Caution: An icon does not represent a person but a responsibility. Overview of the Nexus Framework for scaling Scrum. We start on the left with the Product Backlog. We assume that the reader knows the Scrum Framework well and therefore we highlight just the elements add to the Scrum Framework. We will discuss the framework step by step and explain how the elements allow us to identify and eliminate dependencies across teams. This article provides an overview of the Nexus framework for practitioners who are already familiar with Scrum. They don't waste sprints training employees in new roles, implementing new processes or ways of working, setting up new infrastructure, or waiting to get support from external consultants. Organizations that choose to scale Scrum with Nexus are committed to continuously delivering value to their users. Scrum practitioners will find themselves using the Nexus framework because it extends Scrum only minimally. At its core, the Nexus framework helps multiple teams continuously integrate their work into a product. Only delivery will create value for the organization.Ĭontinuously eliminating dependencies and integrating all work is deliberate practice.

This effort is put into perspective if an integrated increment can be delivered at the end of each sprint.

We know that it takes discipline and effort to make dependencies transparent and eliminate them. These conflicts arise from interdependencies. Common sense tells us that there will inevitably be integration conflicts when teams work together on a single initiative. Scrum practitioners know that scaling Scrum is more than just a math problem. Benefits and advantages come from delivering more value in the same amount of time.

When scaling Scrum, we balance cost and effort with benefits and advantages.
