DevOps - Revision history

Johannesthiem: /* Annotated bibliography */

2021-02-27T15:14:34Z

Annotated bibliography

← Older revision		Revision as of 15:14, 27 February 2021
Line 143:		Line 143:
	:- The DevOps Handbook describes how using the DevOps principles can integrate Product Management, Development, QA, IT Operations, and Information Security to help effective management of technology. It provides a theoretical explanation of the principles as well as a practical approach to applying the DevOps principles. This reference is particularly relevant for technical and organizational structures that can facilitate the principles.		:- The DevOps Handbook describes how using the DevOps principles can integrate Product Management, Development, QA, IT Operations, and Information Security to help effective management of technology. It provides a theoretical explanation of the principles as well as a practical approach to applying the DevOps principles. This reference is particularly relevant for technical and organizational structures that can facilitate the principles.
	*''Davis, J.; Daniels, R. (2016): Effective DevOps : building a culture of collaboration, affinity, and tooling at scale''		*''Davis, J.; Daniels, R. (2016): Effective DevOps : building a culture of collaboration, affinity, and tooling at scale''
	:-Effective DevOps provides actionable strategies to achieve organizational changes. These changes must come from within and this book seeks to be a practical guide to the DevOps principles. It primarily focuses on human factors and job organization in general. It offers a collection of ideas and approaches for improving on key factors of the DevOps principles, like improving collaboration within teams, creating affinity among teams or promoting efficient tool usage.		:- Effective DevOps provides actionable strategies to achieve organizational changes. These changes must come from within and this book seeks to be a practical guide to the DevOps principles. It primarily focuses on human factors and job organization in general. It offers a collection of ideas and approaches for improving on key factors of the DevOps principles, like improving collaboration within teams, creating affinity among teams or promoting efficient tool usage.
	*''Forsgren, N.; Humble, J.; Kim, G. (2018): Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations''		*''Forsgren, N.; Humble, J.; Kim, G. (2018): Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations''
	:-This book provides a summary of the latest research on DevOps and Software Development. It explains, how technology can be applied to drive business value. Findings and the science behind ongoing research on the topic of software delivery performance is presented. The information is presented in a way that makes the application to other organizations possible. For example, explanation on how to measure performance of teams or on what capabilities to invest in to drive higher performance are presented.		:- This book provides a summary of the latest research on DevOps and Software Development. It explains, how technology can be applied to drive business value. Findings and the science behind ongoing research on the topic of software delivery performance is presented. The information is presented in a way that makes the application to other organizations possible. For example, explanation on how to measure performance of teams or on what capabilities to invest in to drive higher performance are presented.
	*''Kim, G.; Behr, K.; Spafford, G, (2013): The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business''		*''Kim, G.; Behr, K.; Spafford, G, (2013): The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business''
	:- The Phoenix Project is a novel about an IT manager that uses the DevOps principles to lead a technology organization to new success. It introduces the Three Ways and shows a fictive success story of the DevOps principles.		:- The Phoenix Project is a novel about an IT manager that uses the DevOps principles to lead a technology organization to new success. It introduces the Three Ways and shows a fictive success story of the DevOps principles.

Johannesthiem: /* Applicability for other sectors and limitations */

2021-02-27T15:12:34Z

Applicability for other sectors and limitations

← Older revision		Revision as of 15:12, 27 February 2021
Line 124:		Line 124:

	== Applicability for other sectors and limitations ==		== Applicability for other sectors and limitations ==
	As the adaptation ~~from~~ principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be successful ~~competitors~~ in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.		As the adaptation of principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be a successful competitor in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.

	However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="disadvantages">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in labor cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.		However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="disadvantages">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in labor cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.

Johannesthiem: /* A small case story */

2021-02-27T15:09:51Z

A small case story

← Older revision		Revision as of 15:09, 27 February 2021
Line 119:		Line 119:
	** enable people to feel more motivated and to take ownership		** enable people to feel more motivated and to take ownership
	** improve the community in which one is responsible		** improve the community in which one is responsible
	** ~~Improve~~ the product one is responsible for		** improve the product one is responsible for
	*Remember that the transformation takes time and will not be an overnight process		*Remember that the transformation takes time and will not be an overnight process
	*It has to be a cultural change in the way people are interacting and disagreements and discussions along the way are ok		*It has to be a cultural change in the way people are interacting and disagreements and discussions along the way are ok

