It's an incredibly busy position if you're doing it right! I've had development teams of 4 - 20 reporting to me, and I think my responsibilities have generally included:
- Being the point of contact between Development and the rest of the organization, fielding questions about what can and can't be done, plus t-shirt sizing on effort
- Keeping tooling and technology unified (not ending up with one project each using Vue.js, React, Ember, Angular...)
- Keeping up standards (around code reviews, documentation, testing and alerts, end user and developer training)
- Thinking long term about how features, services and tools being built today can be re-used tomorrow
- Decisions about budgets and how to approach a project (use internal people or outsource to a vendor; field RFP responses; negotiate and get paperwork signed)
A lot of communication (inter-team and intra-team), budget work and "architecting" stuff is a reasonable summary, I think.
- Being the point of contact between Development and the rest of the organization, fielding questions about what can and can't be done, plus t-shirt sizing on effort
- Keeping tooling and technology unified (not ending up with one project each using Vue.js, React, Ember, Angular...)
- Keeping up standards (around code reviews, documentation, testing and alerts, end user and developer training)
- Thinking long term about how features, services and tools being built today can be re-used tomorrow
- Decisions about budgets and how to approach a project (use internal people or outsource to a vendor; field RFP responses; negotiate and get paperwork signed)
A lot of communication (inter-team and intra-team), budget work and "architecting" stuff is a reasonable summary, I think.