- Server maintenance
- Hard-core development (applications, eCommerce, etc)
- Database maintenance and development
- Front-end design and architecture
- Content development
- E-mail marketing
- Enterprise applications
These separate departments don't necessarily play well together and are rarely looped in on each others' plans or projects, operating largely in their own silos. Is this how it should be or should they all be under one, centrally-managed group?
How are other "Web Teams" structured? Bear in mind I'm not talking about agency Web teams, I mean Web teams internal to a corporation or association. These teams work together over the long haul and may evolve over time. They're not the streamlined, project-focused teams you'd find in agency and members may wear several hats and manage several different Web sites like intranets, extranets, external sites, enterprise applications, etc. They may be called on to handle the minutiae and whims of departments throughout the enterprise.
I've yet to see an optimal model for this kind of team, but I will keep looking.