Cross Functional Teams with Mobile (Android & IOS) + Web Developers

Last post 04:00 pm July 27, 2021
by Daniel Wilhite
3 replies
Author
Messages
07:12 pm July 26, 2021

Hi everyone,

A few months ago, we used to work with separate teams for Mobile and Web development.

Once the Product is the same, the company decided to put it together in one unique team, so now, I have teams composed by the following skills: (2 Android Devs, 2 iOS Devs, 3 Frontend/Backend Web Devs, 1 Designer, 1 Web QA, 1 Mobile QA) + a PO and a Scrum Master == 10 people.

Is this setup a common way other companies does, or usually, companies uses one separate team for IOS/Android and another one team for Web Dev?

Having this mixed skills teams, also let me have other problems, for example, if one of them (android, ios or web) have some problem, the others can't help to save the currrent sprint.

 

Thanks for support friends!

07:17 pm July 26, 2021

Just to explaing, I do not considered the PO and SM in the count, because they are shared with other teams.

02:20 am July 27, 2021

the company decided to put it together in one unique team, 

Why is the company deciding how to organize teams? Shouldn't management be encouraging these skilled professionals to find the best way of self-organizing themselves?

04:00 pm July 27, 2021

Does the team think this is an efficient method of organization?  What impediments are they seeing? What benefits do they see?

Since your "company decided" has anyone stated what benefits were expected?  What problems were being solved? Who raised those problems?  

Your post provokes more questions than answers for me. 

Is this setup a common way other companies does, or usually, companies uses one separate team for IOS/Android and another one team for Web Dev?

The answer to that question is "it depends on the company".  I've worked in companies that worked in both of these ways at the same time because it was left up to the Scrum Teams to decide the best manner to organize.  For one Product, they would organize in separate teams while with other Products it made more sense to be a single team.  I have never seen "the perfect way".