Skip to main content

Suite Integration

Last post 02:19 pm January 25, 2017 by Benjamin Williams
2 replies
05:27 pm January 12, 2017

Hi everyone,

I'm working on the PSM 1 as a professional development goal and have found Jeff Sutherland's book, 'The Art of Doing Twice The Work...' very helpful as an accompaniment to the scrum guide. Not having approached the Nexus material yet, I have a question about organizing teams for Integration development within a Suite.

We have a Suite of tools that can be licensed separately or together. In the latter case, they can be made to talk to one another very easily, out of the box. However, with custom configuration comes the need for someone to make extensions to the OOTB integration. My question is whether within Scrum that integration work should be treated as a separate product stream, with a devoted Dev team, or if the Dev teams for the two products doing the talking should have the skills to handle the integration themselves.

My feeling is that the answer will be context-dependent, based on the size of the integration work to be completed and the product to which a particular module belongs (If a process in Product A relies on a request to Product B, perhaps the story belongs to the Product A team, but if both products require heavy co-dependent configuration there may be a need for a separate team). Thanks for your help in clearing this up!


11:23 pm January 12, 2017

> My question is whether within Scrum that integration work should
> be treated as a separate product stream, with a devoted Dev team, or
> if the Dev teams for the two products doing the talking should have
> the skills to handle the integration themselves.

Presumably the stream would have no features to integrate and deliver, unless the product Dev Teams provided those features.

If so, it would be more sensible and desirable for the Dev Teams to integrate their work by themselves, and thereby collaborate to produce a valuable increment of release quality.

It's reasonable to have a "stream" which has oversight of integration matters, such as a Nexus Integration Team, but that group ought not to do any integration work if it can possibly be avoided.


02:19 pm January 25, 2017

Thank you, Ian.


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.