Scaled Professional Scrum and Nexus – The Nexus Integration Team

The Nexus Integration Team is a new team introduced by the Nexus framework.

The Nexus Integration Team is accountable for ensuring that an integrated Increment is produced at least every Sprint.

Who is part of the team?

The Nexus Integration Team is a Scrum Team that consists of:

  • The Product Owner – Responsible for ensuring value is delivered from the work carried out by the Nexus. As with the Scrum framework they do this by managing the Product Backlog
  • A Scrum Master – Has overall responsibility for ensuring the Nexus framework is understood and enacted.
  • Nexus Integration Team Members – Responsible for ensuring that an integrated Increment is produced at least every Sprint

Nexus Integration Team members will consist of software professionals who are skilled in the use of tools and technologies to make scaled software development possible. This may include, but is not limited to, techniques such as continuous integration, automated testing and environment management.

Members of the Nexus Integration Team may also work on the Scrum Teams in the Nexus. However, where they do priority must be given to their work as part of the Nexus Integration Team. This is to ensure that the work to resolve issues that affects many teams takes priority.

Composition of the Nexus Integration Team may change over time as the needs of the Nexus develop and change.

What Does The Nexus Integration Team Do?

Activities of a Nexus Integration Team may include coaching, consulting and raising awareness of dependencies and common issues faced by multiple Scrum Teams. They will increase the awareness, understanding and knowledge of the other Scrum Teams in development, architectural and infrastructural standards required to ensure the development of quality integrated increments.

The Nexus Integration Team will take ownership of integration issues. However, they may not necessarily do the work required to resolve these when they occur. They may work with 1 or more Scrum Teams to help them resolve issues around integration. At other times they may deliver tools and technology to help make integration run more smoothly.

They may perform work from the Product Backlog themselves. This would likely be Product Backlog Items that effect multiple Scrum Teams or are related to integration. For example they may implement a continuous integration tool and then introduce and train the Scrum Teams in the Nexus on its effective use.

Next post: Product Backlog Refinement –>

<– Previous post: Nexus Artefacts

Index – Scaled Professional Scrum And Nexus – The Definitive Guide

mm

The Scrum Master is Simon Kneafsey. Simon is a Professional Scrum Trainer with Scrum.org, the home of Scrum run by Scrum co-creator, Ken Schwaber. Simon offers Professional Scrum Certification training courses globally and works with clients to introduce Scrum to their organisations.


Share this Post

Comments 2

  1. Thanks for the information…I have a question for the Nexus Integration Team…Who has Overall responsibility for ensuring Nexus Sprint Retrospectives occur ?. The Nexus Integration Team or the Scrum Master on the Nexus Integration Team ?
    Anyway, can Any Scrum Master for the Nexus teams or the development teams can be sure that the Nexus Sprint Retrospectives occur ?
    Thanks

    1. mm Post
      Author

Leave a Reply

Your email address will not be published. Required fields are marked *