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.
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.
Scrum.org Professional Scrum Courses June 201821st June 2018
Scrum.org Professional Scrum Courses May 201821st June 2018
Scrum.org Professional Scrum Courses April 20181st May 2018
Share this Post