Here is an intriguing one: Multiple Agile groups across numerous related, yet separate items...

Howdy All,

I've looked for this, however I've just seen posts in regards to numerous Agile groups dealing with one item. My present circumstance is as per the following:

    I've ventured into a PO job in an organization that made the change from cascade to lithe around two years prior.

    Before my appearance, there was not an authority PO for the items that I am overseeing - the head of dev was working twofold time on her primary obligations and as the PO.

    At the present time, we have three unique items and three distinct dexterous groups working across those items (groups are not committed to a particular item).

    Of the three items, two have solitary accumulations and one has numerous (to represent the way that this item is profoundly redone for every client, however has a somewhat shared normal code base).

    We have three different group level accumulations also. The group accumulations contain stories that basically highlight the item stories.

    As of now, the arrangement upholds the accompanying requirements:

        Accommodating a strategy to consolidate work across the three items into group level ECRs that require work across various items for new elements/bugs/and so on

        Accommodating one work process on the item overabundances and an alternate, improved on work process in the group excesses. (item things require more beginning and in-progress surveys by a more extensive group)

        Forestalling one exceptionally huge build-up across three items (there are many things across the three items).

    As of now, the arrangement is hindering the accompanying requirements (these are the fundamental ones at any rate):

        Arrangement with other item groups in the organization, who have the essential arrangement of one group for each item, and in this manner one build-up per item.

        Undeniable level perspective on discharges that length numerous items (copy downs, detailing, include level data, and so on)

        The requirement for some form of mental soundness with respect to the Product Owner :)

Has anybody seen anything like this previously? Is it true that you were ready to join things into some reasonable interaction? Any thoughts on the most proficient method to make more significant level perspectives into the deliveries and to line up with the other item groups that utilization one build-up per item? I've depleted myself attempting to track down an answer for this one. I have an order to guarantee arrangement between my groups and the other item groups in the organization. I'm confused on the best way to achieve this.

Much obliged such a huge amount for any guidance you can give!