In Monday’s article, we suggested that the three technical factors that could get the big boss fired are probably only limited to:
- Repeated and/or catastrophic failure (of network, systems, etc)
- Inability to serve the market (eg offerings, capacity, etc)
- Inability to operate network assets profitably
In that article, we looked closely at a human factor and how current trends of open-source, Agile and microservices might actually exacerbate it.
But let’s look at some of the broader examples under point 1 today. The failure factors we could consider that might result in the big boss getting fired are:
-
Availability (nodal and E2E)
-
Performance (nodal and E2E)
-
Security (security trust model – cloud vs corporate vs active network and related zones)
-
Remediation times, systems & processes (Assurance), particularly effectiveness of process for handling P1 (Priority 1) incidents
-
Resilience Architecture
-
Disaster Recovery Plan (incl Backup and Restore process, what black-swan events the organisation is susceptible to, etc)
-
Supportability and Maintenance Routines
-
Change and Release Management approaches
-
Human resources (incl business continuity risk of losing IP, etc)
-
Where are the SPoFs (Single Points of Failure)
We should note too that these should be viewed through two lenses:
- The lens of the network our OSS/BSS is managing and
- The lens of the systems (hardware/software/cloud) that make up our OSS/BSS