Suite Integration
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!
> 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.
Thank you, Ian.