Re: Frontend/backend team with different technology stacks
| Newsgroups | gmane.comp.programming.extreme-programming |
|---|---|
| Message-ID | <CAF7qo6XfUnqex0ASXLF5rWK_zwQbGz5agmjQHX6PUmncbGJuKg@mail.gmail.com> |
On Sat, Feb 25, 2017 at 6:06 PM, Eb [email protected] [extremeprogramming] < [email protected]> wrote: > > > Hi Jan - > > >> >> >> >> Separating the teams smells with waterfall, but does joining the two >> groups together in a team outweigh the cost in this case? >> Does it make sense to split the frontend team and perhaps make the >> backend part more cross-functional towards the core of the system instead? >> Does anyone have successful experience with frontend+backend teams >> without full-stack developers (or teams with little shared knowledge in >> general)? >> >> > > > What is the cost of joining the two groups together? How many people in > total are we looking at that would be in this new team? > > Eb > > -- > blog: http://eikonne.wordpress.com > twitter: @eikonne > > > If a unified team is too large, two separate full-stack feature teams is better than one front-end and one back-end team. If testing is also separate (as I am imagining), then folding testers in as well makes the size even bigger, so multiple "feature" teams may be unavoidable. > _,___ >