These dependencies are often caused by mismatches related to: Nexus helps to make transparent dependencies. The Nexus Framework helps teams solve common scaling challenges like reducing cross-team dependencies, preserving team self-management and transparency, and ensuring accountability. It does this by reducing the complexity that those teams encounter as they collaborate to deliver an integrated, valuable, useful product Increment at least once every Sprint. The goal of Nexus is to scale the value that a group of Scrum Teams, working on a single product, is able to deliver. It minimally extends the Scrum framework only where absolutely necessary to enable multiple teams to work from a single Product Backlog to build an Integrated Increment that meets a goal.Īt its heart, Nexus seeks to preserve and enhance Scrum’s foundational bottom-up intelligence and empiricism while enabling a group of Scrum Teams to deliver more value than can be achieved by a single team. Nexus builds upon Scrum’s foundation, and its parts will be familiar to those who have used Scrum. The Nexus framework defines the accountabilities, events, and artifacts that bind and weave together the work of the Scrum Teams in a Nexus. A Nexus has a single Product Owner who manages a single Product Backlog from which the Scrum Teams work. Table of ContentsĪ Nexus is a group of approximately three to nine Scrum Teams that work together to deliver a single product it is a connection between people and things. As with Scrum, such tactics vary widely and are described elsewhere. Each element of the framework serves a specific purpose that is essential to help teams and organizations scale the benefits of Scrum with multiple teams working together.Īs organizations use Nexus, they typically discover complementary patterns, processes, and practices that help them in their application of the Nexus framework. This Guide contains the definition of Nexus.
Doing so covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
Nexus does not change the core design or ideas of Scrum, or leave out elements, or negate the rules of Scrum. The Nexus framework inherits the purpose and intent of the Scrum framework as documented in the Scrum Guide. It builds upon Scrum, extending it only where absolutely necessary to minimize and manage dependencies between multiple Scrum Teams while promoting empiricism and the Scrum Values. Nexus is a framework for developing and sustaining scaled product delivery initiatives. Product delivery is complex, and the integration of product development work into a valuable product requires coordinating many diverse activities. The Definitive Guide to Scaling Scrum with Nexus January 2021
0 kommentar(er)
