Skip to main content

Posts

Showing posts with the label DevOps Campus

How to Move and SHIFT the CULTURE!

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

SRE Is the Most Innovative Approach to ITSM Since ITIL®

Originally published on DevOps.com , written by Jayne Groll , CEO of DevOps Institute For over a decade, ITIL has been the leading ITSM framework adopted by enterprises across the globe. So, what is driving a rapidly increasing interest in Site Reliability Engineering (SRE) as a service management alternative? In its own words, Google refers to SRE as its approach to service management: “The SRE team is responsible for the availability, latency, performance, efficiency, change management, monitoring, emergency response and capacity planning.” In traditional ITSM terms, the role of the SRE is responsible for service level, change, availability, event, incident, problem, capacity, performance, infrastructure and platform management. While the operational practice areas may be similar, there are significant differences in how the practices are approached. ITIL4 Framework Compared to SRE Released in 2019, the newest update to ITIL4 remains a complex governance model with four dimensi

Shifting Sands - Minimum Viable – What is it Really?

For high performing IT providers, the sands are shifting. If you are getting certified in ITIL 4 , DevOps , or Agile Service Management you hear that we have to “Think BIG and ACT small!”. Minimum Viable Products and Minimum Viable Processes (MVP) are on the move. Historically, IT organizations delivered products and processes into production with huge batch runs or the big bang approach. This method is fraught with issues, escalations, and constant firefighting. These large releases are tightly managed, governed from the highest levels, and require participation from all parts of the organization. The days of large batch runs that take months to create and war rooms staffed 24×7 for weeks before and after the release, have given way to small incremental deployments. In comes Minimum Viable Products/Processes:  High performing organizations know that deployments that deliver value to the consumer fast are required. The idea is not to stage, stage, stage until you have a huge batch

Calling All ITIL Experts

What is an ITIL Expert?  An evangelist?  A champion?  A coach? D.    All of the Above .  Holding the ITIL Expert designation (or being an expert in ITIL) means that an individual has a broad and balanced understanding of ITIL concepts and is able to effectively apply and integrate that knowledge to the benefit of an organization. So, what happens when ITIL evolves? ITIL 4 has been introduced and now it’s time for ITIL Experts to evolve their knowledge as well. But that doesn’t mean simply expanding their knowledge of ITIL. ITIL 4 provides the guidance organizations need to address changing service management challenges and to utilize the potential of modern technology. This includes integrating Agile, Lean and DevOps concepts and understanding how these concepts influence new ways of thinking and working. So how do we bring these concepts together? Agile Service Management describes how to adapt Agile and Scrum values and practices to ITSM process design and improve

A Dash of Neuroscience – DevOps Leaders Listen Up!

As leaders, we need to understand the people that we are leading.   It is critical to understand that this is a new world and if we are to lead the global enterprise into a successful future, we need to understand the strategic, tactical, and operational objectives of our organization and also that we must have a passion for learning. “A Dash of Neuroscience“ is one of many topics introduced by the DevOps Institute for the newly updated DevOpsLeader course .   This information is taken from that course and is just a smattering of what you will learn as you prepare for your certification. Learn how to optimize speed to value as a DevOps Leader.   Live in a perpetual world of learning Many people feel their brains limit their potential and prevent them from learning.   However, learning can change our brains in terms of function, connectivity, and structure.   Our brain shapes our learning but learning shapes our brain, and research has shown that simply knowing about brain pla

DevOps and ITSM… Are They Compatible?

Many are surprised to learn that ITSM practices ARE compatible with their DevOps pipelines and even more importantly that they are a critical element to ensure the effectiveness, efficiency, and value that is expected. Those that are struggling with silos, us vs. them blame games, or roadblocks and impediments for change and test, are shocked to learn how accelerated, modernized ITSM practices can enable their outcomes!  Topics and discussion from a recent ITSM for DevOps class were exciting as practitioners, managers, and leaders discovered together how It is possible to streamline and even automate their ITSM processes and practices so that people don’t even realize that they are executing ITSM processes. We don’t need to change “what” needs to be accomplished. Policy, Governance, and Compliance are a reality. To achieve true value and business outcomes service providers must change the way that they think. A change in thinking provokes a change in how we do work. How we

Why I am Excited to Attend the DevSecOps Engineering Class

The opportunity exists to reinvent security and to do this we must redefine the roles and practices of security engineering. Information is available faster than the speed of your connection and cybersecurity risk is everywhere!  Empowerment to change begins with getting level set on what DevSecOps (DSOE) really is and how to move fast to get there.  That is why I am excited to attend the  DevSecOps Engineering  class and to acquire the DevSecOps Engineer certification!  Digital Transformations are not only real, they are accelerating. IT systems and software literally drive the world and that makes every business a digital tech business. Along with that is a proliferation of apps, devices and opportunities. Those opportunities are not always honorable; hackers abound. DevSecOps is a mindset that “everyone is responsible for security” with the goal of safely distributing security decisions at speed and scale to those who hold the highest level of context without sacrificing

