DevOps and YaSM - Revision history

Andrea at 17:29, 26 January 2025

2025-01-26T17:29:24Z

← Older revision		Revision as of 19:29, 26 January 2025
Line 2:		Line 2:
	<meta name="keywords" content="what is devops, devops processes, devops process model" />		<meta name="keywords" content="what is devops, devops processes, devops process model" />
	<meta name="description" content="DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies." />		<meta name="description" content="DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies." />
			<meta name="thumbnail" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/thumbnail/devops-service-management-processes-yasm.jpg" />
	<meta property="og:url" content="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM" />		<meta property="og:url" content="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM" />
	<meta property="og:title" content="DevOps and YaSM \| YaSM Service Management Wiki" />		<meta property="og:title" content="DevOps and YaSM \| YaSM Service Management Wiki" />
Line 14:		Line 15:
	</itpmch>		</itpmch>
	<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="210" height="54" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>		<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="210" height="54" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
	~~<p> </p>~~
	<p><b>Comparison:</b> YaSM and DevOps</p>		<p><b>Comparison:</b> YaSM and DevOps</p>
	<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>		<p><b>Part of</b>: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>
Line 43:		Line 44:
	<meta itemprop="dateCreated" content="2024-11-06" />		<meta itemprop="dateCreated" content="2024-11-06" />
	<meta itemprop="datePublished" content="2024-11-06" />		<meta itemprop="datePublished" content="2024-11-06" />
			</span>
			<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
			<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/thumbnail/devops-service-management-processes-yasm.jpg" />
			<meta itemprop="width" content="1200" />
			<meta itemprop="height" content="1200" />
			<meta itemprop="dateCreated" content="2025-01-25" />
			<meta itemprop="datePublished" content="2025-01-25" />
	</span>		</span>
	<meta itemprop="keywords" content="What is DevOps?" />		<meta itemprop="keywords" content="What is DevOps?" />

Andrea at 10:07, 8 November 2024

2024-11-08T10:07:43Z

← Older revision		Revision as of 12:07, 8 November 2024
Line 13:		Line 13:
	<meta name="pinterest-rich-pin" content="false" />		<meta name="pinterest-rich-pin" content="false" />
	</itpmch>		</itpmch>
	<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="~~140~~" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>		<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="210" height="54" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
	<p> </p>		<p> </p>
	<p><b>Comparison:</b> YaSM and DevOps</p>		<p><b>Comparison:</b> YaSM and DevOps</p>
Line 83:		Line 83:
	==Why is DevOps so popular?==		==Why is DevOps so popular?==

	ITSM frameworks like [[ITIL]]~~<sup><small>~~&~~#174~~;~~</small></sup>~~ have earned themselves a reputation for being overly complex, slowing organizations down. DevOps is often seen as a way to break free from this world of rigid processes and get things done faster.		ITSM frameworks like [[ITIL]]® have earned themselves a reputation for being overly complex, slowing organizations down. DevOps is often seen as a way to break free from this world of rigid processes and get things done faster.

	And indeed, the DevOps principles enable many organizations to be more responsive to changing business environments and customer needs:		And indeed, the DevOps principles enable many organizations to be more responsive to changing business environments and customer needs:
Line 118:		Line 118:
	====A case in point: The dreaded change management process====		====A case in point: The dreaded change management process====

	<html>A particular ITIL~~<sup><small>~~&~~#174~~;~~</small></sup>~~ discipline that is often regarded as cumbersome and excessively bureaucratic is <a class="external" href="https://wiki.en.it-processmaps.com/index.php/Change_Management" title="IT Process Wiki \| ITIL Change Management">change management</a>, with special criticism reserved for the dreaded <a href="https://yasm.com/wiki/en/index.php/YaSM_Roles" title="Definition: Change Advisory Board (CAB)">CAB</a> meeting. Its poor reputation is the result of some organizations treating every change the same, leading to a huge number of changes to be discussed and CAB meetings dragging on forever.</html>		<html>A particular ITIL® discipline that is often regarded as cumbersome and excessively bureaucratic is <a class="external" href="https://wiki.en.it-processmaps.com/index.php/Change_Management" title="IT Process Wiki \| ITIL Change Management">change management</a>, with special criticism reserved for the dreaded <a href="https://yasm.com/wiki/en/index.php/YaSM_Roles" title="Definition: Change Advisory Board (CAB)">CAB</a> meeting. Its poor reputation is the result of some organizations treating every change the same, leading to a huge number of changes to be discussed and CAB meetings dragging on forever.</html>

	Surely, this cannot work for organizations that adopt DevOps, where changes are frequent and need to be deployed rapidly.		Surely, this cannot work for organizations that adopt DevOps, where changes are frequent and need to be deployed rapidly.
Line 124:		Line 124:
	But the need to control changes will not go away, whether organizations follow the DevOps approach or not. This is because, by some estimates, more than half of all service incidents are caused by poorly coordinated or tested changes. So the way forward is not to dump change management, but to understand the principles behind the process and make it work better.		But the need to control changes will not go away, whether organizations follow the DevOps approach or not. This is because, by some estimates, more than half of all service incidents are caused by poorly coordinated or tested changes. So the way forward is not to dump change management, but to understand the principles behind the process and make it work better.

	Change management in ITIL~~<sup><small>~~&~~#174~~;~~</small></sup>~~ is about controlling risk caused by changes. ITIL~~<sup><small>~~&~~#174~~;~~</small></sup>~~ does not mandate in any way that every change be discussed by the CAB, but offers several ways of dealing with changes: High-risk changes are to be authorized by the CAB, but these should be few in number. For most changes, the risks are well known, and for such changes ITIL~~<sup><small>~~&~~#174~~;~~</small></sup>~~ recommends the definition of (pre-approved) standard changes, including change models.		Change management in ITIL® is about controlling risk caused by changes. ITIL® does not mandate in any way that every change be discussed by the CAB, but offers several ways of dealing with changes: High-risk changes are to be authorized by the CAB, but these should be few in number. For most changes, the risks are well known, and for such changes ITIL® recommends the definition of (pre-approved) standard changes, including change models.

	In a DevOps environment, where testing and deployment is often automated and standardized, the risk of changes going wrong is greatly reduced. DevOps thus enables organizations to define even more standard changes and further shrink the workload of the CAB.		In a DevOps environment, where testing and deployment is often automated and standardized, the risk of changes going wrong is greatly reduced. DevOps thus enables organizations to define even more standard changes and further shrink the workload of the CAB.
