Scaled Agile Framework features and components: http://www.scaledagileframework.com/features-and-components/
"Scaling with Feature vs. Component Teams" by Ken Rubin: http://www.innolution.com/resources/presentations/svaln-2015...
Re:Working remotely with 150+ people
by brilliantcode on Thursday January 05, 2017 @02:16PM
(#13330400)
This is gold. Thank you for posting that.
The more general term for these two structures are Functional vs Divisional structures. In the case of software engineering, a feature based team is a functional structure, and a "database team" (or "API team", or any other specific technical concern) is a divisional structure.
Re:Working remotely with 150+ people
by brilliantcode on Friday January 06, 2017 @11:54AM
(#13337837)
so why aren't more shops implementing a functional organization? It's still divided into front-end and back-end. What is the hindering factor and what tools would be a good fit for functional organization? AWS Lambda where people push their own backend along with the front-end thereby managing the full stack?
I have no idea why many engineering organizations insist on maintaining the artificial distinctions of "front end" and "back end". I think we do ourselves a disservice by labelling ourselves with those distinctions, but the entire industry seems to disagree with me.
To me it totally makes sense. Instead of the inevitable interdependency that arises through the component model, I can see that if teams were building features on their own than it could be completed at their leisure (in the budget & time affordable) without the multi-directional multi-disciplinary communication shitshow.
I wonder if there is an official name for this feature teams model or more guide on how to implement it.