Take away the "(usually those the management like, rather than actual competence or knowledge)" part and the structure makes good sense to me.
Who else would ensure developers are making stuff in a way that caters to the business case? I mean it's not feasible to include all developers in every business decision and related meeting?
I've tried not having teck' leads, and the anarchy was really hard to deal with.
I would make a feature, and include a cool tool, so would my mate, and all of the sudden we had an application soup that was impossible to maintain.
Take away the "(usually those the management like, rather than actual competence or knowledge)" part and the structure makes good sense to me.
Who else would ensure developers are making stuff in a way that caters to the business case? I mean it's not feasible to include all developers in every business decision and related meeting?
I've tried not having teck' leads, and the anarchy was really hard to deal with.
I would make a feature, and include a cool tool, so would my mate, and all of the sudden we had an application soup that was impossible to maintain.
Also, the bigger the team the worse the soup... :I