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

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,

Guest Host Post by Mike Orzen, previously posted on Mike’s Blog ,  March 25, 2021 For decades, the lean community has been talking about the importance of creating and managing customer value across the value stream. A value stream is comprised of all the activities performed to create, manage and deliver value to customers. It includes all the wasteful and broken processes we have come to accept as inherent in the way the work gets done. A key player who focuses on coordinating and aligning the efforts of all pieces of the value stream is the value stream manager. Their goal is to get everyone working together and aligned toward the common goal of optimizing their entire value stream. I like to call this character the “mythical value stream manager” because they are described in books but seldom seen in the wild – much like a unicorn. This person is the master coordinator among silos, conflicting priorities, constrained resources, and localized performance. No small task as most peo

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; ITSM professionals must now understand how the practices they use to co-create value can either support or undermine the flow of work and pervasive 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. While these measures have value, sacrificing speed, agility, and innovation can negatively impact the business. Even with the evolution to ITIL 4 , the what and why of ITSM haven’t changed. A customer-focused culture in which everyone understands how they contribute to the co

There are three core frameworks that can help us to shift the way we think, do work, and ultimately shape the behaviors and values that are the heartbeat of our organizations - CULTURE! Each of these models can be used to identify, analyze, and move an organization to new heights, new ways of collaborating and increasing speed and value for service consumers. Models for learning how to "Shift the Culture!” Erickson Model – Identifies the stages of psychosocial development  The Erickson Model helps as a starting point for “Where are we now?”. Westrum Model – Focus here is on the organizational types :  - Pathological  - Bureaucratic  - Generative  The Westrum Model helps providers get detail on the behaviors within their organization and teams.  Laloux’s Culture Model – Frederic Laloux’s model provides a clear picture of how culture may evolve in an organization. Laloux expands the concepts of the two previous models. The model comes f

I find that there are many people that do not understand WHAT a Certified Process Design Engineer (CPDE) really is (be sure to scroll down on the page and then download the free whitepaper for surprising details). The CPDE role is likely much broader and deeper than you might think! Time and Money?! Yes, but not at the expense of quality and stability!  The role of a Certified Process Design Engineer is a critical skill set for all IT service  providers. There are many frameworks and standards that  define practices and methods for achieving success; ITIL 4 , Agile , Lean , DevOps , COBIT, ISO, and Site Reliability Engineering (SRE) are only a few. My point is that while each describes processes and controls (what to do), they don’t provide clear, step-by-step methods and techniques for designing, reengineering and improving processes (how to do it).  A Certified Process Design Engineer equips managers and staff at all levels to lead the organization to do t

The Service Value System (SVS) and Service Value Chain as indicated in ITIL 4 Best Practices give you the big picture macro view that should be the start of every DevOps Pipeline . Without it, you could get swept into the undercurrent and potentially focus too much effort or misdirect resources towards the technical and automation aspects of continuous integration and continuous delivery (CI/CD).  Components of the SVS include:  The ITIL4 Guiding Principles, Governance, The Service Value Chain, Practices, and Continual Improvement. A Service Value Chain and Value Stream Mapping (VSM) exercise provides all stakeholders with a high-level view of the end-to-end steps required for your DevOps Pipeline. Applying the concept of “Systems Thinking” to the overall CI/CD Pipeline is critical but without including the information/data and flow of work we truly miss the mark. This is where Lean  principles and VSM are helpful.  Notice in the above image from our Value Stream

Part of ITIL 4 ’s value proposition is that it embraces newer ways of working, such as Agile, Lean and DevOps. I was recently asked whether there was a compelling argument for individuals to go to ITIL for information about these approaches, vs. going to ‘the source’. Here’s my answer and I’d love to hear yours. 3) What source? Yes. There is a massive amount of information available about these topics. There are many ‘definitive’ sources of knowledge. For lifelong learners such as myself, these sources are a joy. They can also be overwhelming and at times a challenge to apply. A search for information about Lean, for example, may take you down a manufacturing route which then requires translation. Looking to learn more about Agile? Which method? Scrum, SAFe, extreme programming … you get the point. 2) The source is evolving. As an example, DevOps practitioners often pride themselves in the fact that there is no definitive body of knowledge; rather, there is an evolving col

