Skip to main content

Optimal scrum team structures for multi channel development

Last post 09:46 pm December 28, 2021 by Visweswar Bulusu
5 replies
01:34 pm December 27, 2021

Hello - Needed some suggestions on how best to structure scrum teams on multi channel app development teams. If we have feature development going on for web and mobile (iOS and android),  how best to structure multiple scrum teams ?

Option 1:   Organize by Channel - Separate teams for separate channels - each team develops features for their respective channel

Option 2:  Organize by Features -  Separate teams by product features - each team develops for all channels for their respective features

Any other options ?

Thanks,

Viswes


04:48 pm December 27, 2021

Firstly, the members of the Developers accountability should be allowed to self-manage themselves, which includes self-organisation.  No one other than themselves should be allowed to tell them how to form their teams. 

Secondly, if these channels are for the same product, then there should only be one PO and one Product Backlog, which all teams will select PBIs from in order to help them achieve their Sprint Goals, allowing the PO to optimise product value from their work. 


05:26 pm December 27, 2021

Needed some suggestions on how best to structure scrum teams on multi channel app development teams. 

I'm not sure you do. Rather, the challenge you appear to be facing is more one of how to identify products, so value can then be clearly accounted for by a Product Owner.

Establish transparency over this first.

  • What does it mean to have valuable products,
  • What are they here, and
  • Who is accountable for them?

Then encourage team members to self-organize so Done increments of those products will be created every Sprint.


07:30 pm December 28, 2021

Thanks Scott and Ian for your responses.

Scott - Yes the channels (web, mobile) are for the same product and we will go with single PO and backlog.

Ian - To answer your points,  in this case it is the same product which they are rolling out via multiple channels / interfaces.  The same sponsor and PO is accountable for all channels.  Yes agree with both of you that the team members need to be the ones deciding the team structure and they need to be empowered.  However, at this point, we are submitting a proposal to customer and we need to make a suggestion on the team structure at this point (though the team will come into the picture later when we execute the project) 

Thank you ! 

cheers,

Viswes

 

 

 


07:54 pm December 28, 2021

However, at this point, we are submitting a proposal to customer and we need to make a suggestion on the team structure at this point (though the team will come into the picture later when we execute the project)

I suggest you bring them into the picture now, so they can advise you, and to ensure nothing is offered which they are unable to commit to.


09:46 pm December 28, 2021

Agree with you Ian.  Have involved senior leads for the development.  However, we are not guaranteed we will be awarded the project. Hence - due to practical considerations - am not able to bring in most of the team.  Have involved developers who have executed similar projects in the past.  Thank you ! 


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.