By Donna Knapp In the context of work, a role is typically defined as a set of responsibilities, activities and authorities granted to a person or team. While a role can, at times, represent a full-time job, this is not always the case. In the course of our work, many of us play different roles (i.e., we wear different hats). For example, we may play different roles within our teams (e.g., team lead or team member), or within practices (or processes) (e.g., practice owner, process owner, or practice/process practitioner), or in the context of a framework or methodology (e.g., customer, user, or sponsor; or product owner, scrum master, or scrum team member). Roles are important because they provide greater flexibility than job descriptions, which are often bound to formalized performance plans and perhaps even to contracts. This flexibility is important because organizations are increasingly adopting operating models that are more evolutionary and less structured than most companies h

Retirement is a time that marks a new beginning. It’s a major transition that isn’t always easy. This is  true whether it relates to the retirement of people, or a technology, or as is the case with ITIL v3 Foundation, a certification. Like other major transitions, the retirement of ITIL v3 Foundation has sparked a variety of emotions and concerns. On a positive note, we can look back fondly on ITIL v3 and celebrate the progress that it has enabled us to make in terms of promoting the value of service management. It helped us to understand what processes are and the importance of continually improving those processes. It also paved the way for us to understand the importance of aligning service management with business requirements. Concerns, however, have started to creep in. Is ITIL v3 enough in the digital age? Or perhaps more importantly, is ITIL v3 too much when viewed through the lens of adjacent ways of work such as Agile, Lean, and DevOps? Have our processes become unnecessaril

Originally posted on devclass.com, June 22, 2021 and written by Joseph Martins. Sponsored Experience is everything when it comes to delivering IT-enabled products and services. But it’s no longer about how many deadlines your team smashed, how often you’d exceeded service-level agreements (SLAs), or how many lines of code you’ve spat out. Rather it’s about how the services and products you deliver impact the rest of the organisation’s ability to do their jobs, increase productivity, deliver customer satisfaction and co-create value. “Experience” may be seen as subjective, even ephemeral, compared to the traditional IT metrics, deadlines and SLAs. But if you want proof of its importance, consider how ITIL® 4, the latest revision of the best practice framework for service management from AXELOS, focuses on improving user experience of digital services and how this enhances productivity right across the organisation. Ian Aitchison, VP Product Management at Nexthink, the leader in digital

Guest Host Post by Jeff Jensen , previously posted on Jeff's Blog , February 23, 2021 I thought it would be valuable for me to share my own personal thoughts on what you will be able to do differently or better as a result of investing your time and money in becoming an ITIL 4 certified Strategic Leader : ITIL 4 Foundation WHY this class is worthwhile ITIL 4 Foundation introduces a brand new framework and concepts to reflect modern ways of working while providing guidance on how an IT organization can both position itself as a high-performing organization and improve its products, services, and underpinning practices and capabilities.  The class introduces the Service Value System, which is a systems thinking framework t hat is foundational for showing how an organization can visualize the end-to-end delivery for current state products and services, as well as utilize the guidance as a means to improve. This class is also the foundational basis of more advanced learning in the IT

Originally posted on The AXELOS Blog , March 2021 and written by Solmaz Purser , Project Editor, AXELOS The past year has been tumultuous and unexpected, to say the least. Over a year on from the start of a pandemic that few ever expected, the world has certainly changed. Many people are now working from home . This was expected to be a temporary measure, but in some instances, people have been working from home for nearly a year. It would be fair to say that this is the new normal, where commutes now involve walking to a computer, and work social events are conducted via video conferencing. This brings us to ITIL® 4;: Create, Deliver and Support (CDS) and how it can be used to help you in the new normal. The components of CDS are flexible and adaptable enough to be applied to any situation, such as surviving prolonged periods at home. Relationship management CDS explores the importance of relationship management, where a service manager acts as a point of contact and liaison between

By Donna Knapp and Jeff Jensen Let’s answer the obvious question first. What is a service management office (SMO)? ITIL® describes an SMO as a “group or department that functions as a center of excellence for service management, ensuring continual development and the consistent application of management practices across an organization.” So given that service management is a “set of specialized organizational capabilities for enabling value for customers in the form of services”, it is the SMO that helps the organization to develop these capabilities. A SMO can be formalized and have significant authority to drive service management in the organization, or it can be less-formal teams focused on continual development of the organization’s management practices. In some organizations, the SMO provides a management structure for the various practice/process owners and managers to report into. This also allows for a roll-up of enterprise metrics and reporting, and in some cases provides

By Donna Knapp We sometimes hear from organizations that they are “good with ITIL® v3”. We’d like to encourage an alternative point of view. AXELOS launched ITIL 4 in February 2019 and since then, the world has changed dramatically. COVID-19 has taught us all that the need for organizations to undergo a digital transformation is paramount to survival, as is the need to understand and leverage emerging disruptive technologies. But let’s be honest, that’s been the case long before a global pandemic changed our landscape. The gap between those able to benefit from the digital age and those who are not has been widening since the 1990s. What COVID-19 has done is accelerate the digital transformation processes in organizations. According  to a McKinsey survey of executives, “companies have accelerated the digitization of their customer and supply-chain interactions and of their internal operations by three to four years”. Let’s accept the reality of that… things have sped up dramatically,

As the pace of technological innovation increases and digital disruption becomes the norm, the need to adapt and accelerate IT service management (ITSM) processes is more critical than ever. It’s no longer a debate about whether ITSM and DevOps should interface; it’s time now for ITSM professionals to understand how the practices they use to co-create value can underpin (or undermine) the flow of work and pervasive use of automation in a DevOps environment. It’s easy to understand why ITSM professionals are skeptical about DevOps. ITSM performance metrics and service level agreements (SLAs) often revolve around the IT organization’s ability to mitigate risks, minimize impact, and “guarantee” availability. On the surface, these measures aren’t bad. It’s when we sacrifice speed, agility, and innovation in the process that the business starts to suffer. Even with the evolution to ITIL 4 , the what and why of ITSM haven’t changed. A customer-focused culture in which everyone understands

Value streams are getting a lot of attention these days for a couple of reasons. One is that value streams allow us to identify opportunities to minimize waste or bottlenecks across organizations, processes and functional silos, and to improve the flow of value. Organizations adopting DevOps , for example, are using value stream mapping as a way to improve the flow of activities during the software development lifecycle, and to improve cross-functional collaboration. Another reason is that value streams direct our attention to what customers value. For example, organizations can use value stream mapping to streamline new product development activities, improve time-based measures such as lead time and time to market, and identify ways to improve product quality. They can also use it to streamline the activities involved in integrating a new employee into the company and its culture. What these both have in common is that the focus is on optimizing the value-adding activities; with the