There are high performing organizations in the world that are exceeding speed to value, safety, and reliability expectations and they are provisioning co-created services fast .  Not there?! That is ok, you are not alone. I think that we all agree that we must at least be on that journey. Service providers should be capable of generating and sustaining relentless improvement with high velocity for the conversion of demand to consumer value. The ITIL 4 High Velocity IT (HVIT) certification  course explores the ways in which digital organizations function in high-velocity environments. We must move fast, and we have to do the right things fast. Velocity not only refers to speed but also to direction! Understanding these operating models helps practitioners, leaders, and organizations to improve and succeed. The ITIL 4  High Velocity IT   module and certification course  incorporate known and working practices  that focus on the rapid delivery of products and services  such as Ag

Every successful organization in the world must strive to create a “learning and improving” culture that permeates all areas of operation.  The ITIL 4 Qualification Scheme has two main streams for advanced learning and certification: The ITIL Managing Professional, The ITIL Strategic Leader Direct, Plan and Improve is so critical it has become the universal module, that stars as a key component of both, ITIL Managing Professional and ITIL Strategic Leader streams.  The ITIL 4 Direct, Plan and Improve (DPI) training and certification course provides individuals with the real-world skills necessary to create a learning and improving IT organization. This class will focus on working holistically and aligns with principles from AGILE, LEAN and Continuous Delivery optimization. Leaders, practitioners, and all service management professionals understand that strategy is key and will walk away with a strong and effective basis for strategic direction. Learners acq

Keeping it Simple is one step towards creating a world where people get up in the morning and are inspired to go to work and love to do the work that they do. The more complex something is, the more there are ways for it to go wrong. We as an industry of service providers must become educated and stop the insanity! Getting the education and the certification is a wonderful first step but once qualified we must adapt those learnings to make it simple and “Keep IT Simple”  “Keep it Simple”, one of the seven ITIL 4 Guiding Principles is a topic we have written about many times over the years.  It is anything but simple. We must acknowledge that IT services are comprised of many complex systems and if there is a way to make them even more complex IT Professionals in general seem to have that idea down to an ART.  So; How did we get that way. Business requirements are dynamic and are consistently evolving even as you read this line. Over a period of years and in ma

Communication has always been a key principle for service providers and this ITIL 4 Guiding Principle “Collaborate and Promote visibility” takes us to new heights. Encouraging staff and giving stakeholders the opportunity to develop this skill, will amalgamate teams in ways we never thought possible.  This guiding principle also represents the influence of Agile, DevOps, and LEAN on ITSM and best practices. A pillar of Agile is to be “transparent” and LEAN encourages making work visible in order to remove waste and increase flow. Both collaboration and being transparent are a key focus of DevOps integrated teams in order to ensure a continuous delivery pipeline. To understand this further let’s look at the two elements of this ITIL4 Guiding Principles. Collaborate  When we communicate, we are notifying or telling something to a person or a group. Collaboration is quite different and occurs when a group of people work together. The key word here is “together”. They wor

One of the leading questions following the release of ITIL 4 is “How do I Transition from ITIL V3 to ITIL 4?   Which translates to, how do you proceed to adapt existing processes to the new way of working?  The answer is… ITIL 4 for ITIL 4. What? That’s right! ITIL 4 has the best practice for “adapting” and might I include “accelerating” the ITSM processes that you have in play today. Below is an outline of principles, concepts and precepts from ITIL 4 guidance that will help. Ongoing Continual Improvement has always been a best practice. Therefore: How do you proceed to adapt existing processes to the new way of working? Each is discussed here at a very high level. First and foremost, START WHERE YOU ARE!  Continual Improvement - ITIL 4 is the next logical progression of your improvement cycle. Business Requirements are dynamic and therefore we must be dynamic in order to provision for evolving business and customer needs. We must be responsive (Agile) and ensure “Stab

The Practice Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies that to operations with the goal of creating ultra-scalable and highly reliable software systems. It is an Explosion!  If you have taken any classes including ITIL4, DevOps, Agile, or Lean , you have probably heard how critical Site Reliability Engineering (SRE) is to the Value Streams and Pipelines that deliver products and services to this world. New concepts like understanding “Error Budgets” and the creation of anti-fragile environments are explored. You only need to visit one of the job sites and do a search on “Site Reliability Engineering” to see that there is a huge uplift in demand for Site Reliability Engineers. Try it! T he Role As a Site Reliability Engineer, you'll build solutions to enhance availability, performance, and stability for the resilience of services. You will also work towards a Continuous Delivery Pipeline by automati