Home » ITSM
Category Archives: ITSM
AI module in IT Service management online course
Our course IT Service management has a new module now – AI in ITSM.
Learn which roles can AI play in ITSM – boring and generative. We discuss risks, achievements, challenges and advantages of applying AI for IT service management.
Join or Retake our course NOW!

AI applying for Service Desk
Our online course – Service operations and Service Desk – got a new module – AI in Service Desk.
Join our course here.

We’re DevOps accredited training provider!
We’re happy to announce that services gained again the prestigious Training Provider and Accredited trainer status.
Join our online courses and purchase individual consulting!


Challenges in moving to DevOps Culture
Axelos, famous for its ITIL(r) and PRINCE(r) frameworks, issued a series of publications on DevOps culture and DevOps engineering.
In this publication our authors discuss the presented 4 challenges/barriers on the organization’s road to DevOps culture.
“1. An organization’s structural barrier keeps DevOps teams from thriving:
Organizational structure barriers are easy to spot but difficult to change.These organizational structural barriers include the following:
a) the excessive layers of anxious middle management which stand between ideas and their execution,
b) pathologically siloed organizational structures with no history of or incentives to engage in collaboration, and
c) senior-level executives who are not able, willing, or skilled to lead digital disruption in the company.
2. Cultural habits an fears prevent individuals and teams from innovating: for 25% of global enterprise IT organizations, a change in culture is one of the top three challenges they are facing (Upskilling IT 2023). Culture refers to the organization’s informal patterns that signal to people which behaviors are right and which behaviors define you as difficult.
The challenges can be summarized as:
a) not bringing the right people into the organization or not keeping and developing them once there,
b) aversion to risk-taking and proposing innovative ideas, and existing habits of seeing past failures and successes inhibit change.
3· Existing processes, bureaucracy, and procedural hurdles challenge even motivated staff members and teams: existing complex processes hamper the ability to make changes as there are too many dependencies and constituencies to connect. For 15% of IT enterprise organizations, the lack of innovative operating models hampers their progress. Existing processes and procedures are important as they are useful in getting things done, but they also cause issues if there is too much emphasis on internal processes and procedures versus the focus on outcomes.
4· Technology trends will continue to drive challenges: although there are a variety of technology topics that are interesting, exciting and might provide a variety of benefits, technology challenges are unavoidable, but the continuous adoption of technology continues to increase the technical debt. For 31% of IT enterprise organizations, managing technical debt and/or avoiding technical debt is a significant challenge. “
Service Desk Predictors (Leading indicators)
Service desk predictors (or leading indicators) module is added to our Service Desk KPIs e-learning course. In this module you learn how to develop and measure subjective predictors which help us to predict ad solve issues before they happen, and thus reach high KPIs.

ITSM vs DevOps e-learning course is improved with adding Scrum for Operations module
DevOps Culture Foundation e-Course. Join!
Myths about DevOps
DASA – one of the world leading associations in developing DevOps culture – shares the perfect DORA model (we tell about it in the next post) and claims a set of myths about DevOps, which build impediments on the way of correct and valuable DevOps implementing.
“
DevOps Antipatterns: However, in practice, DevOps has different meanings for different people. Due to this confusion, organizations don’t realize the benefits of DevOps. Here are some antipatterns.
Agile is for development teams, and DevOps is for the downstream teams: Wrong. DevOps is about building end-to-end product teams, who own the product and are responsible for it throughout its lifecycle. These are the teams Amazon and Spotify popularized: the two pizza teams with build-and-run responsibilities.
The DASA DevOps team competency model illustrates the skills and knowledge areas of an end-to-end responsible DevOps team.

DevOps is a CI/CD pipeline: Another common antipattern is to confuse a CI/CD pipeline with DevOps. DevOps is more than implementing a CI/CD pipeline. It is about embracing the technical and cultural practices that enable the smooth flow of small batches of work from development to operations, getting continuous feedback across the delivery pipeline, including from operations, and continually improving the process and the product based on feedback.
The mythical DevOps engineers: This antipattern is widely prevalent and perhaps the most stressful for the unlucky person. Instead of the entire organization owning the improvement of software delivery performance, a person is responsible for it. Predictably, this doesn’t work. Instead of DevOps breaking silos, organizations create another silo and a bottleneck – the stressed-out DevOps engineer.”

