Hintergründe zum Nexus

Software delivery is complex, and the integration of that work into working software has many artifacts and activities that must be coordinated to create a “Done” outcome. The work must be organized and sequenced, the dependencies resolved, and the outcomes staged.

Many developers have used the Scrum framework to work collectively to develop and deliver an Increment of working software. However, if more than one Scrum Team is working off the same Product Backlog and in the same codebase for a product, difficulties often arise. If the developers are not on the same collocated team, how will they communicate when they are doing work that will affect each other? If they work on different teams, how will they integrate their work and test the Integrated Increment? These challenges appear when two Scrum Teams are integrating their work into a single increment, and become significantly more difficult when three or more Scrum Teams integrate their work into a single increment.

There are many dependencies that arise between the work of multiple teams that collaborate to create a complete and “Done” Increment at least once every Sprint. These dependencies are related to:

  1. Requirements: The scope of the requirements may overlap, and the manner in which they are implemented may also affect each other. That knowledge should be considered when ordering the Product Backlog and selecting Product Backlog items.
  2. Domain knowledge: The people on the teams have knowledge of various business and computer systems. Their knowledge should be distributed across the Scrum Teams to ensure that the teams have the knowledge they need to do their work, to minimize interruptions between Scrum Teams during a Sprint.
  3. Software and test artifacts: The requirements are, or will be, instantiated in software.

To the extent that requirements, team members’ knowledge, and software artifacts are mapped to the same Scrum Teams, teams can reduce the number of dependencies between them.

When software delivery using Scrum is scaled, these dependencies of requirements, domain knowledge, and software artifacts should drive the organization of the Development Teams. To the extent that it does, productivity will be optimized.

Nexus Overview

Read on