Line 159:		Line 159:

	<html>Naturally, there is also a lot of information about DevOps on the internet. One of the best resources for DevOps on the web is <a class="external" href="https://devops.com/" title="Devops.com - Where the world meets DevOps">devops.com</a> [<a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#DevOps-com" title="Reference: DevOps.com">5</a>] with a huge amount of original content, including blog posts by industry experts, featured articles, webinars, podcasts etc.</html>		<html>Naturally, there is also a lot of information about DevOps on the internet. One of the best resources for DevOps on the web is <a class="external" href="https://devops.com/" title="Devops.com - Where the world meets DevOps">devops.com</a> [<a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#DevOps-com" title="Reference: DevOps.com">5</a>] with a huge amount of original content, including blog posts by industry experts, featured articles, webinars, podcasts etc.</html>

			==Related articles==

			<html><figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Agile_Service_Management" title="Agile service management"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/agile/400px/agile-service-management-processes-yasm.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/agile/480px/agile-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/agile/agile-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/agile/480px/agile-service-management-processes-yasm.jpg" decoding="async" width="400" height="300" class="mw-file-element" alt="Agile service management based on the YaSM process model." /></a><figcaption><span style="font-variant:small-caps;">Agile and the YaSM process modell</span></figcaption></figure>
			<p><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Agile_Service_Management" title="Agile service management">Agile service management</a></p>
			<p>Agile software development is an approach to 'lightweight' software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams and the customers.</p>
			<p>How to apply agile principles as a service provider, and is the YaSM service management model compatible with Agile?<br /><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Agile_Service_Management" title="Agile service management and YaSM">[ ... Read more ]</a></p>
			<p style="clear:both;"> </p>

			<figure class="mw-halign-left" typeof="mw:File/Thumb"><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Lean_Service_Management" title="Lean Service Management"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/lean/400px/lean-service-management-yasm-process-model.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/lean/480px/lean-service-management-yasm-process-model.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/lean/lean-service-management-yasm-process-model.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/lean/480px/lean-service-management-yasm-process-model.jpg" decoding="async" width="400" height="300" class="mw-file-element" alt="Lean Service Management based on the YaSM process model." /></a><figcaption><span style="font-variant:small-caps;">Lean service management and YaSM</span></figcaption></figure>
			<p><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Lean_Service_Management" title="Lean Service Management">Lean service management</a></p>
			<p>Organizations applying the Lean principles have experienced increases in profitability and customer satisfaction.</p>
			<p>Lean was originally developed in the manufacturing industry, but today lean principles are also successfully applied in many other areas - including the service industry.<br /><a href="https://yasm.com/wiki/en/index.php/YaSM_and_Lean_Service_Management" title="Lean service management">[ ... Read more ]</a></p></html>
			<br style="clear:both;"/>

	==Notes and references==		==Notes and references==

Andrea at 17:00, 14 August 2024

2024-08-14T17:00:31Z

← Older revision		Revision as of 19:00, 14 August 2024
Line 20:		Line 20:

	<span id="What_is_DevOps.3F"><span id="md-webpage-description" itemprop="description"><b><span style="color:#465674;">DevOps</span></b> describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></span>		<span id="What_is_DevOps.3F"><span id="md-webpage-description" itemprop="description"><b><span style="color:#465674;">DevOps</span></b> describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></span>
			<p> </p>

	<html><div ~~style="float:right; margin-top:2em;"><div itemscope itemtype="https://schema.org/ImageObject">~~		<html><div itemid="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" itemscope itemtype="https://schema.org/ImageObject">
	~~<a href~~="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" ~~title~~="~~DevOps, service management and YaSM" itemprop="contentUrl~~">
	<meta itemprop="caption" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM process model go together?" />		<meta itemprop="caption" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM process model go together?" />
	<meta itemprop="width" content="1200" />		<meta itemprop="width" content="1200" />
Line 36:		Line 36:
	<meta itemprop="dateCreated" content="2022-11-12" />		<meta itemprop="dateCreated" content="2022-11-12" />
	<meta itemprop="datePublished" content="2022-11-12" />		<meta itemprop="datePublished" content="2022-11-12" />
			</span>
			<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
			<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/400px/devops-service-management-processes-yasm.jpg" />
			<meta itemprop="width" content="400" />
			<meta itemprop="height" content="300" />
			<meta itemprop="dateCreated" content="2024-11-06" />
			<meta itemprop="datePublished" content="2024-11-06" />
	</span>		</span>
	<meta itemprop="keywords" content="What is DevOps?" />		<meta itemprop="keywords" content="What is DevOps?" />
	<meta itemprop="keywords" content="DevOps processes" />		<meta itemprop="keywords" content="DevOps processes" />
	<meta itemprop="keywords" content="DevOps service management" />		<meta itemprop="keywords" content="DevOps service management" />
	<~~img style~~="~~margin~~:~~15px 0px 15px 20px; float~~:~~right;~~" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" ~~title~~="~~DevOps, service management and YaSM~~" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a><~~div class="thumbcaption" style="margin:0px 0px 20px 20px"~~><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps in service management">Use of DevOps in service management</a></b></span></~~div~~></~~div~~></div></html>		<figure class="mw-halign-right" typeof="mw:File/Thumb"><a itemprop="contentUrl"href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps, service management and YaSM"><img srcset="https://yasm.com/wiki/en/img/yasm-frameworks/devops/400px/devops-service-management-processes-yasm.jpg 400w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" class="mw-file-element" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a>
	~~<p> </p~~>		<figcaption><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps in service management">Use of DevOps in service management</a></b></span></figcaption></figure></div></html>

	__TOC__		__TOC__
			<br style="clear:both;"/>

	~~<p> </p>~~
	Traditionally, organizations doing software development tended to work in 'silos'. Developers, testers, administrators and operational staff were organized in separate teams, handing over (biggish) chunks of work from one team to another.		Traditionally, organizations doing software development tended to work in 'silos'. Developers, testers, administrators and operational staff were organized in separate teams, handing over (biggish) chunks of work from one team to another.

Line 59:		Line 66:

	Everything in the DevOps approach can be derived from a few basic principles, known as the <i>'Three Ways of DevOps':</i>		Everything in the DevOps approach can be derived from a few basic principles, known as the <i>'Three Ways of DevOps':</i>
	;The first way - Systems thinking
	:Organizations need to focus on the performance of the entire system, as opposed to the performance of individual silos. This includes trying to remove bottlenecks to optimize the flow of work.		===The first way===
	;The second way - Amplify feedback loops		<i>Systems thinking:</i>
	:This principle states that feedback loops should be short, allowing for frequent and continual improvement. Issues should be regarded as feedback and corrective action taken swiftly.		*Organizations need to focus on the performance of the entire system, as opposed to the performance of individual silos.
	;The third way - Culture of continual experimentation and learning		* This includes trying to remove bottlenecks to optimize the flow of work.
	:The third way says that experimenting, taking (calculated) risk and learning from successes and failures are essential for making progress and perfecting the organization's operations.
			===The second way===
			<i>Amplify feedback loops:</i>
			*This principle states that feedback loops should be short, allowing for frequent and continual improvement.
			* Issues should be regarded as feedback and corrective action taken swiftly.

			===The third way===
			<i>Culture of continual experimentation and learning:</i>
			*The third way says that experimenting, taking (calculated) risk and learning from successes and failures are essential for making progress and perfecting the organization's operations.

	==Why is DevOps so popular?==		==Why is DevOps so popular?==
Line 147:		Line 162:
	==Notes and references==		==Notes and references==

	<span id="Wikipedia-Continuous-Integration">[1] [https://en.wikipedia.org/wiki/Continuous_integration Continuous Integration]. -- Wikipedia. Retrieved ~~September 22~~, ~~2018~~.</span><br />		<span id="Wikipedia-Continuous-Integration">[1] [https://en.wikipedia.org/wiki/Continuous_integration Continuous Integration]. -- Wikipedia. Retrieved August 14, 2024.</span><br />
	<span id="Wikipedia-Continuous-Delivery">[2] [https://en.wikipedia.org/wiki/Continuous_delivery Continuous delivery]. -- Wikipedia. Retrieved ~~September 22~~, ~~2018~~.</span><br />		<span id="Wikipedia-Continuous-Delivery">[2] [https://en.wikipedia.org/wiki/Continuous_delivery Continuous delivery]. -- Wikipedia. Retrieved August 14, 2024.</span><br />
	<span id="Patrick-Debois-Twitter">[1] Follow [https://www.linkedin.com/in/patrickdebois/ Patrick Debois on LinkedIn]!</span><br />		<span id="Patrick-Debois-Twitter">[1] Follow [https://www.linkedin.com/in/patrickdebois/ Patrick Debois on LinkedIn]!</span><br />
	<span id="DevOps-Phoenix-Project">[2] Gene Kim, Kevin Behr, and George Spafford, 2013. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution Press, Portland, Oregon; USA.</span><br />		<span id="DevOps-Phoenix-Project">[2] Gene Kim, Kevin Behr, and George Spafford, 2013. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution Press, Portland, Oregon; USA.</span><br />

Andrea at 16:10, 4 April 2024

2024-04-04T16:10:21Z

Andrea at 16:05, 30 December 2023

2023-12-30T16:05:02Z

← Older revision		Revision as of 18:05, 30 December 2023
Line 6:		Line 6:
	<meta property="og:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?" />		<meta property="og:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?" />
	<meta property="og:site_name" content="YaSM Service Management">		<meta property="og:site_name" content="YaSM Service Management">
	<meta property="og:type" content="article~~" />~~		<meta property="og:type" content="article" />
	~~<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />~~
	~~<meta property="fb:admins" content="100002035253209" />~~
	~~<meta property="fb:admins" content="100002592864414~~" />
	<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" />		<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" />
	<meta property="og:image:width" content="1200" />		<meta property="og:image:width" content="1200" />
	<meta property="og:image:height" content="900" />		<meta property="og:image:height" content="900" />
	~~<meta name="twitter:card" content="summary_large_image">~~
	~~<meta name="twitter:site" content="@yasmcom">~~
	~~<meta name="twitter:creator" content="@yasmcom">~~
	~~<meta name="twitter:title" content="DevOps and YaSM">~~
	~~<meta name="twitter:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?">~~
	~~<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg">~~
	~~<meta name="twitter:image:alt" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM service management process model go together?">~~
	<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />		<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
	<meta name="pinterest-rich-pin" content="false" />		<meta name="pinterest-rich-pin" content="false" />

Andrea at 12:22, 12 November 2022

2022-11-12T12:22:05Z

← Older revision		Revision as of 14:22, 12 November 2022
Line 5:		Line 5:
	<meta property="og:title" content="DevOps and YaSM \| YaSM Service Management Wiki" />		<meta property="og:title" content="DevOps and YaSM \| YaSM Service Management Wiki" />
	<meta property="og:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?" />		<meta property="og:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?" />
	<meta property="og:site_name" content="YaSM">		<meta property="og:site_name" content="YaSM Service Management">
	<meta property="og:type" content="article" />		<meta property="og:type" content="article" />
	<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />		<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />
Line 29:		Line 29:
	<p> </p>		<p> </p>

	=~~==What is DevOps?===~~		<span id="What_is_DevOps.3F"><span id="md-webpage-description" itemprop="description">DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></span>
	~~----~~

	~~<html~~><span id="md-webpage-description" itemprop="description">DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></p>

	<div itemscope itemtype="https://schema.org/ImageObject">		<html><div style="float:right; margin-top:2em;"><div itemscope itemtype="https://schema.org/ImageObject">
	<a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps, service management and YaSM" itemprop="contentUrl">		<a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps, service management and YaSM" itemprop="contentUrl">
	<meta itemprop="caption" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM process model go together?" />		<meta itemprop="caption" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM process model go together?" />
	<meta itemprop="width" content="1200" />		<meta itemprop="width" content="1200" />
	<meta itemprop="height" content="900" />		<meta itemprop="height" content="900" />
			<meta itemprop="dateCreated" content="2018-09-21" />
			<meta itemprop="datePublished" content="2018-09-22" />
			<meta itemprop="dateModified" content="2022-11-12" />
	<meta itemprop="representativeOfPage" content="true"/>		<meta itemprop="representativeOfPage" content="true"/>
			<span itemprop="thumbnail" itemscope itemtype="https://schema.org/ImageObject">
			<meta itemprop="url" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg" />
			<meta itemprop="width" content="480" />
			<meta itemprop="height" content="360" />
			<meta itemprop="dateCreated" content="2022-11-12" />
			<meta itemprop="datePublished" content="2022-11-12" />
			</span>
	<meta itemprop="keywords" content="What is DevOps?" />		<meta itemprop="keywords" content="What is DevOps?" />
	<meta itemprop="keywords" content="DevOps processes" />		<meta itemprop="keywords" content="DevOps processes" />
	<img style="margin:20px ~~0px 30px 30px~~; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" width="480" height="360" title="DevOps, service management and YaSM" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a></div></html>		<meta itemprop="keywords" content="DevOps service management" />
			<img style="margin:15px 0px 15px 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" width="480" height="360" title="DevOps, service management and YaSM" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a><div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: Use of DevOps in service management</b></span></div></div></div></html>

	<p> </p>		<p> </p>
Line 57:		Line 65:
	DevOps is about breaking down these silos and creating cross-functional teams, so that developers, testers and administrators work closely together from the very beginning. Each team takes collective accountability for how actual users experience their software. The objective is faster, more reliable deployment of software, in line with the fast-changing needs of the customers.		DevOps is about breaking down these silos and creating cross-functional teams, so that developers, testers and administrators work closely together from the very beginning. Each team takes collective accountability for how actual users experience their software. The objective is faster, more reliable deployment of software, in line with the fast-changing needs of the customers.

	To make this approach work, DevOps promotes the use of other, related practices, such as Agile, Lean, Continuous Integration [[#Wikipedia-Continuous-Integration\|[1]]], Continuous Delivery [[#Wikipedia-Continuous-Delivery\|[2]]], etc.		To make this approach work, DevOps promotes the use of other, related practices, such as [[YaSM_and_Agile_Service_Management\|Agile]], [[YaSM_and_Lean_Service_Management\|Lean]], Continuous Integration [[#Wikipedia-Continuous-Integration\|[1]]], Continuous Delivery [[#Wikipedia-Continuous-Delivery\|[2]]], etc.

	==The Three Ways of DevOps==		==The Three Ways of DevOps==
Line 71:		Line 79:
	==Why is DevOps so popular?==		==Why is DevOps so popular?==

	~~<html>~~ITSM frameworks like ~~<a href="https://wiki.en.it-processmaps.com/index.php/History_of_ITIL" title="What is ITIL \| IT Process Wiki">~~ITIL~~</a>~~<sup><small>®</small></sup> have earned themselves a reputation for being overly complex, slowing organizations down. DevOps is often seen as a way to break free from this world of rigid processes and get things done faster.~~</html>~~		ITSM frameworks like [[ITIL]]<sup><small>®</small></sup> have earned themselves a reputation for being overly complex, slowing organizations down. DevOps is often seen as a way to break free from this world of rigid processes and get things done faster.

	And indeed, the DevOps principles enable many organizations to be more responsive to changing business environments and customer needs:		And indeed, the DevOps principles enable many organizations to be more responsive to changing business environments and customer needs:
Line 98:		Line 106:
	*[[SP3: Manage customer relationships\|Manage relationships with customers]]		*[[SP3: Manage customer relationships\|Manage relationships with customers]]
	*[[SP11: Manage suppliers\|Manage suppliers]]		*[[SP11: Manage suppliers\|Manage suppliers]]
	*[[SP9: Ensure compliance\|Ensure compliance]]		*[[SP9: Ensure compliance\|Ensure compliance]].

	These are essential capabilities for every service provider, yet DevOps has nothing, or very little, to say about them. It would thus be wrong to dismiss the time-honored service management practices as old hat. In fact, they are as relevant as ever.		These are essential capabilities for every service provider, yet DevOps has nothing, or very little, to say about them. It would thus be wrong to dismiss the time-honored service management practices as old hat. In fact, they are as relevant as ever.
Line 152:		Line 160:
	<span id="Wikipedia-Continuous-Integration">[1] [https://en.wikipedia.org/wiki/Continuous_integration Continuous Integration]. -- Wikipedia. Retrieved September 22, 2018.</span><br />		<span id="Wikipedia-Continuous-Integration">[1] [https://en.wikipedia.org/wiki/Continuous_integration Continuous Integration]. -- Wikipedia. Retrieved September 22, 2018.</span><br />
	<span id="Wikipedia-Continuous-Delivery">[2] [https://en.wikipedia.org/wiki/Continuous_delivery Continuous delivery]. -- Wikipedia. Retrieved September 22, 2018.</span><br />		<span id="Wikipedia-Continuous-Delivery">[2] [https://en.wikipedia.org/wiki/Continuous_delivery Continuous delivery]. -- Wikipedia. Retrieved September 22, 2018.</span><br />
	<span id="Patrick-Debois-Twitter">[1] Follow [https://~~twitter~~.com/patrickdebois Patrick Debois on ~~Twitter~~]!</span><br />		<span id="Patrick-Debois-Twitter">[1] Follow [https://www.linkedin.com/in/patrickdebois/ Patrick Debois on LinkedIn]!</span><br />
	<span id="DevOps-Phoenix-Project">[2] Gene Kim, Kevin Behr, and George Spafford, 2013. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution Press, Portland, Oregon; USA.</span><br />		<span id="DevOps-Phoenix-Project">[2] Gene Kim, Kevin Behr, and George Spafford, 2013. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution Press, Portland, Oregon; USA.</span><br />
	<span id="DevOps-com">[3] Devops.com (2018). Where the world meets DevOps. Retrieved from https://devops.com/</span><br />		<span id="DevOps-com">[3] Devops.com (2018). Where the world meets DevOps. Retrieved from https://devops.com/</span><br />

Andrea at 17:48, 28 March 2019

2019-03-28T17:48:17Z

← Older revision		Revision as of 19:48, 28 March 2019
Line 16:		Line 16:
	<meta name="twitter:site" content="@yasmcom">		<meta name="twitter:site" content="@yasmcom">
	<meta name="twitter:creator" content="@yasmcom">		<meta name="twitter:creator" content="@yasmcom">
	<meta name="twitter:title" content="DevOps and YaSM ~~\| YaSM Wiki~~">		<meta name="twitter:title" content="DevOps and YaSM">
	<meta name="twitter:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?">		<meta name="twitter:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?">
	<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg">		<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg">
Line 23:		Line 23:
	<meta name="pinterest-rich-pin" content="false" />		<meta name="pinterest-rich-pin" content="false" />
	</itpmch>		</itpmch>
	<html><div class="floatright"><div class="noresize"><map name="ImageMap_yasm-wiki-share"><area href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FDevOps_and_YaSM&hl=en_US&source=YaSM%20Wiki" class="plainlinks" rel="nofollow" shape="rect" coords="55,0,99,36" alt="share this page on LinkedIn" title="share this page on LinkedIn"/><area href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FDevOps_and_YaSM&text=%23YaSMwiki%20%7C%20Does%20DevOps%20replace%20ITSM%20and%20service%20management%20best%20practice%3F%0ACan%20%23DevOps%20and%20the%20%23YaSM%20process%20model%20go%20together%3F%20%0A%E2%96%BA&lang=de&via=yasmcom" class="plainlinks" rel="nofollow" shape="rect" coords="97,0,140,36" alt="share this page on Twitter" title="share this page on Twitter"/></map><img alt="share this page" src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-share.png" width="140" height="36" usemap="#ImageMap_yasm-wiki-share"/></div></div><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:~~left~~;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>		<html><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:right;" alt="auf Deutsch" title="This page in German" /></a></div><br style="clear:both;"/>
	<p> </p>		<p> </p>
	<p><b>Comparison:</b> YaSM and DevOps</p>		<p><b>Comparison:</b> YaSM and DevOps</p>
Line 58:		Line 58:

	To make this approach work, DevOps promotes the use of other, related practices, such as Agile, Lean, Continuous Integration [[#Wikipedia-Continuous-Integration\|[1]]], Continuous Delivery [[#Wikipedia-Continuous-Delivery\|[2]]], etc.		To make this approach work, DevOps promotes the use of other, related practices, such as Agile, Lean, Continuous Integration [[#Wikipedia-Continuous-Integration\|[1]]], Continuous Delivery [[#Wikipedia-Continuous-Delivery\|[2]]], etc.
	~~<p> </p>~~

	==The Three Ways of DevOps==		==The Three Ways of DevOps==
Line 69:		Line 68:
	;The third way - Culture of continual experimentation and learning		;The third way - Culture of continual experimentation and learning
	:The third way says that experimenting, taking (calculated) risk and learning from successes and failures are essential for making progress and perfecting the organization's operations.		:The third way says that experimenting, taking (calculated) risk and learning from successes and failures are essential for making progress and perfecting the organization's operations.
	~~<p> </p>~~

	==Why is DevOps so popular?==		==Why is DevOps so popular?==
Line 80:		Line 78:

	Another reason for DevOps being so popular is the availability of modern technologies and concepts that support its adoption, such as cloud services, virtualization, containerization, microservices, etc.		Another reason for DevOps being so popular is the availability of modern technologies and concepts that support its adoption, such as cloud services, virtualization, containerization, microservices, etc.
	~~<p> </p>~~

	==Does DevOps replace ITSM and service management best practice?==		==Does DevOps replace ITSM and service management best practice?==
Line 89:		Line 86:

	So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.		So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.
	~~<p> </p>~~

	==Why service management best practice is not old stuff==		==Why service management best practice is not old stuff==
Line 107:		Line 103:

	What should be dismissed is the notion that service management as a discipline is difficult and bureaucratic. Service management frameworks can come across as very complex, but it has always been mistaken to try to 'implement' everything dogmatically. The key is to understand the principles behind the frameworks, select those parts of the guidance that offer the most benefits, and define clear, tailor-made processes that work for the organization.		What should be dismissed is the notion that service management as a discipline is difficult and bureaucratic. Service management frameworks can come across as very complex, but it has always been mistaken to try to 'implement' everything dogmatically. The key is to understand the principles behind the frameworks, select those parts of the guidance that offer the most benefits, and define clear, tailor-made processes that work for the organization.
	~~<p> </p>~~

	====A case in point: The dreaded change management process====		====A case in point: The dreaded change management process====
Line 122:		Line 117:

	So DevOps has by no means rendered the [[SP5: Assess and coordinate changes\|change management process]] irrelevant. Rather, DevOps provides an opportunity to deal with changes more efficiently.		So DevOps has by no means rendered the [[SP5: Assess and coordinate changes\|change management process]] irrelevant. Rather, DevOps provides an opportunity to deal with changes more efficiently.
	~~<p> </p>~~

	==Is DevOps for all service providers?==		==Is DevOps for all service providers?==
Line 133:		Line 127:

	So all service providers are encouraged to explore the DevOps approach.		So all service providers are encouraged to explore the DevOps approach.
	~~<p> </p>~~

	==Can YaSM and DevOps go together?==		==Can YaSM and DevOps go together?==
Line 146:		Line 139:

	<html>So the YaSM model is not specifically aligned with DevOps, but with its streamlined, straightforward <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map: Service management process templates">set of processes and templates</a>, YaSM gives organizations a kind of skeleton for their service management processes, and the flexibility to build DevOps principles into these processes.</html>		<html>So the YaSM model is not specifically aligned with DevOps, but with its streamlined, straightforward <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map: Service management process templates">set of processes and templates</a>, YaSM gives organizations a kind of skeleton for their service management processes, and the flexibility to build DevOps principles into these processes.</html>
	~~<p> </p>~~

	==Where can I learn more about DevOps?==		==Where can I learn more about DevOps?==
Line 155:		Line 147:

	<html>Naturally, there is also a lot of information about DevOps on the internet. One of the best resources for DevOps on the web is <a class="external" href="https://devops.com/" title="Devops.com - Where the world meets DevOps">devops.com</a> [<a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#DevOps-com" title="Reference: DevOps.com">5</a>] with a huge amount of original content, including blog posts by industry experts, featured articles, webinars, podcasts etc.</html>		<html>Naturally, there is also a lot of information about DevOps on the internet. One of the best resources for DevOps on the web is <a class="external" href="https://devops.com/" title="Devops.com - Where the world meets DevOps">devops.com</a> [<a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#DevOps-com" title="Reference: DevOps.com">5</a>] with a huge amount of original content, including blog posts by industry experts, featured articles, webinars, podcasts etc.</html>
	~~<p> </p>~~

	==Notes and references==		==Notes and references==
Line 165:		Line 156:
	<span id="DevOps-com">[3] Devops.com (2018). Where the world meets DevOps. Retrieved from https://devops.com/</span><br />		<span id="DevOps-com">[3] Devops.com (2018). Where the world meets DevOps. Retrieved from https://devops.com/</span><br />

	<html>By:  Stefan Kempter <a ~~rel="author"~~ href="https://~~plus~~.~~google~~.com/~~111925560448291102517~~/~~about~~"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/~~google~~.jpg" width="16" height="16" title="By: Stefan Kempter \| Profile on ~~Google+~~" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://~~plus~~.~~google~~.com/~~113316270668629760475~~/~~about~~"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/~~google~~.jpg" width="16" height="16" title="By: Andrea Kempter \| Profile on ~~Google+~~" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.		<html>By:  Stefan Kempter <a href="https://www.linkedin.com/in/stefankempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Stefan Kempter \| Profile on LinkedIn" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://www.linkedin.com/in/andreakempter"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/linkedin.jpg" width="16" height="16" title="By: Andrea Kempter \| Profile on LinkedIn" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
	<p> </p>		<p> </p>

Andrea at 10:08, 11 October 2018

2018-10-11T10:08:14Z

← Older revision		Revision as of 12:08, 11 October 2018
Line 86:		Line 86:
	The term 'DevOps' was first coined in 2009 by Patrick Debois [[#Patrick-Debois-Twitter\|[3]]]. Interest in DevOps grew quickly and, amid much hype, many were lead to believe that DevOps was a better alternative to ITSM and service management frameworks like ITIL.		The term 'DevOps' was first coined in 2009 by Patrick Debois [[#Patrick-Debois-Twitter\|[3]]]. Interest in DevOps grew quickly and, amid much hype, many were lead to believe that DevOps was a better alternative to ITSM and service management frameworks like ITIL.

	There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. [[~~YaSM~~ Processes\|Properly defined processes]] are still needed to provide direction and control. How else would organizations ensure, for example, that the services offered are aligned with customer needs, and delivered as promised?		There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. [[Service Management Processes\|Properly defined processes]] are still needed to provide direction and control. How else would organizations ensure, for example, that the services offered are aligned with customer needs, and delivered as promised?

	So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.		So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.

Andrea: Created page with "DevOps and YaSM | YaSM Wiki
2018-09-22T13:55:25Z

Created page with "<itpmch><title>DevOps and YaSM | YaSM Wiki</title> <meta name="keywords" content="what is devops, devops processes, devops process model" /> <meta name="description" content="..."

New page
<itpmch><title>DevOps and YaSM | YaSM Service Management Wiki</title>
<meta name="keywords" content="what is devops, devops processes, devops process model" />
<meta name="description" content="DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies." />
<meta property="og:url" content="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM" />
<meta property="og:title" content="DevOps and YaSM | YaSM Service Management Wiki" />
<meta property="og:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?" />
<meta property="og:site_name" content="YaSM">
<meta property="og:type" content="article" />
<meta property="article:publisher" content="https://www.facebook.com/yasmcom" />
<meta property="fb:admins" content="100002035253209" />
<meta property="fb:admins" content="100002592864414" />
<meta property="og:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="900" />
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@yasmcom">
<meta name="twitter:creator" content="@yasmcom">
<meta name="twitter:title" content="DevOps and YaSM | YaSM Wiki">
<meta name="twitter:description" content="Does DevOps replace ITSM and service management best practice? Can YaSM and DevOps go together?">
<meta name="twitter:image" content="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg">
<meta name="twitter:image:alt" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM service management process model go together?">
<link href="https://plus.google.com/104150539756444616711/posts" rel="publisher" />
<meta name="pinterest-rich-pin" content="false" />
</itpmch>
<html><div class="floatright"><div class="noresize"><map name="ImageMap_yasm-wiki-share"><area href="https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FDevOps_and_YaSM&hl=en_US&source=YaSM%20Wiki" class="plainlinks" rel="nofollow" shape="rect" coords="55,0,99,36" alt="share this page on LinkedIn" title="share this page on LinkedIn"/><area href="https://twitter.com/intent/tweet?url=https%3A%2F%2Fyasm.com%2Fwiki%2Fen%2Findex.php%2FDevOps_and_YaSM&text=%23YaSMwiki%20%7C%20Does%20DevOps%20replace%20ITSM%20and%20service%20management%20best%20practice%3F%0ACan%20%23DevOps%20and%20the%20%23YaSM%20process%20model%20go%20together%3F%20%0A%E2%96%BA&lang=de&via=yasmcom" class="plainlinks" rel="nofollow" shape="rect" coords="97,0,140,36" alt="share this page on Twitter" title="share this page on Twitter"/></map><img alt="share this page" src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-share.png" width="140" height="36" usemap="#ImageMap_yasm-wiki-share"/></div></div><div class="noresize"><a href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM"><img src="https://yasm.com/wiki/en/img/yasm-wiki/YaSM-Wiki-Deutsch.png" width="140" height="36" style="float:left;" alt="auf Deutsch" title="This page in German" /></a></div> 
 
Comparison: YaSM and DevOps
Part of: <a href="https://yasm.com/wiki/en/index.php/What_is_YaSM#yasm-other-service-management-frameworks" title="YaSM and other service management frameworks and standards">YaSM vs. other service management frameworks and standards</a></html>
 

===What is DevOps?===
----

<html>DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.

<div itemscope itemtype="https://schema.org/ImageObject">
<a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps, service management and YaSM" itemprop="contentUrl">
<meta itemprop="caption" content="DevOps, service management processes and YaSM: Can DevOps and the YaSM process model go together?" />
<meta itemprop="width" content="1200" />
<meta itemprop="height" content="900" />
<meta itemprop="representativeOfPage" content="true"/>
<meta itemprop="keywords" content="What is DevOps?" />
<meta itemprop="keywords" content="DevOps processes" />
<img style="margin:20px 0px 30px 30px; float:right;" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" width="480" height="360" title="DevOps, service management and YaSM" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a></div></html>

 

TOC

 
Traditionally, organizations doing software development tended to work in 'silos'. Developers, testers, administrators and operational staff were organized in separate teams, handing over (biggish) chunks of work from one team to another.

This linear structure often creates problems, as teams focus on their own areas of responsibility and are less interested in overall success.

A typical example are the often conflicting interests between software development and operations: While the developers' focus may be on the fast completion of code, operations is a lot more concerned about software quality and rigorous testing, to keep the production environment stable.

DevOps is about breaking down these silos and creating cross-functional teams, so that developers, testers and administrators work closely together from the very beginning. Each team takes collective accountability for how actual users experience their software. The objective is faster, more reliable deployment of software, in line with the fast-changing needs of the customers.

To make this approach work, DevOps promotes the use of other, related practices, such as Agile, Lean, Continuous Integration [[#Wikipedia-Continuous-Integration|[1]]], Continuous Delivery [[#Wikipedia-Continuous-Delivery|[2]]], etc.
 

==The Three Ways of DevOps==

Everything in the DevOps approach can be derived from a few basic principles, known as the 'Three Ways of DevOps':
;The first way - Systems thinking
:Organizations need to focus on the performance of the entire system, as opposed to the performance of individual silos. This includes trying to remove bottlenecks to optimize the flow of work.
;The second way - Amplify feedback loops
:This principle states that feedback loops should be short, allowing for frequent and continual improvement. Issues should be regarded as feedback and corrective action taken swiftly.
;The third way - Culture of continual experimentation and learning
:The third way says that experimenting, taking (calculated) risk and learning from successes and failures are essential for making progress and perfecting the organization's operations.
 

==Why is DevOps so popular?==

<html>ITSM frameworks like <a href="https://wiki.en.it-processmaps.com/index.php/History_of_ITIL" title="What is ITIL | IT Process Wiki">ITIL</a>® have earned themselves a reputation for being overly complex, slowing organizations down. DevOps is often seen as a way to break free from this world of rigid processes and get things done faster.</html>

And indeed, the DevOps principles enable many organizations to be more responsive to changing business environments and customer needs:
Work is broken into smaller chunks, leading to shorter development and release cycles.
Cross-functional teams, spanning development and operations, ensure that operational needs of new software are considered from the beginning.

Another reason for DevOps being so popular is the availability of modern technologies and concepts that support its adoption, such as cloud services, virtualization, containerization, microservices, etc.
 

==Does DevOps replace ITSM and service management best practice?==

The term 'DevOps' was first coined in 2009 by Patrick Debois [[#Patrick-Debois-Twitter|[3]]]. Interest in DevOps grew quickly and, amid much hype, many were lead to believe that DevOps was a better alternative to ITSM and service management frameworks like ITIL.

There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. [[YaSM Processes|Properly defined processes]] are still needed to provide direction and control. How else would organizations ensure, for example, that the services offered are aligned with customer needs, and delivered as promised?

So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.
 

==Why service management best practice is not old stuff==

[[What_is_YaSM#YaSM_and_ITIL.2C_ISO_20000.2C_SIAM.2C_VeriSM.2C_DevOps.2C_.E2.80.A6|Service management frameworks]] contain lots of time-tested advice for being successful as a service provider. They describe, for instance, how to
[[LP1: Set the strategic direction|Formulate and execute a service strategy]]
[[LP2: Design new or changed services|Define services based on customer requirements]]
[[SP5: Assess and coordinate changes|Manage changes and their associated risks]]
[[LP4.6: Resolve incidents and service requests|Resolve service incidents and fulfil service requests]]
[[LP4: Operate the services#LP4.4|Measure service quality]]
[[LP5: Improve the services|Continually improve the services]]
[[SP3: Manage customer relationships|Manage relationships with customers]]
[[SP11: Manage suppliers|Manage suppliers]]
*[[SP9: Ensure compliance|Ensure compliance]]

These are essential capabilities for every service provider, yet DevOps has nothing, or very little, to say about them. It would thus be wrong to dismiss the time-honored service management practices as old hat. In fact, they are as relevant as ever.

What should be dismissed is the notion that service management as a discipline is difficult and bureaucratic. Service management frameworks can come across as very complex, but it has always been mistaken to try to 'implement' everything dogmatically. The key is to understand the principles behind the frameworks, select those parts of the guidance that offer the most benefits, and define clear, tailor-made processes that work for the organization.
 

====A case in point: The dreaded change management process====

<html>A particular ITIL® discipline that is often regarded as cumbersome and excessively bureaucratic is <a class="external" href="https://wiki.en.it-processmaps.com/index.php/Change_Management" title="IT Process Wiki | ITIL Change Management">change management</a>, with special criticism reserved for the dreaded <a href="https://yasm.com/wiki/en/index.php/YaSM_Roles" title="Definition: Change Advisory Board (CAB)">CAB</a> meeting. Its poor reputation is the result of some organizations treating every change the same, leading to a huge number of changes to be discussed and CAB meetings dragging on forever.</html>

Surely, this cannot work for organizations that adopt DevOps, where changes are frequent and need to be deployed rapidly.

But the need to control changes will not go away, whether organizations follow the DevOps approach or not. This is because, by some estimates, more than half of all service incidents are caused by poorly coordinated or tested changes. So the way forward is not to dump change management, but to understand the principles behind the process and make it work better.

Change management in ITIL® is about controlling risk caused by changes. ITIL® does not mandate in any way that every change be discussed by the CAB, but offers several ways of dealing with changes: High-risk changes are to be authorized by the CAB, but these should be few in number. For most changes, the risks are well known, and for such changes ITIL® recommends the definition of (pre-approved) standard changes, including change models.

In a DevOps environment, where testing and deployment is often automated and standardized, the risk of changes going wrong is greatly reduced. DevOps thus enables organizations to define even more standard changes and further shrink the workload of the CAB.

So DevOps has by no means rendered the [[SP5: Assess and coordinate changes|change management process]] irrelevant. Rather, DevOps provides an opportunity to deal with changes more efficiently.
 

==Is DevOps for all service providers?==

DevOps has its roots in software engineering, and therefore it is particularly well suited for software-based services. For other types of services, the picture is less clear, although DevOps is very likely to hold some useful recommendations for most service providers.

As an example, a logistics services business makes heavy use of fixed assets such as vehicles, warehouses, etc. It is obvious that this kind of equipment cannot be upgraded in short cycles, as is the case with software.

Still, even in environments where service components cannot be 'virtualized' and changed at short notice, applying some DevOps ideas may prove beneficial, such as putting cross-functional teams in charge of services across their whole lifecycle, from service design to deployment, operation and improvement.

So all service providers are encouraged to explore the DevOps approach.
 

==Can YaSM and DevOps go together?==

<html>The <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map">YaSM process model</a> represents established service management best practice and can be applied to IT services and all other types of services.</html>

The model includes activities for [[LP2: Design new or changed services|designing]], [[LP3: Build new or changed services|building]], [[LP3: Build new or changed services#LP3.5|testing]], [[LP3: Build new or changed services#LP3.6|deploying]], [[LP4: Operate the services|operating]] and [[LP5: Improve the services|improving services]]. But the YaSM model is not prescriptive and users are free to adapt the processes to their needs and execute them in the most effective way.

For example, [[LP3: Build new or changed services#LP3.5|testing activities]] include the creation of [[LP3: Build new or changed services#Test-script|test scripts]], running tests, [[LP3: Build new or changed services#Test-report|documenting test results]], etc. Exactly how tests are executed must be decided on a case-by-case basis and will depend on the nature of the service components to be tested. Organizations that follow the DevOps principles will certainly try to automate testing wherever possible.

Much the same applies to deployment. The YaSM model describes [[LP3: Build new or changed services#LP3.6|the typical deployment activities]], and organizations that have adopted DevOps will implement this as an automated process.

<html>So the YaSM model is not specifically aligned with DevOps, but with its streamlined, straightforward <a href="https://yasm.com/en/products/yasm-process-map" title="The YaSM Process Map: Service management process templates">set of processes and templates</a>, YaSM gives organizations a kind of skeleton for their service management processes, and the flexibility to build DevOps principles into these processes.</html>
 

==Where can I learn more about DevOps?==

Most service management publications these days include sections about DevOps, explaining the basic concepts and highlighting how service management can benefit from the DevOps approach.

Otherwise, 'The Phoenix Project' [[#DevOps-Phoenix-Project|[4]]] is often said to be a must read for anyone who looks for a first introduction to DevOps. It's a novel telling the story of an IT manager who suddenly finds himself promoted into a senior role, applying the DevOps approach to speed up the delivery of value from IT projects.

<html>Naturally, there is also a lot of information about DevOps on the internet. One of the best resources for DevOps on the web is <a class="external" href="https://devops.com/" title="Devops.com - Where the world meets DevOps">devops.com</a> [<a href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#DevOps-com" title="Reference: DevOps.com">5</a>] with a huge amount of original content, including blog posts by industry experts, featured articles, webinars, podcasts etc.</html>
 

==Notes and references==

[1] [https://en.wikipedia.org/wiki/Continuous_integration Continuous Integration]. -- Wikipedia. Retrieved September 22, 2018. 
[2] [https://en.wikipedia.org/wiki/Continuous_delivery Continuous delivery]. -- Wikipedia. Retrieved September 22, 2018. 
[1] Follow [https://twitter.com/patrickdebois Patrick Debois on Twitter]! 
[2] Gene Kim, Kevin Behr, and George Spafford, 2013. The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. IT Revolution Press, Portland, Oregon; USA. 
[3] Devops.com (2018). Where the world meets DevOps. Retrieved from https://devops.com/ 

<html>By:  Stefan Kempter <a rel="author" href="https://plus.google.com/111925560448291102517/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Stefan Kempter | Profile on Google+" alt="Author: Stefan Kempter, IT Process Maps GbR" /></a>  and  Andrea Kempter <a href="https://plus.google.com/113316270668629760475/about"><img style="margin:0px 0px 0px 0px;" src="/wiki/en/img/yasm-wiki/bookmarking/google.jpg" width="16" height="16" title="By: Andrea Kempter | Profile on Google+" alt="Contributor: Andrea Kempter, IT Process Maps GbR" /></a>, IT Process Maps.
 




<a itemprop="item" href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#What_is_DevOps.3F"> What is DevOps?</a>
<meta itemprop="position" content="1" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#The_Three_Ways_of_DevOps"> Three Ways of DevOps</a>
<meta itemprop="position" content="2" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#Does_DevOps_replace_ITSM_and_service_management_best_practice.3F"> Does DevOps replace ITSM and service management?</a>
<meta itemprop="position" content="3" /> ›

<a itemprop="item" href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM#Can_YaSM_and_DevOps_go_together.3F"> The YaSM model and DevOps</a>
<meta itemprop="position" content="4" />



 
<meta itemprop="name Headline" content="DevOps and YaSM" />
<meta itemprop="alternativeHeadline" content="DevOps processes" />
<link itemprop="url" href="https://yasm.com/wiki/en/index.php/DevOps_and_YaSM" />
<link itemprop="primaryImageOfPage" href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" />
<meta itemprop="inLanguage" content="en" />
<link itemprop="citation" href="https://yasm.com/wiki/de/index.php/DevOps_und_YaSM" />
<link itemprop="publisher" href="https://yasm.com/en/#YaSMBrand" />
<link itemprop="copyrightHolder creator" href="https://yasm.com/en/contact#ITProcessMapsOrg" />
<link itemprop="author" href="https://yasm.com/en/misc/team#StefanKempter" />
<link itemprop="contributor" href="https://yasm.com/en/misc/team#AndreaKempter" />
</html>


[[Category:Service management frameworks and standards]][[Category:DevOps|!]]

← Older revision		Revision as of 18:10, 4 April 2024
Line 19:		Line 19:
	<p> </p>		<p> </p>

	<span id="What_is_DevOps.3F"><span id="md-webpage-description" itemprop="description">DevOps describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></span>		<span id="What_is_DevOps.3F"><span id="md-webpage-description" itemprop="description"><b><span style="color:#465674;">DevOps</span></b> describes an approach that aims at unifying software development ('Dev') and software operation ('Ops'). DevOps is not a well-defined framework or process, but rather a set of practices and philosophies. At times it's also called a 'movement'.</span></span>

	<html><div style="float:right; margin-top:2em;"><div itemscope itemtype="https://schema.org/ImageObject">		<html><div style="float:right; margin-top:2em;"><div itemscope itemtype="https://schema.org/ImageObject">
Line 40:		Line 40:
	<meta itemprop="keywords" content="DevOps processes" />		<meta itemprop="keywords" content="DevOps processes" />
	<meta itemprop="keywords" content="DevOps service management" />		<meta itemprop="keywords" content="DevOps service management" />
	<img style="margin:15px 0px 15px 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" width="480" height="360" title="DevOps, service management and YaSM" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a><div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: Use of DevOps in service management</b></span></div></div></div></html>		<img style="margin:15px 0px 15px 20px; float:right;" srcset="https://yasm.com/wiki/en/img/yasm-frameworks/devops/480px/devops-service-management-processes-yasm.jpg 480w, https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg 1200w" sizes="100vw" src="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" fetchpriority="high" decoding="async" width="480" height="360" title="DevOps, service management and YaSM" alt="Does DevOps replace ITSM and service management best practice? Can DevOps and the YaSM process model go together?" /></a><div class="thumbcaption" style="margin:0px 0px 20px 20px"><span style="font-variant:small-caps;"><b>Fig. 1: <a href="https://yasm.com/wiki/en/img/yasm-frameworks/devops/devops-service-management-processes-yasm.jpg" title="DevOps in service management">Use of DevOps in service management</a></b></span></div></div></div></html>

	<p> </p>		<p> </p>

Line 79:		Line 78:
	==Does DevOps replace ITSM and service management best practice?==		==Does DevOps replace ITSM and service management best practice?==

	The term 'DevOps' was first coined in 2009 by Patrick Debois [[#Patrick-Debois-Twitter\|[3]]]. Interest in DevOps grew quickly and, amid much hype, many were lead to believe that DevOps was a better alternative to ITSM and service management frameworks like ITIL.		The term 'DevOps' was first coined in 2009 by Patrick Debois [[#Patrick-Debois-Twitter\|[3]]]. Interest in DevOps grew quickly and, amid much hype, many were lead to believe that DevOps was a better alternative to ITSM and [[Service Management\|service management]] frameworks like ITIL.

	There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. [[Service Management Processes\|Properly defined processes]] are still needed to provide direction and control. How else would organizations ensure, for example, that the services offered are aligned with customer needs, and delivered as promised?		There are many benefits of DevOps, but over time it has become clear that organizations can hardly work with free-wheeling cross-functional teams alone. [[Service Management Processes\|Properly defined processes]] are still needed to provide direction and control. How else would organizations ensure, for example, that the [[Service\|services]] offered are aligned with customer needs, and delivered as promised?

	So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.		So today, the common view is that DevOps and ITSM are not the same. They are complementary and should be combined.