Abstract
In this chapter, I’ll introduce the concept of DevOps. I’ll also summarize in which areas traditional projects suffer, what Agile has done in the past several years to improve this situation, and what is nevertheless still missing in many projects to day. With Agile, testers and programmers became developers, and with DevOps, developers and operations become DevOps. I will show that natural con fl icts between developers and operations often lead to the “blame game,” which can be resolved through use of the DevOps approach. DevOps leads to a “one team” approach where programmers, testers, and system administrators are involved in the development of the solution.
Keywords
- Development Team
- Delivery Process
- Software Release
- Operation Team
- Project Setting
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
In Agile is all about fail quick. If you have success in company you do Agile wrong. —DevOps Borat 1
This is a preview of subscription content, access via your institution.
Buying options
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2012 Michael Hüttermann
About this chapter
Cite this chapter
Hüttermann, M. (2012). Introducing DevOps. In: DevOps for Developers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4570-4_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-4570-4_2
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4302-4569-8
Online ISBN: 978-1-4302-4570-4
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books