Back to Forum

Nexus+ : Integration teams collaboration

Last post 01:35 pm May 17, 2017 by Ian Mitchell
3 replies
Jean-Marie Vandamme
03:58 pm May 16, 2017

Hi, 

I have a question about Nexus+ and integration teams. We manage 2 nexus with a total of 17 teams. Each nexus has its own NIT.  The difficulty we are facing is that there are still a lot of dependancies between products integrated by the 2 Nexus. So, how can we organize and improve the collaboration between the two NIT ? Is it recommended to have a dedicated NIT at Nexus+ Level ?  What is your advice ? Thx.

jm 

Ian Mitchell
06:45 pm May 16, 2017

How many products, product backlogs, and product owners are there in this case?

A NIT can be expected to assure the integration of a single product.

Jean-Marie Vandamme
07:30 pm May 16, 2017

In fact, there only one product, with one product backlog. This product was splitted in 3 sub-products (a backend+api and two frontend) with 3 product owners. We use a rich but technically complex eCommerce framework. So, unfortunately, we have to deal with technical constraints. At the beginning we have only one nexus but with too much teams. It's why we splitted in two nexus. 

About NITs, one assures integration of on sub-product. Other assures integration of the two others sub-products. They need to collaborate at nexus+ level. 

Ian Mitchell
01:35 pm May 17, 2017

If you've split a product into constituent pseudo-products by layer (i.e. back-end and front-end), then it is hardly seems surprising that teams face extensive dependencies. What is the reasoning behind this? Why are these so-called "sub-products" (in reality, it would seem layers) thought to be real products around which a Nexus or Nexus+ could organize?

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.