Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches.
We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits:
A modern executive who understands the often-missed link between service availability and business reputation, financial growth and competitive advantage. This person supports the implementation of IMS and commits time and financial resources to build world-class response capabilities.
Unafraid of high-stakes, high-pressure incidents but sometimes viewed as a scoundrel, or even nerf herder, and definitely not afraid to get his hands dirty, Han is actually a true incident commander. People in this category are also typically charismatic, not afraid to make decisions and be leaders.
Our incident responder regardless of rank; who is connonnected to the response and has a strong moral compass to "do the right thing" in the incident response program. These heroes may come across as introverted, but they are taking in the big picture and understand the state of play.
This is the LNO: empathetic, with good communication skills. They can read the room and match the message to the audience. They also have a calming presence and are fearless under pressure and scrutiny. They are also surprisingly good with a blaster.
The C-suite personality, whose motives may seem inscrutable and goals incredibly long-term, Yoda is able to accomplish what the IT Ops team might consider impossible. Operating at the strategic level, Yoda can change the entire Ops landscape with unfailing optimism, critical resources, and the right philosophy.
This is our loyal but (sometimes) grumpy, insightful hero who doesn't communicate well and sometimes operates in a silo. This hero is a good SME, but just requires the right approach. While Chewbacca may be difficult to communicate with and/or manage, this persona is typically well-intentioned but can come with a large personality and presence?
The excellent SME. They are well-versed in troubleshooting, problem-solving and quick thinking. They also communicate with low emotional drama and stick to the facts (good or bad) regardless of the situation.
The analyst; incredibly knowledgeable of IT Ops statistics, C3PO identifies short and long-term trends, and communicates them in the appropriate language??
When it comes to avoiding outages and service issues, there is no one-size-fits-all approach. The most critical thing to put in place is a team that can make honest assessments based on verified information. In addition, this team has to avoid political, reactionary and change-averse elements that can all derail otherwise good plans. It takes a team of intergalactic all-stars who understand the value of AIOps to fight the empire of evil incidents.
Put your Star Wars knowledge to the test!
Attend the INOC and BigPanda webinar and play trivia with us on May the Fourth, 2021 starting at 11:00am PST | 1:00pm CDT | 2:00pm EDT. Click here to register.
Modern complex systems are easy to develop and deploy but extremely difficult to observe. Their IT Ops data gets very messy. If you have ever worked with modern Ops teams, you will know this. There are multiple issues with data, from collection to processing to storage to getting proper insights at the right time. I will try to group and simplify them as much as possible and suggest possible solutions to do it right ...
In Agile, development and testing work in tandem, with testing being performed at each stage of the software delivery lifecycle, also known as the SDLC. This combination of development and testing is known as "shifting left." Shift left is a software development testing practice intended to resolve any errors or performance bottlenecks as early in the software development lifecycle (SDLC) as possible ...
Overwhelmingly, business leaders cited digital preparedness as key to their ability to adapt, according to an in-depth study by the Economist Intelligence Unit (EIU), looking into how the relationship between technology, business and people evolved during the COVID-19 pandemic ...
Robotic Data Automation (RDA) is a new paradigm to help automate data integration and data preparation activities involved in dealing with machine data for Analytics and AI/Machine Learning applications. RDA is not just a framework, but also includes a set of technologies and product capabilities that help implement the data automation ...
There is no one-size-fits-all approach to changing the experience of employees during a pandemic, but technological innovation can have a positive impact on how employees work from home as companies design their digital workspace strategy. The IT team supporting this shift needs to think about the following questions ...
Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches. We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits ...
Vendors and their visions often run ahead of the real-world pack — at least, the good ones do, because progress begins with vision. The downside of this rush to tomorrow is that IT practitioners can be left to ponder the practicality of technologies and wonder if their organization is ahead of the market curve or sliding behind in an invisible race that is always competitive ...
According to a new report, Digital Workspace Deployment & Performance Monitoring in the New Normal, 82% of respondents had changes in their digital workspaces due to the pandemic ...
There are a few best practices that DevOps teams should keep in mind to ensure they are not lost in the weeds when incorporating visibility and troubleshooting programs into their systems, containers, and infrastructures. Let's dive into these best practices ...