One of the ITSM practices that the ITIL framework describes is Service Portfolio Management. According to ITIL, the purpose of this approach is to ensure that organizations have the right mix of programs, projects, products and services to execute their organizational strategies within the constraints of financial and resource limitations. This is quite abstract and technical – so what does this mean? In this article, we want to shed some light on this topic.
Change Management can be a pain – especially if you’re just starting out or simply haven’t gotten the hang of it (or the appropriate tools) yet. The good news is that others have gathered the most valuable tips which we will share with you in this blog as the best 10 practices you should follow.
ITSM teams are in a balancing act between consistency and change: on the one hand, they should offer stable and reliable services, on the other hand, they have to react to constantly changing requirements with service updates. Effective IT Change Management enables you to do both! We explain what you can understand by this, what the change management process can look like and reveal some best practices.
When you bite into your favorite burger at your go to fast food restaurant, you have certain expectations regarding consistency, taste and execution. How you like your burger is exactly how you should get it. This actually requires a number of high-quality functioning configurations. So let’s pivot from you getting that delicious burger to how you expect your IT Service Management to be prepared and delivered. We quickly end up with a process called Configuration Management. Configuration Management’s goal is to make the IT landscape, the ITSM team’s services and all components that contribute to their delivery transparent and reproducible. So much for a quick introduction. Let’s dive a bit deeper into the topic.
Within IT Service Management, the practice of cataloguing, updating and tracking IT assets is referred to as IT Asset Management, or ITAM for short. IT teams anticipate tangible outcomes and advantages from this process. What are these? That’s what we will explore in this article.
ITSM teams have plenty of potential tools for meaningful optimization. However, how can the desire for continuous improvement be turned into something practical? And how can an operational approach be aligned with the organizational vision, and how can it be ensured that change really does focus on customer value? The ITIL framework offers a continuous improvement model that helps the team to operate in a structured way.
In modern IT Service Management, teams rely on frameworks that provide the appropriate processes and tools to define, set up, deliver, and continuously optimize their services. ITIL is the most popular approach in this context, virtually establishing itself as the standard in ITSM. However, several other frameworks aim to equip ITSM teams with systematic practices and processes. In this article, wee will comprehensively present four of them here and include the main differences to ITIL.
Modern IT teams strive to effectively support the company’s business processes by offering their services and tasks in the form of standardised services. The keyword is: IT Service Management, or ITSM for short. In the transformation towards ITSM, teams can fall back on a number of supporting concepts. In this context, the ITIL framework has established itself as a de facto standard that helps to establish ITSM according to a systematic approach. What is behind it?
How do IT teams organize themselves in your company? With the help of ITSM and ITIL or with DevOps? Or both? Neither? Companies often consider themselves to be either a pure ITSM or DevOps company – although the two approaches can also be combined well. But what exactly are the differences between ITSM, ITIL and DevOps? You can find the answer in this blog article.