Re: Frontend/backend team with different technology stacks

Thank you all for your replies, I will keep them in mind as we go forward!


Alexander:
> My feeling is that you already have a bias towards splitting the team


I was actually a proponent of a joint feature team.
The whole story is that I was tasked with making such feature team work together after the previous attempt rather failed. I just wanted a competent third opinion on some of the counterarguments to make sure we are really heading in the right direction.


Steven:
> I am curious how your team(s) are handling testing.


Not sure, as I'm not yet part of the team. I suspect the cycle is: FE provides design and requirements -> BE develop & test their part -> FE develop & test their part -> iterate.


> Ron:
> how to go in very small slices, and how to build up the design incrementally so that designs are built rapidly instead of in advance. 


This advice caught my attention in particular. One of the main arguments was constantly getting off-cycle between the two groups. I believe thiner slices should mitigate this problem.


> The team would have to want to learn to work that way, of course. What’s their view?  


They are willing to learn but skeptical because previous attempts did not work (for 1-2 years).


Another argument against feature team was that the frontend guys do designs/UX for other teams too (due to shortage of FE manpower). My understanding is that it makes sense to exclude some concerns from a feature team if they are cross-cutting, such as infrastructure. I'm a little worried that this feature cross-cutting UX will impair our focus, but hopefully we'll learn to deal with it.


Best regards
Jan


------------------------------------
Posted by: Jan Michelfeit <[email protected]>
------------------------------------

To Post a message, send it to:   [email protected]

To Unsubscribe, send a blank message to: [email protected]

ad-free courtesy of objectmentor.com