---
title: How does the Nexus framework encourage team independence and collaboration?
description: "The [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework encourages team independence and collaboration by maintaining a single [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/) and formulating a [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) [Sprint Goal](https://www.thescrummaster.co.uk/glossary/sprint-goal/) that unifies all Scrum Teams. By having a shared [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/), the framework ensures that all teams work from the…"
url: "https://www.thescrummaster.co.uk/docs/how-does-the-nexus-framework-encourage-team-independence-and-collaboration/"
updated: "2024-12-19"
category: Scaled Scrum With Nexus / Nexus Artifacts
---

# How does the Nexus framework encourage team independence and collaboration?

The [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework encourages team independence and collaboration by maintaining a single [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/) and formulating a [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) [Sprint Goal](https://www.thescrummaster.co.uk/glossary/sprint-goal/) that unifies all Scrum Teams. By having a shared [Product Backlog](https://www.thescrummaster.co.uk/glossary/a-scrum-artifact-that-consists-of-an-ordered-list-of-the-work-to-be-done-in-order-to-create-maintain-and-sustain-a-product-managed-by-the-product-owner/), the framework ensures that all teams work from the same set of priorities and understand the dependencies and requirements upfront. This shared understanding allows teams to work more independently during the Sprint, as they have a clear view of what needs to be done and can plan accordingly to minimise dependencies.

Furthermore, the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) [Sprint Goal](https://www.thescrummaster.co.uk/glossary/sprint-goal/) fosters collaboration by aligning all teams towards a common objective. This goal encourages teams to work together, share insights, and support each other to achieve the overall aim of the Sprint. The [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) [Sprint Backlog](https://www.thescrummaster.co.uk/glossary/sprint-backlog/) and Integrated [Increment](https://www.thescrummaster.co.uk/glossary/increment/) further reinforce this collaborative spirit by providing a transparent view of progress and ensuring that all work is integrated and meets the defined standards. This combination of independence and collaboration ensures that the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework effectively balances autonomy with the need for cohesive, high-quality deliverables.