Developers really are different. From their roles and responsibilities to their placement in the organizational structure, developers are often the "odd group out". You can't even necessarily include them in the term "IT" because development teams swing on pendulums between being a part of IT and being a part of the business.
Even while DevOps as a cultural shift begins to take root, most organizations remain functionally organized into what are not so fondly referred to as IT silos. In our State of Application Services 2019 research, we found that nearly half of all respondents (46%) were still organized in "single function teams" a la "Network", "Server", "Storage", and "Security". More than one-third (37%) were working on combined operations teams better suited to embracing and applying DevOps principles and approaches to application delivery and deployment. Just 15% were working on small, cross functional teams based on business units or company products.
Structure matters, because it in part defines your purpose and priorities. That, in turn, determines the metrics by which success is measured. Siloed organizations mean siloed metrics. We can see that in our NetOps and DevOps survey from last summer. We saw significant differences in how teams were measured based on structure. For example, the most common metrics across all team types and roles were:
- Network uptime (60%)
- Application uptime (56%)
- Process optimization (40%)
- Mean time to resolution (39%)
But when we break that down and look at metrics based on team types, we see that the more collaborative - a.k.a. DevOps-like - a team structure is, priorities shift.
| Single Function | Combined Ops | Cross Function |
Network Uptime | 67% | 54% | 50% |
Application Uptime | 53% | 58% | 61% |
Process Optimization | 34% | 45% | 45% |
Mean time to Resolution (MTTR) | 43% | 30% | 44% |
Now, how does the metrics by which you're measured relate to application services? Quite a bit, actually.
If your primary focus is network uptime, you're going to work toward that and deploy services that serve that goal. The same for application uptime. If that's your priority, you're going to take availability services a lot more seriously than the folks being measured on deployment frequency.
We can see the impact of a largely "single function team" respondent base in the deployment plans for application services in our research. It is more evident when we categorize the application services by what they provide for applications - security, performance, identity/access, availability, and mobility.
These results reflect the impact of single function team metrics. Developers are concerned primarily with availability - which often includes specific performance goals - and plan to deploy those application services that support both availability and performance. Likewise, NetOps are focused on those application services that support network uptime by optimizing, scaling, and protecting the network protocols applications rely on.
Team structure matters. Not just because of the need to encourage a more collaborative culture, but because of the way it impacts decisions - including technology choices. Diverse goals lead to friction and frustration. It's one of the reasons we see application services like load balancing that are traditionally deployed and operated by NetOps being arrogated by DevOps and deployed as part of the application. Because in organizations with single function team structures, application uptime is a priority for developers but not for NetOps.
To really capitalize on DevOps, team structures - and the metrics by which they are measured - must shift toward more collaborative models and away from traditional, single-function teams.
Because silos belong on farms, not in IT.
About the Author
Related Blog Posts
The everywhere attack surface: EDR in the network is no longer optional
All endpoints can become an attacker’s entry point. That’s why your network needs true endpoint detection and response (EDR), delivered by F5 and CrowdStrike.
F5 NGINX Gateway Fabric is a certified solution for Red Hat OpenShift
F5 collaborates with Red Hat to deliver a solution that combines the high-performance app delivery of F5 NGINX with Red Hat OpenShift’s enterprise Kubernetes capabilities.
F5 accelerates and secures AI inference at scale with NVIDIA Cloud Partner reference architecture
F5’s inclusion within the NVIDIA Cloud Partner (NCP) reference architecture enables secure, high-performance AI infrastructure that scales efficiently to support advanced AI workloads.
F5 Silverline Mitigates Record-Breaking DDoS Attacks
Malicious attacks are increasing in scale and complexity, threatening to overwhelm and breach the internal resources of businesses globally. Often, these attacks combine high-volume traffic with stealthy, low-and-slow, application-targeted attack techniques, powered by either automated botnets or human-driven tools.
Volterra and the Power of the Distributed Cloud (Video)
How can organizations fully harness the power of multi-cloud and edge computing? VPs Mark Weiner and James Feger join the DevCentral team for a video discussion on how F5 and Volterra can help.
Phishing Attacks Soar 220% During COVID-19 Peak as Cybercriminal Opportunism Intensifies
David Warburton, author of the F5 Labs 2020 Phishing and Fraud Report, describes how fraudsters are adapting to the pandemic and maps out the trends ahead in this video, with summary comments.