Johannesthiem: /* Designing an organization and architecture */

2021-02-27T15:06:54Z

Designing an organization and architecture

← Older revision		Revision as of 15:06, 27 February 2021
Line 96:		Line 96:
	The DevOps transformation starts with choosing a value stream and building a dedicated transformation team for the effort. Next, one should think about the way an organization can be set up to achieve the value stream goals. In doing so, one should keep Conway´s Law in mind: The organization of the software and the organization of the software team will be congruent; "commonly stated as: 'if you have four groups working on a compiler, you´ll get a 4-pass compiler'".<ref>Raymond, Eric S. (1999): The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary</ref> (Page 224)		The DevOps transformation starts with choosing a value stream and building a dedicated transformation team for the effort. Next, one should think about the way an organization can be set up to achieve the value stream goals. In doing so, one should keep Conway´s Law in mind: The organization of the software and the organization of the software team will be congruent; "commonly stated as: 'if you have four groups working on a compiler, you´ll get a 4-pass compiler'".<ref>Raymond, Eric S. (1999): The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary</ref> (Page 224)

	Thinking of the organization answers also the question of enabling market oriented outcomes. This is achieved through market oriented teams. To achieve the DevOps principles, effects of functional orientation ("Optimizing for cost") must be reduced. Goals should rather be market oriented ("Optimizing for speed"). These two orientations are based on the definition of primary organizational types as defined by Dr. Roberto Fernandez.<ref name="DevOps Handbook"/><ref>Fernandez, Roberto (2021): Creating High Velocity Organizations</ref>		Thinking of the organization answers also the question of enabling market oriented outcomes. This is achieved through market oriented teams. To achieve the DevOps principles, effects of functional orientation ("Optimizing for cost") must be reduced. Goals should rather be market oriented ("Optimizing for speed"). These two orientations are based on the definition of primary organizational types as defined by Dr. Roberto Fernandez.<ref name="DevOps Handbook"/>(Page 140)<ref>Fernandez, Roberto (2021): Creating High Velocity Organizations</ref>

	Large, top-down organizations should be replaced by teams in which all functional skills are embedded. These teams are responsible for testing, operations and security in their daily work. However it should be mentioned that a functional orientation is also feasible as long as all stakeholders of the value stream follow a shared goal (the customer and organizational outcomes).		Large, top-down organizations should be replaced by teams in which all functional skills are embedded. These teams are responsible for testing, operations and security in their daily work. However it should be mentioned that a functional orientation is also feasible as long as all stakeholders of the value stream follow a shared goal (the customer and organizational outcomes).

Johannesthiem: /* Annotated bibliography */

2021-02-26T15:24:05Z

Annotated bibliography

← Older revision		Revision as of 15:24, 26 February 2021
Line 141:		Line 141:
	The following list provides resources for further research and study on DevOps principles:		The following list provides resources for further research and study on DevOps principles:
	*''Kim, G.; Humble, J.; Debois, P.; Willis, J. (2016): The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations''		*''Kim, G.; Humble, J.; Debois, P.; Willis, J. (2016): The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations''
	:- The DevOps Handbook describes how using the DevOps principles can integrate Product Management, Development, QA, IT Operations, and Information Security to help effective management of technology. It provides a theoretical explanation of the principles as well as a practical approach to applying the DevOps principles.		:- The DevOps Handbook describes how using the DevOps principles can integrate Product Management, Development, QA, IT Operations, and Information Security to help effective management of technology. It provides a theoretical explanation of the principles as well as a practical approach to applying the DevOps principles. This reference is particularly relevant for technical and organizational structures that can facilitate the principles.
	*''Davis, J.; Daniels, R. (2016): Effective DevOps : building a culture of collaboration, affinity, and tooling at scale''		*''Davis, J.; Daniels, R. (2016): Effective DevOps : building a culture of collaboration, affinity, and tooling at scale''
	:-Effective DevOps provides actionable strategies to achieve organizational changes. These changes must come from within and this book seeks to be a practical guide to the DevOps principles. It primarily focuses on human factors and job organization in general. It offers a collection of ideas and approaches for improving on key factors of the DevOps principles, like improving collaboration within teams, creating affinity among teams or promoting efficient tool usage.		:-Effective DevOps provides actionable strategies to achieve organizational changes. These changes must come from within and this book seeks to be a practical guide to the DevOps principles. It primarily focuses on human factors and job organization in general. It offers a collection of ideas and approaches for improving on key factors of the DevOps principles, like improving collaboration within teams, creating affinity among teams or promoting efficient tool usage.

