There are many good ways to organize your technology department. This article presents some of them. It is written for a CTO or VP Technology leading a medium size department looking for suggestions on organizing or reorganizing your Digital (Web, Mobile) technology department. It is best suited for you if your organization has the following characteristics:
- You manage software engineering, implementation and technology operations for 3 or more digital brands.
- Yours is a medium size technology department with somewhere between 20 to 100 technology staff.
- Internal corporate IT functions such as desktop support, telecommunications services and internal business systems are beyond the scope of this article.
The Venn diagram below presents one model of organizing your department into 3 sub-departments.
Some CTOs in smaller companies organize their technology departments as 2 sub-departments: Software Engineering and Technology Operations. Software engineering is the function that is responsible for developing and implementing Web & Mobile application software. Technology Operations is responsible for running, maintaining and supporting the Web applications.
If you operate 1 or 2 digital brands (Web sites), having these 2 sub-departments is a good approach. For 3 or more Web sites, organizing Software Engineering into Site Engineering and Platform Engineering has some benefits.
Site Engineering is focused on working on the Web sites’ direct projects. Its work includes
- Small and large projects for adding or changing functionality on the Web sites
- Bug fixes on the Web site applications
Platform Engineering is typically smaller than the other two organizations and typically includes functions like:
- Architecture across sites
- Shared applications across sites
- Common libraries across sites
- Research & Development (R&D)
Technology Operations includes functions such as:
- Systems & Applications Administration
- Infrastructure Management
- 24×7 Tech Support
- Builds & Configuration
- Release Management
- Testing & Quality Assurance (QA)1
- Technical Analysis
- Technical Project Management
- Budget Management
These three departments have purposeful overlap of responsibilities as illustrated in the Venn diagram above. That helps minimize the chances of the departments becoming silos with walls between them. For success, it is important that your entire department functions as one integrated unit. Some shared goals & responsibilities are required for mutual success.
DevOps2 is a set of processes, methods and systems for communication, collaboration and integration between departments for Development (Applications/Software Engineering) and Technology Operations. Its purpose is to facilitate meeting business goals by producing good quality software products and services in a timely fashion. It is where development methodologies (such as agile software development) occur in an organization with separate departments for Development, Technology Operations and Quality Assurance. Development and deployment activities that need deep cross-departmental integration with Technology Support or QA require intimate multi-departmental collaboration.3
To make this work, you need 3 directors who head up these departments who work well together, collaborate often and are not sensitive about their turf. They should know that a successful technology manager is not an individual-only contributor, but a great team player with peers. They should have strong goodwill among each other and welcome each other to work directly with their teams. Such a collaborative team is essential.
Article Updated: September 25, 2010
- QA can also be set up as an independent department. [↩]
- WikiPedia entry on DevOps [↩]
- Article: What is DevOps? [↩]
Great insights. Would love to repost in DIGIDAY.
Melinda, glad you liked the post. You are welcome to repost on DIGIDAY.
You must log in to post a comment.