DevOps is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment, where building, testing, and releasing software can happen rapidly, frequently, and more reliably. Wikipedia (2017)
DevOps is a culture, movement or practice
DevOps is a term used to refer to a set of practices that
emphasizes the collaboration and communication of
both software developers and other information-
technology (IT) professionals while automating the
process of software delivery and infrastructure changes.
DevOps represents a change in IT culture, focusing on rapid IT service delivery through the
adoption of agile, lean practices in the context of a system-oriented approach. DevOps
emphasizes people (and culture), and seeks to improve collaboration between operations and
development teams. DevOps implementations utilize technology — especially automation tools
that can leverage an increasingly programmable and dynamic infrastructure from a life cycle
DevOps is the union of people, process, and products to
enable continuous delivery of value to our end users.
Microsoft (Donovan Brown)
…rooted in Agile Principles…
Individuals and interactions
over processes and tools
over comprehensive documentation
over contract negotiation
Responding to change
over following a plan
Source: Felice Pescatore
The Handbook says
DevOps is the result of
applying Lean principles to
the technology value
git push hook
Centralized Version Control
Azure Key Vault,
AWS Key Management Service,
Deploy – Comments
Dev / QA / Prod
Source: Pete Hodgson
Where is configuration stored?
How is configuration updated?
Is production configuration isolated and secured?
Where are the secrets and who can access them?
How versions are tracked?
Who authorizes changes and how?
How data is preserved on updates?
How data schema and module interfaces updates?
Using environment images or scripts?
How big is the deploy window?
How are the tracked activities and errors?
How are operational data is collected from production?
To know more
Continuous Delivery: Reliable Software
Releases through Build, Test, and
Deployment Automation — J.Humble,
The Phoenix Project — G.Kim, K.Behr,
G.Spafford (IT Revolution Press)
To know more (cont’d)
The DevOps Handbook — G.Kim,
P.Debois, J.Willis, J.Humble (IT
DevOps on the Microsoft Stack —
Wouter de Kort (Apress)
To know more (cont’d)
Continuous Delivery with Visual Studio
ALM 2015 — M.Olausson, J.Ehn (Apress)
Continuous Delivery with Windows and
.NET — Matthew Skelton and Chris