Johannesthiem: /* Applicability for other sectors and limitations */

2021-02-26T15:17:26Z

Applicability for other sectors and limitations

← Older revision		Revision as of 15:17, 26 February 2021
Line 126:		Line 126:
	As the adaptation from principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be successful competitors in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.		As the adaptation from principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be successful competitors in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.

	However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="~~disatvatages~~">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in ~~labour~~ cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.		However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="disadvantages">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in labor cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.

	Therefore, the following points should be considered:<ref name="~~disatvatages~~"/>		Therefore, the following points should be considered:<ref name="disadvantages"/>
	*Organizational challenges/disadvantages		*Organizational challenges/disadvantages
	:DevOps requires a number of organizational changes. Previously required skills and skillsets might not be sufficient anymore, while new skills must be added to teams. These leaves old personnel frustrated and opens the need to change ~~personal~~ through hiring people from the external market, where resources are limited.		:DevOps requires a number of organizational changes. Previously required skills and skillsets might not be sufficient anymore, while new skills must be added to teams. These leaves old personnel frustrated and opens the need to change personnel through hiring people from the external market, where resources are limited.
	*Process-related challenges/disadvantages		*Process-related challenges/disadvantages
	:Continuous feedback is at the core of the DevOps principles. However, if not managed correctly, this may lead to difficulties. At least early on in the process an organization must be fault tolerant. Suggested changes might be implemented without careful consideration, overwhelming the user or destabilizing the system.		:Continuous feedback is at the core of the DevOps principles. However, if not managed correctly, this may lead to difficulties. At least early on in the process an organization must be fault tolerant. Suggested changes might be implemented without careful consideration, overwhelming the user or destabilizing the system.
	*Technology-related challenges/disadvantages		*Technology-related challenges/disadvantages
	:One key technology behind the DevOps principles is the automation of work, for example automating the feedback loop back from users to developers or quality assurance testing. This must be done so that the pace of operation can keep up with development. However, if set up incorrectly, it might lead to unforeseen consequences.		:One key technology behind the DevOps principles is the automation of work, for example automating the feedback loop back from users to developers or quality assurance testing. Also automated deployment processes. This must be done so that the pace of operation can keep up with development. However, if set up incorrectly, it might lead to unforeseen consequences.
	*Speed and security-related challenges/disadvantages		*Speed and security-related challenges/disadvantages
	:Typically, speed and security are not two factors that work well together. However, in DevOps both must be ensured. Traditional security-related work, where a design of a system is analysed for weak points, has to be changed. In DevOps, systems are run in production quickly as a minimum viable product, often without a proper design. The security team must then depend upon the advice of the developers and the operations people, showing the need for a good communication between these functions.		:Typically, speed and security are not two factors that work well together. However, in DevOps both must be ensured. Traditional security-related work, where a design of a system is analysed for weak points, has to be changed. In DevOps, systems are run in production quickly as a minimum viable product, often without a proper design. The security team must then depend upon the advice of the developers and the operations people, showing the need for a good communication between these functions.

Johannesthiem: /* Applicability for other sectors and limitations */

2021-02-26T15:14:00Z

Applicability for other sectors and limitations

