Posted on 4 Comments

Introducing Scaled Professional Scrum – Nexus

Scrum is a framework for complex systems development.

  • Professional ScrumScaled Scrum is any instance of Scrum involving more than one team creating and sustaining a product or system.
  • Scaled Professional Scrum is any instance of scaled Scrum that thrives on Scrum’s formal rules and roles, complemented by software development professionalism, and Scrum’s values and principles.

The Scaled Professional Scrum framework of provides guidance to organizations engaging in efforts to scale their product development done through Scrum. The framework cohesively integrates practices, experience and insights gained from efforts to scale Scrum worldwide, including the substantial efforts that involved Ken Schwaber and Jeff Sutherland, co-creators of Scrum.

At the heart of Scaled Professional Scrum is a Nexus, an ‘exo-skeleton’ for Scrum. A Nexus employs the Scrum process to inter-connect 3-9 Scrum Teams building one product.


The Scaled Professional Scrum framework holds 40+ practices. Each of these practices, if chosen and used against context, augments the operation of the Nexus.

The whitepaper “Scaled Professional Scrum – Rationale of the framework” (PDF) is now available through the website.

At the “Scrum Day Europe” event of July 2 in Amsterdam I introduced the Scaled Professional Scrum framework of and the Nexus in my opening keynote. Find the presentation at SlideShare. The recording of the session is available at YouTube.

4 thoughts on “Introducing Scaled Professional Scrum – Nexus

  1. […] of the post Introducing Professional Scrum – Nexus by Gunther Verheyen Scrum is a framework for complex systems […]

  2. Dear Gunther,

    Could you please clarify the Nexus artifact “Nexus Sprint backlog”? I understand that each team organizes his work for the sprint (on his own sprint backlog); so what’s the use of the Nexus sprint backlog?


    1. Scrum’s artifacts serve transparency. They make information visible. A Nexus Sprint Backlog serves to make in-Sprint dependencies across the teams visible to they can be managed.
      We have a Nexus Guide in the pipeline.

  3. Reblogged this on Technology Unplugged..

Leave a Reply