Scaled Professional Scrum and Nexus – Nexus Sprint Review

The Nexus Sprint Review is the scaled version of the Sprint Review event from the Scrum framework.

How does it work?

The objective of the Nexus Sprint Review is the same as the Sprint Review which it replaces. That is, to review the completed Increment and generate feedback based on new learnings and view points. This will be captured in the Product Backlog.

This feedback may take the form of new requirements that have been revealed by inspecting the recently created Increment. It may cause changes to previously created Product Backlog Items. It may lead to items being removed from the Product Backlog if it has now been recognised that these items will not generate the intended value.

It is still the responsibility of the Product Owner to manage the Product Backlog and decide which changes will be accepted and what impact these will have to the ordering the other Product Backlog Items it contains.

As with a Sprint Review, an effective Nexus Sprint Review should be collaborative session to show the new features and functionality that have been created by all the Scrum Teams in the Nexus during the current Sprint.

Who should attend?

  • Representatives of each of the Scrum Teams in the Nexus. The teams will decide within themselves who the most appropriate people to attend are. This may change over time and vary from one Nexus Sprint Review to another.
  • The Product Owner. As we are now operating in a scaled environment, the Product Owner will likely have specialist assistance from others to work closely with the Scrum Teams in the Nexus. These specialists should also attend the Nexus Sprint Review where there knowledge and view point will add value.
  • A Scrum Master. May be needed to facilitate this event. With the number of people and teams involved, the facilitation skills of the Scrum Master will be vital to ensure the event is carried out effectively and can be completed within a reasonable time box without confusion and conflict.
  • Stakeholders with an interest in the product and the functionality added in the current increment will attend to learn about and see what has been created and to give feedback.

What is the time box?

The Nexus framework suggests that the duration of Nexus events be guided by the length of the corresponding events in the Scrum framework. So for The Nexus Sprint Review the target for the time box would be 4 hours for a 1 month Sprint.

Inspection and adaption may lead to this being adjusted over time as required. Depending on the number of teams in the Nexus and the level new functionality being delivered, the time required may vary significantly between Nexuses.

When and where does it take place?

The Nexus Sprint Review should be held at a consistent time and place to ensure attendees have a clear expectation of when and where they need to be.

What else do I need to know?

The Nexus Sprint Review is one way in which Nexus framework does modify the underlying Scrum framework. Where previously each Development team would conduct a Sprint Review to show the completed increment to stakeholders, now we have a single higher level Nexus Sprint Review. The entire increment will be reviewed during this single event.

The Nexus framework does not preclude individual Scrum Teams inside the Nexus from holding Reviews to showcase the functionality that has been created by a specific team. These lower level reviews are not mandated by the Nexus framework in the way that the Nexus Sprint Review is. Remember that Nexus is a framework and inspection and adaption will lead you to develop the practices that will work for you in your unique situation.

The Nexus Sprint Review also doesn’t replace the need for the Product Owner to see the Product Backlog Items as they are being developed and becoming “done”. This is a good practice in Nexus just as it is in Scrum.

A traditional Scrum style review will likely no longer be suitable to show the work of multiple teams to a likely increased number of interested stakeholders. Scaled Professional Scrum introduces some practices to help run Nexus Sprint Reviews and deal with the additional complexity that comes with potentially larger audiences and increased functionality to show case in the session. I will write more about these in a future post when we come on to look at the 40+ practices that Scaled Professional Scrum introduces alongside the Nexus framework.

Next post: Nexus Sprint Retrospective –>

<– Previous post: Nexus Daily Scrum

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 6

  1. Hi Simon,

    I have a question about “Who should attend Nexus Sprint Review”.

    I think it makes sense to have “most suitable representatives of each of the Scrum Team” to capture feedback from Stakeholders. But my understanding from Nexus Guide is all Scrum Teams should participate.

    What are your thoughts on this? Would it be more accurate to say the following instead?

    “Nexus Sprint Review should be attended by all Scrum Teams and include all team members.

    In reality, it can be tough to coordinate this large number of people, so each Scrum Teams should nominate a smaller number of appropriate people to represent the team when capturing feedback from the stakeholders. The teams will decide within themselves who the most appropriate people to attend are. This may change over time and vary from one Nexus Sprint Review to another.”

    Thanks,

    Tony
    ———————————
    Below are the sources:

    A) Here the article stated: “Representatives of each of the Scrum Teams in the Nexus. The teams will decide within themselves who the most appropriate people to attend are. This may change over time and vary from one Nexus Sprint Review to another.”

    B) Nexus Guide says: “All teams meet with the Product Owner to review the Integrated Increment. Adjustments may be made to the Product Backlog.” and “… It may not be possible to show all completed work in detail. Techniques may be necessary to maximize stakeholder feedback. ”

    e.g. Nexus Guide specifically stated, “All teams meet with Product Owner …” dhttps://gyazo.com/5983be20ffec3d416018cd86798708bd

    1. mm Post
      Author

      Hi Tony,

      Interesting question. I would agree that all Scrum Teams in the Nexus must attend the Nexus Sprint Review. However, it may not be possible or sensible for ALL members of ALL teams to attend. So for me, appropriate representatives of each team must attend. When I use Nexus this is usually all or most members of each Scrum Team in the Nexus. This maximises the opportunity to inspect the Increment and adapt the Product Backlog.

      Events like this at scale will need special techniques to be successful. Scaled Professional Scrum extends Nexus to introduce some of these. They aren’t covered in the Nexus Guide.

      Regards

      Simon

      1. Hi Simon,

        Thank you for the response. I just want to clarify the event we are discussing is “Nexus Sprint Review” – not “Nexus Sprint Retrospective”.

        I do agree with your comment about “all Scrum Teams must attend the Nexus Sprint Retrospective”.

        My confusion is about “Who should attend Nexus Sprint Review” in Nexus Guide and this article.
        Screeenshot: https://gyazo.com/8765a148bd5950450fa1e9f44ef776b3

        My guess and interpretation of the Nexus Guide is

        “All teams should attend and participate Nexus Sprint Review, but events like this at scale will need special techniques to be successful.

        For example, most suitable representatives of each of the Scrum Team should attend and capture the feedback from stakeholders. And then discuss and work their own each Scrum Teams. ”

        What do you think? Can you please help clarifying my understanding?

        Thanks!

        Tony

        1. mm Post
          Author

          Apologies. My comments applied to the Nexus Sprint Review (even though I said Retrospective). I have updated my comment to prevent future confusion.

          Your additional comment here is valid. You should also re-read my previous comment which explains it as clearly as is possible in this forum.

  2. Hi Simon,

    Thank you for the clarification! Your explanation helped me to have a better understanding of Nexus Guide’s statement.

    Specifically, I misread and mixed the definition of “all teams” and “all members of all teams”. Now, this statement naturally makes sense to me and it aligns with your explanation in the article.

    Thank you!

    Tony

    1. mm Post
      Author

Leave a Reply

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