DevOps and the North Pole

T’was a month before Christmas on the pipeline, not a heart was beating not even mine. For the product owner there is work to be “DONE”, so into the “Sprint Log” the work has begun! ­­­­ On Dasher! On Prancer (Development Deer) - QA and Security, they are all here. Red hats worn by all and only one “White”; The teams almost ready, so don’t you fright. When what to my wondering eyes should appear, a massive build from the Ops Engineer! This today, that tomorrow, “Fail Fast” and learn there is no sorrow! Ho Ho Ho! A jolly Scrum Master appears; impediments removed we all give a cheer! Ops leads the way with their nose shining bright; we are agile and fast and we’re out of site! Off with a flash, then “deer-to-deer” review”; here comes the surprise, it's coming to YOU. We stand all amazed and straight is our gaze.  The Christmas tree stands all tall and bright; its branches are massive and covered with lights!  On top is a star that streams long bright bars

DevOps Stakeholders – Who Are They?

IT professionals attending the DevOps FND Certification class offered by the DevOps Campus at ITSM Academy are sometimes surprised to discover that DevOps in not just about Dev and Ops . The DevOps pipeline and value stream for the continuous delivery of products and services mandates that integration of requirements and controls be orchestrated in such a way that speed and value are achieved. DevOps extends far beyond software developers and IT operations. One way to consider the stakeholders for DevOps: Dev Includes all people involved in developing software products and services including but not exclusive to: Architects, business representatives, customers, product owners, project managers, quality assurance (QA), testers and analysts, suppliers … Ops Includes all people involved in delivering and managing software products and services including but not exclusive to: ·Information security professionals, systems engineers, system administrators, IT operations engineer

You too can Take Action! – Key Takeaways from DevOps Foundation Certified Professionals

Taking action is one of the most necessary steps in effectuating life changes. However, as most of us know, sometimes it is very difficult to take that first step and commit to a desired achievement. When delivering DevOps/Agile/ITSM certification classes, I like to stress that as leaders we must inspire. And this is true because Inspiration leads to motivation and motivation triggers ACTION! Although this is true, a recent Forbes article opened my mind to another way of looking at this. In this article Svetlana Whitener states that: “You don’t need to wait to feel inspired before you implement a new behavior. You can immediately begin by gathering your willpower (a strong self-control determination that allows you to do something difficult) and stop procrastinating.” So whether you dig deep into your inner self and use will power or you are inspired by others, take action! Both motivation and will power are necessary. The bottom line is this: Digital Transformation is real and IT

DevOps and ITSM Required

Organizations adopting DevOps culture and practices are able to deliver high-quality products faster and therefore the business can deliver value to customers faster. You sometimes hear that DevOps and ITSM aren’t compatible . An IT professional attending the ITSM for DevOps course said “Everything would be OK if we could get change and compliance people out of the way!” Sound familiar? The reality is that high-performing organizations aren’t achieving success without ITSM processes. In today’s digital world organizations are performing ITSM processes Understanding Agile Service Management is key to ensure agility across the entire lifecycle. These high performers streamline, integrate and automate the process into the DevOps pipeline so that people don’t even realize that they are executing ITSM processes. We can not optimize DevOps without them and we can not accelerate our ITSM processes without DevOps. In an enterprise, DevOps doesn’t eliminate the need for controls and data. Re

Continuous Delivery vs. Continuous Deployment

One of the most frequently stated key takeaways from DevOps Foundation Certification Candidates is the big AAH-HAA moment when they realize the difference between Continuous Delivery and Continuous Deployment. Terms matter and the context in which we use them can make or break the success of any DevOps pipeline for digital transformation . Which one of these you select for your organization will have a significant impact on the way you orchestrate ­­­­your DevOps Pipeline and your Continuous Delivery Architecture. It will most definitely help to define the appropriate tool pipeline, determine how you will utilize and program those tools for automation and will have an impact on the context of your communication plans to your stakeholders. How will you approach integrated testing? There is not one element of development and delivery that Continuous Delivery or Continuous Deployment will NOT impact. Therefore; It is critical to understand what they are, how they are the same, how they

Golden Keys to Unlock Agile Success

Communication and Education before Collaboration  An engineer attending a recent DevOps FND class for certification said “OMGosh! I have been trying to do DevOps and I really did not understand what it really was!” He knew that a self-organizing team was defined as a group of motivated individuals who work together toward a goal, have the authority to take decisions and readily adapt to changing demands. Solutions are derived from inter team collaboration. Innovation is the name of the game for digital transformations. All true but … “authority” without ability is dangerous.  Let’s not forget that before these teams are able to recommend innovative ideas for improvement that we must communicate the strategy and outcomes that deliver value. Also true is the fact that we must educate teams to continuously enhance their skills.  Challenge: During your next virtual or face to face meeting with staff, ask a few questions to validate that all are on the same page. You could as

