DevOps Driven Service Design

What are the top 3 things Service Management Teams should do to improve process capabilities? How do we get and keep alignment between ITIL4 and DevOps? Would love your thoughts.

Please let us know your thoughts on LinkedIn Now at:

Axelos presented a video on this topic. ITSM needs to be able to right size it for Cloud Computing at the Service and Product Value Streams.

CMDB is still the system of record for the production environment reflecting what is running where, and who owns it. The records are updated with the DevOps Life Cycle.

Cloud DevOps delivery has changed the pace, the process, and the way we manage CMDB. Public clouds change service delivery and now the infrastructure as a service including the public cloud environment’s servers, storage, networking, and data center operations. Additionally, today’s cloud computing leverages public cloud service management with third-party cloud management tools.

DevOps is the driving force for digital transformations but pace and value are slowed by the lack of evolution of legacy IT policies and processes.

Some of the implications of DevOps Driven Service Design include:

  • Challenging some of the traditional definitions of a Service
  • Introducing more logic around the use of Microservices.
  • Use of CMDB by DevOps improves referenceability and automation capabilities for design and monitoring.
  • Change Management /Risk Management audit of integrated system relationships.
  • Automated Continuous Integration brings Infrastructure as Code and Configuration as Code Reference to CMDB.
  • Greater use of Microservice or MiniService definitions to accommodate DevOps Continuous Deployment drives the need for a better definition of Service and Application.
  • Cloud related changes as to how we define our Infrastructure CIs include accounting for Kubernetes managed environments.

DZone shared the top 7 Pipeline Design Patterns for Continuous Delivery and the benefits of each:

  • Pipeline Design Pattern #1: Pipelines as Code
  • Pipeline Design Pattern #2: Externalize Logic into Reusable Libraries Libraries discoverable with good documentation.
  • Pipeline Design Pattern #3: Separate Build and Deploy Pipelines to build once, deploy many. Focus on the first build. It becomes an artifact that you can deploy many times.
  • Pipeline Design Pattern #4: Trigger the Right Pipeline
  • Pipeline Design Pattern #5: Fast Team Feedback where each successful run produces a versioned package
  • Pipeline Design Pattern #6: Stable Internal Releases
  • Pipeline Design Pattern #7: Buttoned Up Product Releases Automated releases on demand that leave a transparent paper trail that’s auditable for governance and quality


Who is looking for Work? Who is Hiring ITSM Professionals?

Helping my fellow ITSM Professionals! Where are my ITSM Configuration Management Jobseekers? THis is an awesome opportunity. Join our Professional Jobs n Careers Network to share jobs, find talent, or receive job leads.– this is where recruiters and Job Seekers can meet each other! If I know you, or you are a member or itSMF USA with SACM ServiceNow Experience, let me know and I can submit you directly.

Posted on the Linked In Group: Professionals Jobs N Career Network.


Silicon Valley IT Service Management Forum is preparing its relaunch. Would you like to join the discussion on Modern ITSM?
Contact Dawn Simmons to get involved

25 Most Impactful Leaders on LinkedIn | Artificial Intelligence (AI) and (RPA)| COVID-19 A-Z   | Enterprise Global Cyber Fraud Prevention Global Employment Taskforce  | Enterprise Global Cyber Fraud Prevention | Executive Womens Network |  Global Recruiting  Network  | Vouch4Vets |

DawnCSimmons Modern CXO ITSM, CMDB


Leave a comment