When you work in larger teams, or perhaps even a whole department organized in several teams, do you specialize your team members or stay all-rounded?
And if you specialize, how do you organise your teams?
Examples could be that there are specialized developers, testers, scrum masters/coaches and other roles.
This could be within one team or perhaps you have specialized teams working on the portfolio of applications that your department manages.
In general, it's more likely to find an all-round Mendix developer compared to traditional development. Nevertheless, I do see that specialized knowledge for certain topics is needed for a bigger or non-standard Mendix practice.
As I see it, the power lies in the ability to use skills and knowledge when needed, without keeping it unnecessarily occupied within an app or project. For example; a member specialized in UX or front-end work should not be tied to one app only. If you fascilitate this member to move from app to app, the specialized skills can be utilized effectively. Additionally, including other team members in such collaboration should be mandatory if you would ask me. As there is a need in another app, it's likely that the Mendix practice soon needs more of this skill. By enabling other team members to tap in to this knowledge, you'll end up with more T-shaped members over time. This can be applied to topics like testing, automation, cloud, certain integrations, etc.
In short: all-round by default, specialized/T-shape in addition. By aiming for many all-rounders by default, it's more likely that this group is able to recognize the need for specialization when needed.