← Older revision		Revision as of 15:14, 26 February 2021
Line 126:		Line 126:
	As the adaptation from principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be successful competitors in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.		As the adaptation from principles taken from physical manufacturing shows, the DevOps principles and ideas can hold true for different sectors. However, the concrete realization behind DevOps, the collaboration between development, operations, and QA is primarily applicable to IT projects. What can be said is that every organization, independent of the core business, must conduct technology work in some way, to be successful competitors in today´s market landscape. This shows the importance and relevance of DevOps, which can assist in creating value from IT projects.

	However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="disatvatages">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in labour cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.		However, the DevOps principles and ideas are not without shortcomings and the transition should be carefully evaluated. Using the DevOps principles when structuring or managing a new project or portfolio does not only require a new set of tools but also a new mindset and new culture. These changes must reach further than the IT operations departments. Every department and every team that relies on the services provided by IT must be ready to provide continuous feedback. Therefore, to achieve a successful transition, first a comprehensive understanding of DevOps must be reached in in the organization. In addition, funding should be secured. This includes both financial as well as time-related resources. Because, if one chooses to transition to DevOps, you should do it correctly. “A half-baked, insufficiently-funded DevOps “effort” will likely leave you worse off than when you began” <ref name="disatvatages">Tiempo Development (2019): Disadvantages Of Using DevOps [online], available at: https://www.tiempodev.com/blog/devops-disadvantages/</ref>. And DevOps is not the only possible way to reach the desired goal. It is cost-intensive, both in labour cost as well as in operational cost due to extended automation. If speed of continuous updates is not business critical, DevOps might not be the right choice.

	Therefore, the following points should be considered:<ref name="disatvatages"/>		Therefore, the following points should be considered:<ref name="disatvatages"/>

Johannesthiem: /* A small case story */

2021-02-26T15:12:39Z

A small case story

Johannesthiem at 15:09, 26 February 2021

2021-02-26T15:09:01Z

Show changes

Johannesthiem: /* The three ways */

2021-02-26T14:39:00Z

The three ways