DevOps Continuous Delivery Architecture (CDA) – Should I get Certified?

A Continuous Delivery Architect (CDA) is a tool-agnostic individual engaged in the design, implementation and management of DevOps deployment pipelines and tool chains that support Continuous Integration, Continuous Delivery, Continuous Testing and, potentially, Continuous Deployment. A continuous delivery architect is also involved in defining or integrating underpinning processes, metrics, APIs and cultural considerations. Getting CDA certified prepares any IT professional engaged in the Continuous Delivery value stream . Not only will they know what to expect but could save a lot of time, money and effort to expedite the systems required to deliver. While earning a CDA Certification is a great compliment to the DevOps Foundation Certification , you might also find that it can help boost your career or prepare you for very needed positions coming up. The information and perspectives that one gains from shared experiences and class discussions is invaluable. Sometimes it is just a

DevOps - Driving Mainframe Agility

Applying DevOps principles and practices will be needed to ensure the DevOps values for Culture, Automation, Measurement and Sharing (CAMS). As major industries consider how to optimize for 2016, busting out of silos should be at the top of their list. This is true in all areas of service management and includes mainframe systems and applications.  Mainframe application and system development, like all areas of development, face many obstacles that include broken processes, obsolete tools and the common us vs. them mentality. Mainframe systems remain crucial for critical business knowledge and back-end support for customer engagement. What are service providers going to do when the mainframe developers retire or move to other positions? We have seen decades of progress on many platforms but in many cases mainframe code is still managed by siloed teams. Even so, things are moving in the right direction to increase and optimize the value stream for the development, deployment and on

Orchestration vs. Automation

It is important to understand the difference between orchestration and automation for any DevOps continuous delivery pipeline initiative. We orchestrate processes and we automate the activities within the process. In a recent DevOps Test Engineer (DTE) certification class I learned how to deconstruct the DevOps pipeline. Understanding the constructs of the pipeline and what your test strategies are will prove helpful for both the orchestration and automation of your delivery pipeline. Benefits of that knowledge generate better alignment and cadence with the business demand and greater deployment velocity. Orchestration and automation take advantage of standardization throughout the DevOps pipeline for integrated tools, integrated code, integrated build and integrated test all the way through. The results? Not only can we deliver product faster but that product or service is now delivered into an anti-fragile, secure and stable environment.  Confirmation that the process is repeat

It’s Still All About “The Process”

Organizations adopting DevOps cultures and practices are able to deliver high-quality software faster. This means the business can deliver value to customers faster. You sometimes hear that DevOps and ITSM aren’t compatible.  In a recent ITSM for DevOps workshop an attendee asked whether process is still relevant for digital transformation initiatives in today’s environment.  The answer is emphatically Yes.   Now more than ever before the attention to process is critical.  Whether your company is striving to achieve traction for a cultural shift, for a digital transformation, to create a DevOps pipeline or any other improvement initiative, Process will always be a critical success factor.   Remember we are talking about just enough process. We cannot have over engineered bureaucratic processes. For our purpose here, we will focus high level on some of the process design considerations and mistakes to avoid.   To learn more about what is just enough and how to design or redesign your

I KAN KANBAN

LEAN Principles LEAN principles originated in Japan with the “Toyota Production System” and have evolved from manufacturing. Tools and techniques for LEAN are rocking the world of Information Technology (LEAN IT). LEAN does not stand alone! There is a DevOps Foundation certification class available that explains how LEAN, AGILE and ITSM dove tail together to optimize a DevOps integrated delivery pipeline. The core idea is to deliver customer value while eliminating waste ( Muda ). The goal is to provide value to the customer through a perfect value creation process that has zero waste. What About KANBAN? KANBAN is one of many techniques utilized for LEAN practices and results in an increase in productivity and value for individuals and teams. In Japanese the word KAN means visual and the word BAN means board. KANBAN is a visual board that helps teams to visualize work and get more done. If you’re reading this because you are interested in using KANBAN for yourself or your team,

Tips & Resources for Passing a DevOps or Agile Service Management Exam

Learning the principles and practices of DevOps or Agile Service Management or learning how to become an Agile Process Owner are great, but having the credential that validates that you are certified could be a game changer for you in your career path.  There are many certification courses available from the DevOps Campus so be sure to browse through to find those that are best suited for your or your teams career path or job role function.   If you are just getting started there are a lot of free resources available to assist you on that journey. Two free whitepapers that I found helpful were: What is DevOps? - This is an in-depth overview for DevOps with a lot of good information .  It’s a great getting started and study guide. What is Agile Service Management? – Agile Service Management (Agile SM) ensures that ITSM processes reflect Agile values and are designed with “just enough” control and structure in order to effectively and efficiently deliver services that facilitat