---
title: "How does the Nexus framework determine the duration of Cross-Team Refinement events?"
description: "In the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework, the duration of Cross-Team [Refinement](https://www.thescrummaster.co.uk/glossary/refinement/) events is guided by the length of corresponding events in the Scrum framework, though there is no directly related event in Scrum. Consequently, the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework allows for flexibility in deciding…"
url: "https://www.thescrummaster.co.uk/docs/how-does-the-nexus-framework-determine-the-duration-of-cross-team-refinement-events/"
updated: "2024-12-19"
category: Scaled Scrum With Nexus / Nexus Events
---

# How does the Nexus framework determine the duration of Cross-Team Refinement events?

In the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework, the duration of Cross-Team [Refinement](https://www.thescrummaster.co.uk/glossary/refinement/) events is guided by the length of corresponding events in the Scrum framework, though there is no directly related event in Scrum. Consequently, the [Nexus](https://www.thescrummaster.co.uk/glossary/nexus/) framework allows for flexibility in deciding the appropriate duration for these events. Over time, inspection and adaptation may lead to adjustments in the amount of time allocated.

The complexity and dependencies inherent in the [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/) dictate the number, frequency, duration, and attendance of Cross-Team [Refinement](https://www.thescrummaster.co.uk/glossary/refinement/) events. The greater the complexity and dependencies, the more [Refinement](https://www.thescrummaster.co.uk/glossary/refinement/) is needed to remove them. Consistent and regular scheduling of these events within a Sprint helps ensure that [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/) items are ready and selectable with minimal dependencies during [Sprint Planning](https://www.thescrummaster.co.uk/glossary/sprint-planning/).