← Older revision		Revision as of 14:39, 26 February 2021
Line 39:		Line 39:
	The third way enables a high trust culture. A dynamic, disciplined and scientific approach to experimentation and risk taking is established to facilitate organizational learning from success and failures. Daily work should be continually improved and local learning must be transformed into global learning. Feedback looks are continually shorted (See graphic: The Three Ways) to further amplify the results of the second way, showing that the third way is interwoven with the first and second way. <ref name = "Three ways"/>		The third way enables a high trust culture. A dynamic, disciplined and scientific approach to experimentation and risk taking is established to facilitate organizational learning from success and failures. Daily work should be continually improved and local learning must be transformed into global learning. Feedback looks are continually shorted (See graphic: The Three Ways) to further amplify the results of the second way, showing that the third way is interwoven with the first and second way. <ref name = "Three ways"/>

	Taking the things above in mind, ~~ythe~~ DevOps principles can be summarized as shown in the picture below (The DevOps Toolchain<ref>Creative Commons Attribution-Share Alike 4.0 International, available at: https://commons.wikimedia.org/wiki/File:Devops-toolchain.svg</ref>) that shows what the value stream can look like in DevOps. Most noteworthy in the figure is the cooperation and co-creation between development and operations that is at the core of the concept. In addition, the figure tries to explain the value stream that is needed to allow for continuous delivery of features, another core concept behind DevOps.		Taking the things above in mind, the DevOps principles can be summarized as shown in the picture below (The DevOps Toolchain<ref>Creative Commons Attribution-Share Alike 4.0 International, available at: https://commons.wikimedia.org/wiki/File:Devops-toolchain.svg</ref>) that shows what the value stream can look like in DevOps. Most noteworthy in the figure is the cooperation and co-creation between development and operations that is at the core of the concept. In addition, the figure tries to explain the value stream that is needed to allow for continuous delivery of features, another core concept behind DevOps.

	[[File:1920px-Devops-toolchain.png\|700px\|DevOps Toolchain]]		[[File:1920px-Devops-toolchain.png\|700px\|DevOps Toolchain]]

← Older revision		Revision as of 15:12, 26 February 2021
Line 103:		Line 103:

	==A small case story==		==A small case story==
	The following chapter will provide a short description of a successful case of applying the DevOps principles. This should help in further understanding of the theory and application. One of the most referenced case-stories is the story of Etsy, an online marketplace, who were among the first to successfully adapt the DevOps principles. Part of the success is due to the fact that in 2009, when the transformation started, the change was initiated from the top negating the need for senior management buy in. <ref name="Etsy">Donnelly, Caroline (2015): Case study: What the enterprise can learn from Etsy's DevOps strategy [online], available at: https://www.computerweekly.com/news/4500247782/Case-study-What-the-enterprise-can-learn-from-Etsys-DevOps-strategy</ref> This is however not true for most DevOps transformations. Nonetheless, Jon Cowy (Senior Engineer at Etsy) has some advice for successful transformation processes in all organizations:<ref name="Etsy"/>		The following chapter will provide a short description of a successful case of applying the DevOps principles. This should help in further understanding of the theory and application. One of the most referenced case-stories is the story of Etsy, an online marketplace, who were among the first to successfully adapt the DevOps principles. Part of the success is due to the fact that in 2009, when the transformation started, the change was initiated from the top, negating the need for senior management buy in. <ref name="Etsy">Donnelly, Caroline (2015): Case study: What the enterprise can learn from Etsy's DevOps strategy [online], available at: https://www.computerweekly.com/news/4500247782/Case-study-What-the-enterprise-can-learn-from-Etsys-DevOps-strategy</ref> This is however not true for most DevOps transformations. Nonetheless, Jon Cowy (Senior Engineer at Etsy) has some advice for successful transformation processes in all organizations:<ref name="Etsy"/>
	* focus on the business benefits it can provide, rather than getting too bogged down in tech talk		* focus on the business benefits it can provide, rather than getting too bogged down in tech talk
	* start with a concrete project and show senior management how it has positively affected the business		* start with a concrete project and show senior management how it has positively affected the business
	* the idea should be discussed in business terms because IT and development are service organisations that exist to ~~fulfil~~ the priorities of the business		* the idea should be discussed in business terms because IT and development are service organisations that exist to fulfill the priorities of the business

	In 2015 the Etsy VP of Technical Operations Michael Rembetsy spoke in an interview with John Dix about the steps of the transformation: <ref name="~~interwiew~~">Rembetsy, Michael (2015): Interview with John Dix; How Etsy makes Devops work [online], available at: https://www.networkworld.com/article/2886672/how-etsy-makes-devops-work.html</ref>		In 2015 the Etsy VP of Technical Operations Michael Rembetsy spoke in an interview with John Dix about the steps of the transformation: <ref name="interview">Rembetsy, Michael (2015): Interview with John Dix; How Etsy makes Devops work [online], available at: https://www.networkworld.com/article/2886672/how-etsy-makes-devops-work.html</ref>
	*The need for a change arose when small feature releases required laborious code deploys and deploys of the complete website		*The need for a change arose when small feature releases required laborious code deploys and re-deploys of the complete website.
	*That realization led to the creation of a new team, that build tooling to let people deploy quicker.		*That realization led to the creation of a new team, that build tooling to let people deploy quicker.
	*During this phase, the team also realized the need to make the deployment process simpler and to ~~simplify~~ the interdependence between different system.		*During this phase, the team also realized the need to make the deployment process simpler and to reduce the interdependence between different system.
	*The next step for Etsy was the decision to let developers deploy code themselves, instead of the typical structure where deployment work is done by IT operations. If developers felt the responsibility for deploying code to the site they would also take responsibility for the site being up or down, take into consideration performance, and gain an understanding of the stress and fear of a deploy.		*The next step for Etsy was the decision to let developers deploy code themselves, instead of the typical structure where deployment work is done by IT operations. If developers felt the responsibility for deploying code to the site they would also take responsibility for the site being up or down, take into consideration performance, and gain an understanding of the stress and fear of a deploy.

	Rembetsy ~~however~~ describes no intended change with the DevOps principles in mind. It was rather an organic development with the goal of making the processes faster, better and stronger. <ref name="~~interwiew~~"/> Most important for this organic transition from his point of view was the high trust culture in the company. Building this trust requires time and faith in the work of peers, showing one of the challenges of any DevOps transformation. Therefore, he mentions these points to consider before adopting the DevOps methods for work:		Rembetsy describes no intended change with the DevOps principles in mind. It was rather an organic development with the goal of making the processes faster, better and stronger. <ref name="interview"/> Most important for this organic transition from his point of view was the high trust culture in the company. Building this trust requires time and faith in the work of peers, showing one of the challenges of any DevOps transformation. Therefore, he mentions these points to consider before adopting the DevOps methods for work:<ref name="interview"/>
	*Why are you planning the transformation? Good reasons include the following:		*Why are you planning the transformation? Good reasons include the following:
	** improve the overall structure of the engineering culture		** improve the overall structure of the engineering culture