Skip to main content

Accountability for maximising the value of an integrated product in Nexus

Last post 01:30 pm September 4, 2020 by Dibbha Iyer
4 replies
10:02 pm September 3, 2020

In the book, "The Nexus Framework for Scaling Scrum: Continuously Delivering an Integrated Product with Multiple Scrum Teams", it is mentioned that 

(1) The Nexus Integration Team (NIT) is accountable for maximising the value of the integrated Product

(2) Product Owner is accountable for maximising the value of the Product

The reference to maximisation of value is not completely clear to me within the scope of NIT. Does (1) simply refers to maximising value by ensuring the integrated increment adheres to the common Definition Of Done for all scrum teams within Nexus? 

The true value of a Product goes beyond adherence to Definition Of Done which is the accountability of the Product Owner.


10:50 pm September 3, 2020

The Nexus guide mentions "The Product Owner is accountable for managing the Product Backlog so that maximum value is derived from the Integrated Increment created by a Nexus."

What's a bit confusing is what is the accountability of NIT vs the Product Owner in maximising the value derived from the Product / Integrated increment. Looking for some expert advice.


11:13 pm September 3, 2020

The Nexus Guide does state that:

The Product Owner is a member of the Nexus Integration Team.

Given this, I think it makes those other statements clear. By ensuring that the Product Backlog Items are clearly expressed and ordered in a way that maximizes value, the Product Owner is accountable for the value of the Product. However, the Nexus Integration Team is accountable for making sure that the work that is Done from each of the teams in the Nexus is fully integrated.

The way I see it, whenever you have multiple teams collaborating, there can be issues at the seams where the work of two or more teams comes together at some kind of boundary. The members of the NIT are accountable for making sure that those seams hold strong so that way the product as a whole meets the Definition of Done. The risk of quality issues at these seams is likely to be greater than in work done by an individual team, so they need special care.


05:53 am September 4, 2020

Does (1) simply refers to maximising value by ensuring the integrated increment adheres to the common Definition Of Done for all scrum teams within Nexus? 

In order to maximize value, work might need to be released at multiple points during a Sprint. This is true at any scale. These releases must be "Done" and satisfactorily integrated.

In other words, integration has to be timely enough not only for work to be "Done" but for value delivery to be successfully optimized. The roles on a NIT reflect this consideration.


01:30 pm September 4, 2020

Thank you Ian and Thomas. I understand now.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.